SterlingKey™ Forum

Would like to report what looks like a bug with later firmwares.
My SterlingKey was working fine with my Keyboardio Atreus keyboard until I updated the firmware to version 2.0.0.

After initial pairing with PC running windows 10 the following steps causes SterlingKey to no longer work:
1.Touch the sensor until 3 vibrations and SterlingKey (SK) turns off (LED all goes dark).
2.Touch sensor once, SK vibrates once and turns on. At this point keyboard works fine.
3. After a second or so SK vibrates again although the touch sensor is not touched.
4. After another second or so SK vibrates yet again although it is untouched.
5. Keyboard no longer works. Windows indicates SK is paired and connected but key presses no longer register.

I tried going back firmware versions and found that the same issue can be reproed with version 2.0.0, 1.3.0, and 1.2.1. If I go back to version 1.2.0 then this issue is fixed. Now I can power cycle the SK without the extra vibration and the lost of connection.

Thanks.

Hey, thanks for reporting the issue. As Im currently not at home, could you have a look on other threads to see how to turn on logs and send them to me? Let me know if you need any assistance, you can also join my discord server if youd like. It will be easier to troubleshoot. Link is at the homepage of the forum, thanks!

I will try to get the log as soon as I have time. I found the instructions for enabling it but cannot find anything else about it in the forum. Is the log always printed ? If yes, where is the location of the log output ?

Should I keep the sterling key connected to the PC (SK-s usb-c to PC) while it is also connected to the keyboard (SK's usb-a to keyboard) to view the log ?

Thanks

1. Connect SterlingKey to your computer through the type-c port of SterlingKey, and connect your keyboard to the type-A port
2. Access updater
3. Under Console, click on Start
4. A popup will appear where there will be one device, select that
5. After a few seconds, the connection will be established
6. Type "set debug 1" and click enter
7. Click Reset
8. This should restart the device and might trigger the same issue
9. If it doesnt occur, try manually restarting as the steps you mentioned earlier

So the logs are always outputting in realtime at the console in the updater page. Keep all cables connected