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

Z Boiler Mismatch Loop #353

Open
tmack8001 opened this issue Jun 16, 2022 · 1 comment
Open

Z Boiler Mismatch Loop #353

tmack8001 opened this issue Jun 16, 2022 · 1 comment

Comments

@tmack8001
Copy link
Collaborator

If the Pi remembers the incorrect boiler type based on the first ZState request from the Z unit being incorrectly reported this makes it IMPOSSIBLE (without a coordinated Pi and Z restart, documented below) to reset it.

  1. Restart Z into service utility menu (hold knob during startup)
  2. Restart Pi (or python server)
  3. Select Detect Boiler Type (on Z unit)
  4. Continue as normal as the error is resolved

Feature Options:
In the /devices UI provide insight into the current boiler type (potentially? expose this value on the index.html page in the device information section)

Allow brewer to either change the boiler type in the server /devices experience OR to clear the memorized value to allow a detect boiler request to reset it.

Or better yet, setup config.yml to allow big/small Z profiles to be stored based on the UID. Though to do this for everyone we would need to detect a successful session (and only then memorize the boiler type?)

@tmack8001
Copy link
Collaborator Author

Facebook thread on this exact issue, https://www.facebook.com/groups/Picobrewers/permalink/3219472071665098/

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

1 participant