Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't return from deep sleep state until reset button is pressed #11

Open
alparo opened this issue Apr 29, 2024 · 3 comments
Open

Doesn't return from deep sleep state until reset button is pressed #11

alparo opened this issue Apr 29, 2024 · 3 comments

Comments

@alparo
Copy link

alparo commented Apr 29, 2024

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

@ShijiMi-Soup
Copy link

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: ShijiMi-Soup/zmk-config@39fc15d

@alparo
Copy link
Author

alparo commented May 28, 2024

@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.

@ShijiMi-Soup
Copy link

@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.

joekain added a commit to joekain/zmk-config that referenced this issue Aug 25, 2024
This is newly required with support for soft-off.

See mmccoyd/zmk-config#11
joekain added a commit to joekain/zmk-config that referenced this issue Aug 27, 2024
This is newly required with support for soft-off.

See mmccoyd/zmk-config#11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants