-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
datetime.now() is UTC in Docker despite config #19082
Comments
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 👍 |
Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks! |
This is an issue which affects all components using INFO: I have set |
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. |
This is still an issue |
We want to use our own dt_util.now() which takes into consideration the globally set DEFAULT_TIME_ZONE
Home Assistant release with the issue:
0.83.3
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Climate/Radiotherm
Description of problem:
The radiotherm module ignore timezone configuration when setting the thermostat clock.
IE: If timezone is America/Los_Angeles but the system clock is UTC, radiotherm will set the thermostat clock to UTC.
Looks like an easy fix:
The text was updated successfully, but these errors were encountered: