Closed johnl closed 1 week ago
Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (evohome
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
evohome documentation evohome source (message by IssueLinks)
by default preset_mode is set to null which means follow the schedule
The above statement is misleading: you are referring to a TCS, but only zones (and DHW) have schedules. They may have their setpoints FollowSchedule
, or be in one of the override modes (TemporaryOverride
, PermanentOverride
).
A preset_mode
of null
(in JSON, or None
in Python) simply says: 'the TCS will let the zones do their thing' (their 'thing' may not be FollowSchedule
).
The two-tier scheme used by evohome (TCS and Zone) does not map cleanly to most climate control schemas (e.g. HA, HomeKi, Google Home, etc.) - although almost all support Away
mode.
Nonetheless, I agree it is a bug.
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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
According to the entity attributes, evohome supports 4 presets when exposed as a "climate" entity
by default
preset_mode
is set tonull
which means follow the schedule - technically this is a 5th preset. Putting it into one of the other presets, such asaway
works as intended, but then it's impossible to put it back intonull
. You can switch to any other preset but can't go back tonull
(which is different to the other presets)trying to use
climate.set_preset_mode
call withnull
or an empty string results in an error message:However, I can use a
evohome.set_system_mode
call to set it back toAuto
(which getspreset_mode
back tonull
):Looking at the code, it seems as if it's translating
preset_mode
to the various evohome system modes, but just doesn't support the defaultAuto
mode:https://github.com/home-assistant/core/blob/dev/homeassistant/components/evohome/climate.py#L77-L83
I also see that preset "Home" is translated to "Day off" mode in evohome - this hints that maybe there was some confusion here as "Home" seems like the opposite of "Away" but really, for evohome, that is actually "Auto", and "Day off" means , follow Saturday's schedule (like you have a day off of work as if it's a weekend day!)
What version of Home Assistant Core has the issue?
core-2024.4.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
evohome
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response