Skip to content
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

Closed
2 tasks done
andrey-yantsen opened this issue Apr 1, 2024 · 5 comments
Closed
2 tasks done

Target rate sensors ignore day-light saving time #815

andrey-yantsen opened this issue Apr 1, 2024 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@andrey-yantsen
Copy link

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

  1. Set the system timezone to Europe/London (British Summer Time specifically)
  2. Ensure the time is correct
  3. Set up a target rate sensor for running between 16:00 and 21:00 — most likely the sensor will be still active between 21:00 and 22:00.
image

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

  • I confirm that I cannot find my solution within the documentation
  • I confirm that I cannot find my solution within the FAQ
@andrey-yantsen andrey-yantsen added the bug Something isn't working label Apr 1, 2024
@seanmaskey
Copy link
Sponsor

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.

@isteel
Copy link

isteel commented Apr 3, 2024

+1
The timings for cheapest periods are an hour out since the shift to BST. This is preventing use of the automation atm.

@Markyt77 Markyt77 mentioned this issue Apr 3, 2024
2 tasks
@BottlecapDave
Copy link
Owner

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.

@BottlecapDave
Copy link
Owner

The underlying issue should now be fixed in v10.2.1 which should result in the sensor turning on/off during the requested times.

@andrey-yantsen
Copy link
Author

Thank you, @BottlecapDave! It works like a treat!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants