Powersaving on companion when serial is off (ble/wifi) #1347
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weebl2000
changed the title
fschrempf
reviewed
Jan 8, 2026
weebl2000
force-pushed
the
powersaving-ble-companion
branch
from
35fad46 to
69f1ad3
Compare
This also fixes repeaters waking up on button presses (they do not currently)
Author
|
Moved button handling logic to ESP32Board - this has the added benefit that repeaters will also wake up when you press the button (they do not currently). |
Author
|
@fschrempf Actually all basically all devices are low when pressed. Updated the code accordingly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at the repeater firmware I think we can do some more powersaving when BLE/WiFi is off.
After comment by @fschrempf I realized nearly all devices have button pressed = low instead of high, so I also fixed that. Let me know if I should split that up in a separate PR.