Open alparo opened 4 months ago
I had the same problem but fixed after adding wakeup-source;
to the kscan node, as mentioned in the discord post.
See https://zmk.dev/docs/development/new-shield#shield-overlays for an example of a kscan node with this property set correctly.
You can also see the changes that I made in my config here: https://github.com/ShijiMi-Soup/zmk-config/commit/39fc15dd3d56d68ee2899414ab45685c852fea68
@ShijiMi-Soup thank you. I did the same change in my repo. Now the right half wakes up flawlessly. But the left half still can be woken up only by pressing the reset button. As it have never worked before I tend to think, that this is some kind of a hardware issue.
@alparo Glad to hear that the half worked 😊. Both halves of my split keyboard are working fine, so it might be something else causing that issue.
After going to deep sleep after timeout the keyboard doesn't allow to wake it up by pressing any button. Only pressing reset on both halves gets it back to working state. According to discord the solutions should be somewhere there:
" FYI: One small regression has been reported when enabling the ZMK_SLEEP config setting now that soft-off feature has been merged. I've fixed up all the in-tree boards & shields but if you are using a custom board/shield with deep sleep, you will need to fix the definition by adding a wakeup-source; property to all your kscan nodes. See https://zmk.dev/docs/development/new-shield#shield-overlays for an example of a kscan node with this property set correctly. Apologies for any disruption this may have caused you. " From https://discord.com/channels/719497620560543766/719544534500900886