appdaemon
appdaemon copied to clipboard
Cannot set temperature persistently
I have the following settings in my schedy.yaml:
sleeping:
allow_manual_changes: true
rescheduling_delay: 10
actors:
climate.eurotronic_spzb0001_1975c403_thermostat:
template: zigbee
schedule:
- value: 23
weekdays: 2-5
start: "8:00"
end: "17:00"
- value: "OFF"
start: "6:00"
end: "9:00"
- value: 18
watched_entities:
- climate.eurotronic_spzb0001_1975c403_thermostat
Since AppDaemon 4.2, this does not work anymore:
2022-01-18 17:00:00.146730 INFO schedy: <-- [R:sleeping] Value set to 18.0��. [scheduled]
2022-01-18 17:00:02.417154 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 18.0��.
2022-01-18 17:00:02.592938 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 23.0��.
2022-01-18 17:00:02.621737 INFO schedy: --- [R:sleeping] Re-applying the schedule not before 17:10:02 (in 0:10:00).
2022-01-18 17:10:03.048137 INFO schedy: <-- [R:sleeping] Value set to 18.0��. [scheduled]
2022-01-18 17:10:04.229819 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 18.0��.
2022-01-18 17:10:04.446016 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 23.0��.
2022-01-18 17:10:04.452730 INFO schedy: --- [R:sleeping] Re-applying the schedule not before 17:20:04 (in 0:10:00).
(And so on and so forth.) Downgrading to Appdaemon 4.1 restores the correct behaviour:
2022-01-18 20:41:24.736323 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 23.0��.
2022-01-18 20:41:28.178263 INFO schedy: <-- [R:sleeping] Value set to 18.0��. [scheduled]
2022-01-18 20:41:28.301263 INFO schedy: --> [R:sleeping] [A:climate.eurotronic_spzb0001_1975c403_thermostat] Received value of 18.0��.
(And it keeps the 18.0.)
There were some breaking changes in 4.2.0 so you may want to reach out to the maintainer of schedy.
Thanks for the assessment. I filed it also against Schedy here: https://github.com/bob1de/hass-apps/issues/73
Should we keep both open until the problem is localised? Otherwise, feel free to close.
schedy is independant from appdaemon. so indeed your problem should be reported be schedy. robert always did very well supporting on the HA forum in his dedicated schedy topic. in the meantime, because you are an AD user, because you use schedy, you could see if there are breaking changes in AD, that would effect schedy. (see https://appdaemon.readthedocs.io/en/latest/HISTORY.html and the code you use.)