[Bug]: Events from the first hour of each day inaccessible after daylight saving time ended #20764
-
Checklist
Describe the problem you are havingAfter daylight saving time ended today, the events from the first hour of each day was moved to the previous day in the review interface and became inaccessible.
Steps to reproduce
Version0.16.2-4d58206 In which browser(s) are you experiencing the issue with?No response Frigate config file.docker-compose file or Docker CLI command.Relevant Frigate log output.Relevant go2rtc log output.Operating systemOther Linux Install methodDocker Compose Network connectionWired Camera make and model. Screenshots of the Frigate UI's System metrics pages. Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
Based on the available sources, this appears to be a timezone-related issue that has been documented in similar cases with Frigate's review interface. The issue you're experiencing where events from the first hour of each day become inaccessible after daylight saving time ended is consistent with timezone handling problems that have been reported with Frigate's review system(1). Users in non-standard offset timezones (like UTC+5:30) have reported similar issues where the Motion review tab doesn't work correctly when the client is set to certain timezones, showing "No Preview Found" errors or displaying incorrect time ranges(1). This specific problem with DST transitions appears to be related to how Frigate handles timezone conversions between the server time, recording timestamps, and the browser's local timezone. When DST ends, there's a one-hour shift that can cause misalignment in how review items are indexed and retrieved. For context, the Review page displays review items on a vertical timeline with filterable previews(2). Review items are time periods where tracked objects were active, and they're designed not to overlap for a single camera(2). While I don't have specific documentation about DST transition handling in version 0.16.2, similar timezone issues have been addressed in recent Frigate updates. You may want to:
This appears to be a legitimate bug that would benefit from being tracked by the development team. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
What timezone are you in? We haven't made any changes and this has been tested and working through multiple time changes. |
Beta Was this translation helpful? Give feedback.

Fixed in #20770