SterlingKey™ Forum

Hello!

I'm trying to use a Logitech G Pro X mouse with SterlingKey, but the mouse is randomly disconnecting.
Here's my observations:

• SterlingKey status LEDs are normal. Receiver on USB Type-A port is still detected.
• No loss of bluetooth connection from host to SterlingKey.
• Host still claims that a mouse is attached.
• Mouse does not function even after toggling devices; requires SterlingKey reboot or popping the receiver in and out of the USB Type-A port.
• Neither SterlingKey or mouse are out of battery.
• Firmware is 1.3.0.
• Logging is off.
• SterlingKey operates normally when using a typical keyboard.

Hey! Sorry to hear you're having issues. Just to verify, does it happen at random? How often does it happen? Is it just like frozen? All receive power, and all seem connected, but it just does nothing?

To make sure, could you turn on logs and have them running in the background and then send them to me when the freeze happens?

Thanks!

I turned logging on, and the issue did not occur.
I then turned logging off, and the issue still not did occur.



I'll get back with logs later if the issue does reoccur.

I do have a similar issue with my Logitech G403 Hero mouse. At random, sometimes after 5 minutes sometimes after 2 hours, it freezes. Cannot reproduce it reliable. It's probably the same issue since it didn't happen now. It doesn't happen all the time, and it only affects a few devices. I.e. Charachorder.

It's probably a coincidence that both my G403 and your G Pro is from Logitech, because I have other Logitech devices that work flawlessly. Seems to happen *mostly* to high polling rate devices from what I observe.

If it is indeed the same issue, I am already in communication with the developers of the processor that I'm using, because unfortunately it's an error from their end. We are working together to resolve this, and once fixed, or worst case scenario a workaround is found, I will release a firmware update. Sorry for the inconveniece! Hopefully it doesn't occur too often.

I was able download a log while witnessing this issue occur, but it's not particularly useful as far as I can tell. Reproduced issue by going to bed, waking up to mouse without functionality, rebooting the device, then witnessing the issue right away.

Lines when booting up atre:

b11 f#)4 „k1 ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2b (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3818,len:0x109c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xb50
load:0x403cc700,len:0x2fe4
entry 0x403c98ac
EVENT: 0
Vendor ID: 0x46d,
Product ID: 0xc547,
New Device
USB Receiver
bNumInterfaces: 3
bInterfaceNumber: 0
controls: 0
wMaxPacketSize
64
DEVICE READY
bInterfaceNumber: 1
controls: 1
wMaxPacketSize
64
DEVICE READY
bInterfaceNumber: 2
controls: 2
wMaxPacketSize
64
DEVICE READY
USB Receiver
Connected keyboard with name USB Receiver

Last few lines of the log are:

0 0 239 255 245 255 0 0 1 147 64 0 0
Has id: NO
ID: 127
BUFFER SIZE: 13
SEND
0 0 254 255 254 255 0 0 1 147 64 0 0
Has id: NO
ID: 127
BUFFER SIZE: 13
SEND
0 0 230 255 241 255 0 0 1 147 64 0 0
Has id: NO
ID: 127
BUFFER SIZE: 13
SEND
0 0 252 255 253 255 0 0 1 147 64 0 0
Has id: NO
ID: 127
BUFFER SIZE: 13
SEND
0 0 222 255 238 255 0 0 1 147 64 0 0
Has id: NO
ID: 127
BUFFER SIZE: 13
SEND

I suppose moving the mouse produced no other logs, and these are the latest that just worked?

No further lines in the log. Log button was hit by remote desktopping in with a mobile device then hitting the download button.