TOD (Times Of the Day) is not working correctly after daylight saving
See original GitHub issueThe problem
TOD sensor is ignoring daylight saving time.
Sensor changed state at 10:30
, after CET->CEST (+1h). After HA reboot everything works correctly.
What is version of Home Assistant Core has the issue?
2021.3.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
tod
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tod/
Example YAML snippet
- platform: tod
name: day
after: '09:30'
before: '22:00'
Anything in the logs that might be useful for us?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:22
Top Results From Across the Web
Effect of daylight saving time changes - IBM
Generally, most hardware (TOD) clocks are set to Greenwich Mean Time (GMT), with an offset value to indicate local time. It is this...
Read more >Time of day and nzdt - Home Assistant Community
This looks like a related issue: TOD (Times Of the Day) is not working correctly after daylight saving · Issue #48460 · home-assistant/core ......
Read more >Daylight Savings Time - elaws - FLSA Hours Worked Advisor
On the Sunday that Daylight Savings Time starts at 2:00 a.m., the employee does not work the hour from 2:00 a.m. to 3:00...
Read more >Babies and Daylight Saving Time - What to Expect
Here's how daylight saving time can affect your baby or toddler, plus how to maintain her sleep schedule whether you're springing forward or ......
Read more >of daylight saving time is incredibly high. - Inc. Magazine
That's why the number of heart attacks tick up significantly the day after we set the clocks ahead. A similar trend appears when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Encountered this issue following this morning’s UK Daylight Savings change.
configuration.yaml
Following clocks change binary_sensor.tod_ha_night state changed to ‘on’ at 21:00. Host OS and the HA Time & Date sensor both showed correct time, After a HA restart at 21:04 binary_sensor.tod_ha_night correctly showed ‘off’.
Anything? How time automation - something so basic - can be broken on home automation software?