Enforce brew mode until confirmed#31
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.
Field bug (2026-07-11): /wake cold-start sent change-mode one second after the machine WebSocket appeared — while the controller board was still applying startupMode — so the command was silently swallowed and the user waited 39 minutes for a machine that was never heating. The firmware sends no acknowledgment for mode changes, so a single fire-and-forget send can never be trusted. All wake paths (/wake, pending wake, morning auto-heat) now arm an enforcer: resend change-mode every 8s while status frames still report standby, stop on observed brew mode, give up loudly after 90s. /sleep disarms it.