You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using eq3bt with home assistant. Home assistant has been using UTC time internally since 2015, and hassbian is also pre-configured for UTC. There is no way to pass a time zone in to eq3bt as far as I can tell, so the times are off by the TZ difference (in my case, UTC vs CEST = 2 hours). Home Assistant configures a time zone and handles time zones correctly internally, but as it cannot pass that data to eq3bt, the thermostats get the system time (which is in UTC). As a result, all programmed schedules are off.
All methods using datetime.now would need to be extended to take a time zone parameter, or time zone could be made global. The callers need to pass in a time zone. If none is given, system timezone could still be used, but a warning should probably be given to the user.
The text was updated successfully, but these errors were encountered:
I think the the constructor could accept an optional timezone, that way it is easier to handle than adjusting it separately per method. Having a warning is also a good idea, I'm open for PRs.
I’m using eq3bt with home assistant. Home assistant has been using UTC time internally since 2015, and hassbian is also pre-configured for UTC. There is no way to pass a time zone in to eq3bt as far as I can tell, so the times are off by the TZ difference (in my case, UTC vs CEST = 2 hours). Home Assistant configures a time zone and handles time zones correctly internally, but as it cannot pass that data to eq3bt, the thermostats get the system time (which is in UTC). As a result, all programmed schedules are off.
All methods using datetime.now would need to be extended to take a time zone parameter, or time zone could be made global. The callers need to pass in a time zone. If none is given, system timezone could still be used, but a warning should probably be given to the user.
The text was updated successfully, but these errors were encountered: