Frontend displays UTC time instead of local time

Configuration
1

I’ve found a number of posts about this, however, most of them conclude that with Home Assistant running on Hass.io on a raspberry Pi 3b+ that everything on the frontend should display in the local time defined in configuration.yaml. my time_zone: is set to America/Chicago under homeassistant:
About/SystemHealth shows the timezone as America/Chicago

All automation settings are correctly translated to local time (CDT). So switches turn on/off based on the CDT time I programmed them to operate.

All times in the frontend Logbook and History are in UTC

The frontend “time since last snapshot” appears to be mixed. I show the last snapshot date as Sunday, Mar 17, 2019 (16 hours ago). It is 11:12am on March 17th here now, so 16 hours ago would have been March 16th. I say it appears mixed, because, when I create a new snapshot it will show as being made one minute ago.

Error log on the About screen seems to be reporting UTC only.

If I fire up a SSH session and ask the operating system the date it replies with Sun Mar 17 11:12:36 CDT 2019

I’m on HassOS 2.10 with Hass.io supervisor 148 and Home Assistant version 0.89.2.

I’m just checking to see if I have configured something incorrectly. It seems counter intuitive to require the user to calculate local time for most everything they see on the frontend.

2

I think I figured it out.
Someone tell me if I’m crazy, but it looks like HA is smart enough to ask the browser what time zone it is in. Then translates the time to the browser. My primary browser (firefox) does not relay this information so I get UTC in that browser. When I fire up Safari, Everything displays in the correct time zone.

3

Happened to me today on Chrome v73, a refresh fixed it. I was in the future for a moment.

4

have this problem now, scene that’s set to run at 9am runs at 10am,??? Didn’t changed anything. Geographic locali8 is set via Map in settings, bug for me.

5

I am actually using Firefox 78.15.0esr (64-Bit).
The time in the frontend of HA is showing UTC.
If I am using Chrome Browser the time is local.
It seems this problem occurs to the Firefox Browser.
Has somebody already solved this issue?

6

I am having the same exact issue.
But i think this is from HA version because it check it on old Firefox ESR version and the same.

7

I’m having the same issue now, see this logbook entry (local time is 21:43, UTC+2):

  • Safari (and native HA app): Rotor status changed … 19:43:01 - 4 minutes ago
  • Chrome: Rotor status changed … 21:43:01 - 4 minutes ago

Both of the above on my Mac. My iPhone reports right time (21:43) in both the companion app and in Safari.

Could this be related to the release of 2021.10? I haven’t seen the issue before, and somehow this thread is updated with three new reportings a year later?

8

I have this problem on an Android device even though time settings seem to be correct.

9

Any chance this issue popped up after upgrading to 2021.10.x? My Fire HD10 started doing this in both the companion app and in fully kiosk. Chrome was not impacted (not reliant on the older webview chromium that you’re stuck with on the Amazon tablets).

I rolled back to 2021.9.7 and my Fire HD10 front end was the correct time again. For the moment it looks like I’m stuck on this version, as UTC is a fair way behind Sydney time and the family weren’t happy with the kitchen control panel showing yesterday’s weather.

10

I"m also facing the same issue here as well everything showing UTC time in my frontend. Hoping for a fix for this.

11

Please post your experience here: UTC showing in frontend in some browsers · Issue #10502 · home-assistant/frontend · GitHub

I’m not having much luck getting the powers that be to engage on the issue.