HA Add-on: Timestamps inconsistent timezones between frigate/g02rtc/nginx logs

[bdelima]

I can't seem to figure out how to set the timezone across these 3 components so it's consistent. I'm running a standard HAOS image on and N150 mini-pc with the Frigate Add-on. I would think that a canned config like this would just work correctly out of the box, but it doesn't. My Frigate log entries are the correct time, but both nginx and go2rtc logs are 4 hours ahead (I'm assuming it's defaulting to UTC). I've added the timezone setting in my Frigate config fiile to no avail, times are still off by exactly 4 hours. It appears the Frigate UI applies the timezone to what I see in the log viewer only for the Frigae entries. But the raw logs show every log entry exactly 4 hours off. My HA instance is set to the correct imezone, and HA itself is showing everything in the correct time. What do I need to do to fix this in the Frigate Add-on?

[inkeep-ai-assistant[bot]]

This is a known timezone display issue with the Frigate Home Assistant Add-on. The logs themselves are correctly timestamped, but the web UI displays them inconsistently across different components(1)(2).

For the UI timezone configuration, you can set this in your Frigate config:

ui:
  timezone: America/Chicago

(3)

However, based on the GitHub discussions, this setting primarily affects the UI display rather than the underlying log timestamps(1)(2). The issue you're experiencing where Frigate logs show correct time but go2rtc and nginx logs are 4 hours off is a known behavior(1)(2).

The timezone inconsistency appears to be related to how different components within the add-on handle timezone settings. While Frigate respects the container timezone, go2rtc and nginx may not be inheriting the same timezone configuration(1)(2).

Unfortunately, the available sources don't provide a definitive solution for making all three components (Frigate, go2rtc, and nginx) display consistent timestamps in the Home Assistant Add-on environment. The discussions indicate this is an ongoing issue with the add-on's timezone handling(1)(2).

📚 Sources:

1. [Support]: Time zone setting is not applied to log timestamps displayed in the UI
2. [Support]: Logs not respecting timezone
3. Do not use time / timezone from browser

---

Have another question? Just tag @inkeep.

[NickM-27]

it's an issue with the addon not passing the appropriate data, it is not a problem when running Frigate via docker directly as there is more control over this