Just to add my note of thanks for all the hard work that’s gone into this - I now also have both evohome locations after only spinning up my first ever home automation OS (this one HA) about 6 days ago.
Just to make it obvious since it took me FOREVER to find it the install instructions on (how to create a second location for evohome in HA) for any other new user are H E R E with a script to do it here
It’s a shame this thread can’t be linked from the integrations/evohome page.
Br Ant.
I have been unsuccessfully trying to clear the TemporaryOverride status resulting from an automation which boosts evhome DHW via Water_Heater.
I am checking:
the status is FollowSchedule
and then calling operation_mode: on
waiting a bit and then calling
operation_mode: off
Then I am trying to clear the TemporaryOverride flag.
Setting operation_mode: auto does not seem to have the effect of clearing it. I tried Evohome.clear_zone_overrride, but that isn’t really for DHW so it does not work.
Is this all expected or am I missing something?
I checked my card and these are the two actions I have programmed. I don’t often use it but I recall there is a bit of a delay using evohome and setting it back to auto
tap_action:
action: perform_action
perform_action: water_heater.set_operation_mode
target:
entity_id: water_heater.domestic_hot_water
data:
operation_mode: "on"
hold_action:
action: perform_action
perform_action: water_heater.set_operation_mode
target:
entity_id: water_heater.domestic_hot_water
data:
operation_mode: auto
Thank you.
I tried multiple times in dev → actions to set operation_mode: “auto”. Dispite reporting success each time the state of the DHW does not return to FollowSchedule. It remains at TemperaryOverride. In practice this makes no odds since the next setpoint in the system will still be permitted to execute. If I go into the Honeywell TCC app, sure enough the state is “off” until (next setpoint time) and going through the cycle and tapping cancel clears the TemporaryOverride in the app and also in HA once it has synced up.
Ho hum.
All I can add is I didn’t use quotes around the auto.
@zxdavb does the evohome integration now support multiple households? I checked the Honeywell Total Connect Comfort (Europe) - Home Assistant page and it not writes anything yet there.
Not yet - definitely before next winter!
Next PR is to add config flow, but I am a little busy…
After that will be a bunch of breaking changes, and all locations of a user account will be exposed by default.
For example, the refresh_system action will become refresh_location and will thus require a identifier (probably location_id and not _idx).
Also:
scan_interval will be 300 seconds, and not configurableAny update on this? I too could use 2 locations (or 2 separate accounts with 1 location in each would also suffice). Thanks in advance!