Timezone is correctly set however graphs are showing in UTC

del13r · October 14, 2021, 10:36pm

My timezone is 11hours head of UTC so this result is correct

However, my graphs are all in UTC

What on earth is going on here?

JakeK · October 14, 2021, 10:52pm

Same exact problem since updating last night. Something broke. I’ve already checked all the time zones on both my NAS and in HA and have restarted everything. Still off. I also noticed that the time zone was changed in HA on it’s own and currency was set to EUR. But those might be unrelated.

del13r · October 14, 2021, 10:53pm

I just fixed this by doing a full backup and restore.

~~Now back to normal.~~

Weird.

Edit: just checked again and the graphs are back to UTC again! not fixed!

JakeK · October 14, 2021, 10:54pm

Yea I’m not about to do that. There has too be a solution besides a nuke.

JakeK · October 14, 2021, 11:00pm

~~OK it appears that it resolved it’s self a few minutes after a full reboot. :s Very weird.~~

It is showing correct on the app but not Firefox. Edge shows the correct time too. I tried clearing the cache and deleted the cookies for that IP address. no effect.

JakeK · October 14, 2021, 11:25pm

I’m at loss as to why this is happening.

del13r · October 15, 2021, 1:32am

OK, i think we have hit the nail on the head here.

appears to be a bug in home assistant that affects graphs when accessed via web browser.

While when accessing using web browser, all graphs and history are displayed in UTC.

Same graph when viewed on my mobile via the iOS app which formats perfectly.

Sddawson · October 15, 2021, 1:54am

Seems OK using Safari on a Mac.

del13r · October 15, 2021, 1:58am

all web browsers for me

raised an issue

Sddawson · October 15, 2021, 2:06am

Very strange. Here’s mine:

del13r · October 15, 2021, 2:14am

Interesting,

I am on a family members laptop that they are a bit late in updating their apps.

I updated google chrome from Version 80.0.3987.122 (Official Build) (64-bit)
to Version 94.0.4606.81 (Official Build) (x86_64)
and that fixed the issue for chrome.

Firefox 73.0.1 (64-bit) - graphs incorrectly shown in UTC
upgraded firefox to 93.0 (64-bit)
and that fix the issue for Firefox

JakeK · October 15, 2021, 2:14am

Edge works fine for me. Havent tried chrome. I thought maybe firefox got hosed, but firefox is correctly reporting date, tz, and time in the console. I’ve cleares cache, cookies, and restarted both the pc and the browser.

JakeK · October 15, 2021, 2:17am

So I just updated firefox and it fixed the issue for me. :s this is some weird stuff.

del13r · October 15, 2021, 2:34am

I am also on a Mac (Early 2011 MacBook Pro) which cannot upgrade any higher than macOS 10.13.6

The highest safari version that is allowed on macOS 10.13.6 is
Safari Version 13.1.2 (13609.3.5.1.5)
which was Released 15 July 2020
For reference, the latest version of safari is 15.0 released in 20 Sept 2021

When I access home assistant using version 13.1.2 of safari, all the times are still shown incorrectly in UTC.
The only way to view home assistant properly on this old mac is to use chrome or firefox instead.

Sddawson · October 15, 2021, 3:20am

So it would seem HA has recently introduced an incompatibility with older browsers. Might still be worth following up I guess.

mitchellross · November 2, 2021, 11:25pm

github.com/home-assistant/frontend

UTC showing in frontend in some browsers

opened 11:02AM - 02 Nov 21 UTC

mitchellross

bug

### Checklist - [X] I have updated to the latest available Home Assistant versi…on. - [X] I have cleared the cache of my browser. - [X] I have tried a different browser to see if it is related to my browser. ### Describe the issue you are experiencing Since updating to 2021.10.x (now on 2021.10.7) - various browsers attached to my Supervised install have been using UTC rather than local Sydney/Australia time. This has meant that yesterday's weather has been displayed etc. I have replicated this issue on completely fresh install of Debian & Supervised and looking at the logs or any card dependent on timings (like weather) on Firefox on the host machine. Likewise, pointing my Fire HD10 (2019) at that instance shows this behaviour in both Fully Kiosk and the Companion App. "Updating" to 2021.9.7 fixes this issue. The issues do not appear on Chrome or Safari. As an example of this issue, this is a screenshot of the logs section of Supervisor. You can see that the summary entries are appearing in UTC, while the detailed entries below are in local time. This did not occur prior to 2021.10.x. (https://user-images.githubusercontent.com/39319760/139831303-deb733d9-d648-498a-ad94-f6260ca7b0b7.png) ### Describe the behavior you expected I would expect to see a consistent application of local time at the front end of all devices and all browsers, as was the case on 2021.9.7. ### Steps to reproduce the issue 1. Point an impacted browser (Firefox, Amazon Webview based apps etc) at any HA instance from 2021.10.x onwards 2. Check to see whether the front end displays things like the logs, or weather forecasts in local time. 3. ... ### What version of Home Assistant Core has the issue? 2021.10.1 onwards ### What was the last working version of Home Assistant Core? core-2021.9.7 ### In which browser are you experiencing the issue with? Various - see above ### Which operating system are you using to run this browser? Debian Bullseye / FireOS in my own testing ### State of relevant entities ```txt n/a ``` ### Problem-relevant frontend configuration ```yaml No changes made to config.yaml to replicate this issue. Everything left as vanilla as possible to eliminate any other interactions causing the issue. (Only added HACS to get my local weather sensors into the weather card). ``` ### Javascript errors shown in your browser console/inspector ```txt nil ``` ### Additional information Happy to undertake any further testing or turn on debug logging on any device if it helps. Here is the same screenshot as above, but following a downgrade to 2021.9.7 - you'll see that local time is consistently shown. Obviously it doesn't really matter that these aren't the same - but it is an issue when time critical cards like weather forecasts are displaying UTC rather than the local time. ![Screenshot from 2021-11-02 21-56-57](https://user-images.githubusercontent.com/39319760/139834148-18043a79-be01-4652-bb52-c946dad25966.png)

Useful if people could add any further detail they have on the issue here.