Hass: Evohome Debug Logs

Integrating Honeywell's undocumented API into Home Assistant is not a trivial exercise (just look at the code) - issues may still occur, especially with edge cases.

To resolve your issue, I might ask to see your raw JSON - if you're willing to do that, then add the following to Home Assistant's configuration.yaml:

logger:
  default: info  # turn off debug messages, generally...
  logs:
    homeassistant.components.evohome: debug
    homeassistant.components.evohome.climate: debug
    homeassistant.components.evohome.water_heater: debug

When you restart HA with the above logging, you can then search the log file as follows:

cat ~/.homeassistant/home-assistant.log | grep evohome

... and you'll see something like:

2023-09-15 15:36:09.373 DEBUG (MainThread) [homeassistant.components.evohome] Config = {'locationInfo': {'timeZone': {'timeZoneId': 'GMTStandardTime'...
2023-09-15 15:36:13.557 DEBUG (MainThread) [homeassistant.components.evohome] Temperatures = {'3432579': 128.0, '3449740': 21.3, '3432521': 128.0...
2023-09-15 15:36:13.708 DEBUG (MainThread) [homeassistant.components.evohome] Status = {'locationId': '2738909', 'gateways': [{'gatewayId': '2499896'...
2023-09-15 15:36:13.722 DEBUG (MainThread) [homeassistant.components.evohome.climate] Found the Location/Controller (EvoTouch), id=3432522, name=My Home (location_idx=0)
2023-09-15 15:36:13.723 DEBUG (MainThread) [homeassistant.components.evohome.climate] Adding: RadiatorZone (HeatingZone), id=3432577, name=Front Room
2023-09-15 15:36:13.723 DEBUG (MainThread) [homeassistant.components.evohome.climate] Adding: RadiatorZone (HeatingZone), id=3432578, name=Kitchen
2023-09-15 15:36:13.723 DEBUG (MainThread) [homeassistant.components.evohome.climate] Adding: RadiatorZone (HeatingZone), id=3432579, name=Bathroom
2023-09-15 15:36:14.129 DEBUG (MainThread) [homeassistant.components.evohome] Schedule['Front Room'] = {'DailySchedules': [{'DayOfWeek': 0...

Of particular use will be the lines with Config =, Temperatures = (is optional), and Status =. I may also need Schedule[...] = too.

NOTE: the JSON does not include personally identifiable information, other than zone names, your time zone and ID numbers.

Active Faults

It would be helpful if you looked for any 'Active fault' warnings like so:

2024-08-01 22:15:50.524 WARNING (MainThread) [evohomeasync2] Active fault: Zone(id='3432576'): TempZoneActuatorCommunicationLost, since 2022-03-02T15:56:01
2024-08-01 22:15:50.524 WARNING (MainThread) [evohomeasync2] Active fault: Zone(id='3432577'): TempZoneActuatorLowBattery, since 2022-03-02T04:50:20

... and included them in your submission.