frontend
frontend copied to clipboard
home-assistant
Timezones shown are wrong (Auckland)
Checklist
- [X] I have updated to the latest available Home Assistant version.
- [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.
- [X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
Timezone for Auckland was showing as +13; however, that is daylight time and was in standard time back in July 2023 (+12). Not sure where HA is sourcing time zones from but it's wrong. This isn't a recent change of our countries timezones either.
Describe the behavior you expected
Should have been showing +12.
Steps to reproduce the issue
Browse to General and then observe that the timezones are static and therefore wrong.
What version of Home Assistant Core has the issue?
core-2024.1.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
No response
Which operating system are you using to run this browser?
No response
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
Previously raised as a core issue.
This problem is not unique to Auckland. That particular picker uses the google-timezones-json package, which is labeling IANA zones with a fixed offset in northern hemisphere standard time. It also only displays in English.
However, even though the offset is wrong there, your underlying IANA zone is still correct ("Pacific/Auckland"), so times and dates elsewhere in the frontend should be correct as they have nothing to do with that package.
I will be introducing a change to get rid of that package and also display in the user's language soon.
Great news - thank you! You are right that it is recorded correctly (can see it in .storage/core.config).
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I just so that if I go to see the HassOS log... the time is corect, so is GMT+2 (Rome) But if I ask the Assist (I use ChatGPT) it tell me an hour less, so is GMT+1. Denis
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.