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
Evohome integration reporting temperatures of 128 degrees celsius #34559
Comments
Well, the answer is in the logs, firstly:
... and also:
A proposed solution (not best-practice code, tho'): def current_temperature(self) -> Optional[float]:
"""Return the current temperature of a Zone."""
if self._evo_broker.temps:
if self._evo_broker.temps[self._evo_device.zoneId] != 128:
return self._evo_broker.temps[self._evo_device.zoneId]
if not self._evo_device.temperatureStatus["isAvailable"]:
return None
return self._evo_device.temperatureStatus["temperature"] |
This is a bit of an edge-case, I (am a bit busy, but) will submit a PR ASAP. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
@zxdavb did this one ever make it in? I still see the problem sometimes.. |
OK, the issue is when the temp is valid for the v2 API, but the v1 API temp is used, but it isn't valid, so is set to 128. |
The problem
When batteries are low in TRV's, the evohome component is reporting 128 degree C temperatures
Environment
hass 107.7, Ubuntu server, hass.io
107.7
?
Supervised
evohome
https://www.home-assistant.io/integrations/evohome/
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
As discussed here
The text was updated successfully, but these errors were encountered: