Z Boiler Mismatch Loop #353
Description
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.
- Restart Z into service utility menu (hold knob during startup)
- Restart Pi (or python server)
- Select Detect Boiler Type (on Z unit)
- 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?)