home-assistant[bot]
commented
2 months ago Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
TheJulianJES
mabex9
The problem
After updating to home assistant 2024.8.0, the time shown on my Sinope TH1300zb thermostats is 4 hours ahead. It's likely in the wrong time zone.
I tried correcting time on one thermostat by writing the correct time in the manufacturer cluster attribute sec_since_2k. It works for about 1h after which it goes back to 4 hours ahead.
I use a skyconnect dongle with zha to control my ZigBee devices. I have HA OS running on a laptop.
What version of Home Assistant Core has the issue?
Core-2024.8.0
What was the last working version of Home Assistant Core?
Core-2024.7.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zha
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
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