-
Notifications
You must be signed in to change notification settings - Fork 40
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
pcomfortcloud/session.py#L221 history data offset by 9 hrs - tz hardcoded to +0100 #55
Comments
Hi, how are you using this library? |
I have been using it though Home Assistant, but get the same results using
the command line pcomfortcloud from your library.
Mark
|
This issue is still causing me problems. Some further detail below, it is just after 11pm here, heating was switched on after 9pm and should expose consumption from that time. When run as distributed with hardcoded Line221 tz="+01:00":
When run with modified Line221 tz="+11:00", reflecting my timezone:
Why is the tz variable at Line221 hardcoded to +01:00 and is it possible to automatically set tz to the current system time, in my case +11:00? Output below:
My edited version:
|
Noticed my history dump for hourly and daily consumption values were 'odd', turns out they were offset by 9hrs..
Suspecting a TZ issue, I found line 221 in session.py
python-panasonic-comfort-cloud/pcomfortcloud/session.py
Line 221 in 18d4985
Changing to my timezone (tz="+10:00") seems to of fixed the offset issue for me.
It would be better for session.py to set tz from the host system, rather than using a hardcoded value.
Thanks
The text was updated successfully, but these errors were encountered: