Event-driven /wake#28
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The inline cold-start flow (hook, wait 90s, change-mode) raced the WS reconnect backoff and gave up entirely when the plug hook failed — observed in the wild when the plug had a WiFi dropout. /wake now arms a 15-minute pending intent that fires the moment the machine comes online, the same event path the morning auto-heat uses. Works even when the plug is unreachable and the machine gets powered by hand. Plug hooks retry 3x; a new client.nudge() cuts the reconnect backoff short so the switch to brew happens seconds after boot.