[Bug] Review Preview API 404 for 00:30–01:00 Segment When Running as Home Assistant Add-on (Works in Docker) #19990
Replies: 2 comments 6 replies
-
The issue you're experiencing with Review Preview API 404 errors during the 00:30–01:00 time segment is a known problem. Based on the available sources, this appears to be related to a bug in Frigate's preview generation system. The Review Preview API endpoint you're hitting returns a 404 when the preview data doesn't exist in the database(1). The API accepts an Similar issues have been reported where preview generation fails for certain time periods. One documented case shows that when calling the API for event preview, users encountered The error you're seeing in your logs shows 404 responses for specific review event IDs, which suggests that the preview files for those particular time segments aren't being created or are being created in the wrong location. Since this issue appears to be specific to the Home Assistant add-on deployment and works correctly in Docker, it may be related to how the add-on handles file paths or preview generation timing compared to the standalone Docker installation. For immediate troubleshooting, you could check if the preview files are actually being generated on disk in your Home Assistant add-on's data directory during those problematic time windows. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
If it's an addon only issue then it's something that needs to be fixed there, add-ons use docker and the container running is identical |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
When running Frigate as a Home Assistant add-on, the Review Preview feature consistently fails for the 00:30–01:00 segment.
This happens consistently across three different instances running as Home Assistant add-ons, but does not occur in my Docker.
The issue affects:
I am in timezone UTC+5:30 (IST).
I’ve also seen previous bug reports about offset issues that were marked as resolved, but the problem still exists in my setup.
Steps to reproduce
Version
0.16.1
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
N/A
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Home Assistant OS
Install method
Home Assistant Add-on
Network connection
Wired
Camera make and model
Dahua
Screenshots of the Frigate UI's System metrics pages
NA
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions