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
Using the EU version, I created a (test) script which uses the "update_all_vehicles_with_cached_state()".
When I run this script multiple times quickly, one after the other, and check the results, the data is consistent and the same (as expected) but only the "registration date" differs sometimes:
It looks like one of their servers/VMs in their pool is running with a wrong timezone setting or so.
All other times are always the same (but are also in Python's datetime format, the registration_date appears to be just a string).
I have read in the issues other questions about times, maybe we cannot trust on the consistency of their platform for this. Is there any (human) communication channel with Hyundai/KIA by someone?
The text was updated successfully, but these errors were encountered:
A workaround has been made: #643 and #644
However, this is not the holy grail and indeed it would better that Hyundai/Kia fixes this. I do not have a communication channel.
Using the EU version, I created a (test) script which uses the "update_all_vehicles_with_cached_state()".
When I run this script multiple times quickly, one after the other, and check the results, the data is consistent and the same (as expected) but only the "registration date" differs sometimes:
It looks like one of their servers/VMs in their pool is running with a wrong timezone setting or so.
All other times are always the same (but are also in Python's datetime format, the registration_date appears to be just a string).
I have read in the issues other questions about times, maybe we cannot trust on the consistency of their platform for this. Is there any (human) communication channel with Hyundai/KIA by someone?
The text was updated successfully, but these errors were encountered: