Keyboard halves don't connect to each other after PC wakes up from sleep

[totkeks]

I am using a Windows 11 PC and the Advantage 360 Pro with the 3.0 firmware.

I have the issue that the halves don't connect to each other after my PC wakes up from sleep. I only have the three LEDs blinking in red when pressing any key.

From my observations it only happens when the keyboard is connected to the PC via an USB hub that is powered down when the PC goes to sleep, e.g. the USB hub in my monitor or my new powered USB hub (it doesn't use/receive power from the PC, neither sleeping nor awake).

In contrast, when I connected the keyboard halves to my PC directly this error never happened.

Is there any way to increase the delay for when the two halves try to find each other? Or another way to fix this besides unplugging the cables and plugging them again?

[ReFil]

is there any activity from the left side when this happens i.e. layer light lighting up when you push the kp layer key?

[totkeks]

is there any activity from the left side when this happens i.e. layer light lighting up when you push the kp layer key?

Luckily, I just had it happen again.

No activity on the left side when I click the kp or fn keys.
I also just noticed that the red blinking LEDs are only present on the right side, not on the left one.

Does this mean the left side didn't power on / boot properly?

[ReFil]

yes, are you running the latest available firmware? it's possible you're encountering a bug in older versions of the firmware

[totkeks]

I was not, but I just updated my repo locally with the latest changes from the V3.0 branch and built and flashed the new firmware.
Sent my PC to sleep, woke it up again and had the same issue again.

Is there any way I could debug this or retrieve a log file from the left side?

Btw, the backlight was on after waking the PC, so at least it was powered. If that is any help.

[ReFil]

Neither of your branches on that repo look to be up to date. Can you try the latest unchanged firmware first please (from here: https://github.com/KinesisCorporation/Adv360-Pro-ZMK/actions/runs/8709784894) and see if that works?

[totkeks]

That is right. I just did a quick merge locally without pushing it.

I just flashed the version you linked, sent the PC to sleep and woke it up. Same error as before.

[ReFil]

It sounds like there's some weird power management conflict going on. You can enable UART logging but it uses the usb connection for it. I haven't been able to replicate this crash in my testing. Maybe turning off some of the power management settings for the usb hub in device manager will help?

[NullFragment]

I think this has more to do with the order in which both halves of the keyboard regain power if you have them plugged in and the power switches set to the off position. I've noticed that if I plug my keyboard halves into a hub vs the computer itself, sometimes it will be fine and other times I'll have to unplug and replug both halves of the keyboard back in.

That said, it only happens if I don't have the power for the halves switched on so they maintain power during the brief periods in which the hub doesn't supply power to them.

[KinesisCorporation]

The power-on sequence was definitely a factor in 1.0 firmware (syncing worked best when the left module had a moment to initialize first, before turning on the right) but hasn't really been an issue for a while to our knowledge.

@NullFragment It looks like you've got a 3.0 build so you should not be seeing this unless there is something unique about the Hub. Are you able to reproduce failure-to-sync-on-startup just by turning on the battery on the right module, then the left.

[NullFragment]

Oddly enough, I haven't been able to reproduce it since I wrote that comment. It was only happening when using both modules wired with the power turned off. The power sequence didn't seem to matter if I was using wireless, but I've tried both unplugging the keyboards from the USB hubs as well as the hub itself from the PC and couldn't repro it again.

[duanemay]

I recently changed my setup where my keyboard plugs into my monitor's hub and switches between two computers. After the monitor goes to sleep, it cuts power to the USB devices, and after wake up I also get the blinking red lights on the right half of the keyboard. I am on the latest 3.0 firmware.

As a work around, I changed settings on the monitor to keep the USB powered on during sleep. However, this also makes it so the monitor does not always go to sleep.

[KinesisCorporation]

Hi Duane,

That's also surprising behavior. Can you run the "Version Macro" command (Mod + V) for us here so we can see what firmware you are runng