-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target rate sensors ignore day-light saving time #815
Comments
Similar here. Agile target rate sensors seemed to come back up at 23:00 last night 1st April- I could see valuess set in attributes- But are all unavailable again since early this morning. |
+1 |
Hello and sorry for the late response. I think I've found the issue, so will get a fix out within the next few days. |
The underlying issue should now be fixed in v10.2.1 which should result in the sensor turning on/off during the requested times. |
Thank you, @BottlecapDave! It works like a treat! |
Describe the bug
This Sunday, the UK switched the clocks from UTC(+0:00) to BST(+1:00). Today I noticed that one of my target rate sensors, which is supposed to be triggered between 16:00 and 22:00, was enabled from 21:30 to 23:00.
P.S. I did reboot the HA instance today, just to be sure that everything sees BST.
Reproduction steps
Expected behaviour
The target rate sensor uses the local time when checking the minimum/maximum time.
Tariff Code
E-1R-AGILE-23-12-06-H
Integration Version
10.1.4
Home Assistant Version
2024.3.3
Fresh Install?
After upgrading
Home Assistant Logs
n/a
Confirmation
The text was updated successfully, but these errors were encountered: