Closed hausmanconsulting closed 1 month ago
Hey there @tstabrawa, mind taking a look at this issue as it has been labeled with an integration (nuheat
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
nuheat documentation nuheat source (message by IssueLinks)
Further testing reveals this is entirely on NuHeat; using their app to change the target temperature also causes the DST setting to disappear. I'll open a ticket with them.
I'll add a comment/solution here in case anyone else has this issue. So far, it appears that not using the DST setting and turning off network time sync allows the temperature and hold/run settings to work without changing the time. You'll need to change the time on the thermostat(s) for every switch to/from DST, but at least the clock won't change on you unexpectedly.
The problem
I am using the NuHeat integration on HA 2024.5. When I call the service "climate.set_temperature":
The "Use Daylight Savings" setting on the NuHeat Signature thermostat becomes unchecked, and the time resets back to Standard Time. This causes a problem because the thermostat thinks it is an hour earlier and the program doesn't run at the correct time.
What version of Home Assistant Core has the issue?
core-2024.5.3
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
NuHeat
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nuheat
Diagnostics information
home-assistant_nuheat_2024-05-16T16-22-41.144Z.log
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
It can take up to 30 seconds for the clock on the thermostat to change by an hour.