home-assistant / frontend

:lollipop: Frontend for Home Assistant
https://demo.home-assistant.io
Other
4.13k stars 2.81k forks source link

Time selector dropdown on history screen does not respect setting to use server time zone rather than local time zone #17427

Open n-engelhardt opened 1 year ago

n-engelhardt commented 1 year ago

Checklist

Describe the issue you are experiencing

I have my browser set to not provide time zone information to websites I'm visiting, as an anti-fingerprinting measure. As such, Home Assistant thinks that I'm in UTC time instead of the timezone that I'm actually in. I accept this, and to work around it, I set the Time Zone setting to "Use server time zone".

This works fine in most areas, but when I go to the history screen and use the date/time selector, the times listed are in the wrong timezone. The history that gets displayed shows with the correct times, and the dates/times shown in the "Start date" and "End date" boxes are correct. However, the times shown in the drop-down time selectors are not.

Describe the behavior you expected

The selector should select time using the timezone of the server when the time zone setting is set to "Use server time zone"

Steps to reproduce the issue

  1. Set your system timezone to one that's different than the server time, or set your browser to not provide timezone information to the server.
  2. Go to the profile settings, and in the "Time Zone" setting, select "User server time zone".
  3. Go to the history page.
  4. Select at least one entity to display history for.
  5. Expand the date/time picker.
  6. Note that the times displayed in the "Start date" and "End date" boxes do not match the times selected in the drop-down time selection boxes.

What version of Home Assistant Core has the issue?

2023.07.3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 115.0.3

Which operating system are you using to run this browser?

Windows 11 22H2

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

The way I'm doing the "resist fingerprinting" by going to about:config and setting "privacy.resistFingerprinting" to "true", but a more granular approach can likely be taken for testing by only setting "privacy.resistFingerprinting.testing.setTZtoUTC" to "true".

image image

chadbaldwin commented 1 year ago

Just giving this a bump since it's 2 weeks old and I don't want it getting marked as stale. I'm running into this issue as well.

github-actions[bot] commented 1 year ago

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.

n-engelhardt commented 1 year ago

This issue is still present in 2023.11.1

doggkruse commented 11 months ago

Still present in 2023.12.* when using the server timezone setting. Fingerprinting seems unrelated

github-actions[bot] commented 8 months ago

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.

n-engelhardt commented 8 months ago

Still present in 2024.3.3

github-actions[bot] commented 5 months ago

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.

tomlut commented 4 months ago

Thanks Thomas. The time/date pickers are still not respecting the profile "Use Server Time Zone" setting.

tzhist

github-actions[bot] commented 1 month ago

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.

tomlut commented 1 month ago

Still an issue 2024.10.4