-
Notifications
You must be signed in to change notification settings - Fork 7
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
time_to_full_charge showing different results? #195
Comments
Thanks for the quick response - however time AT full charge i dont see. i only have time TO full charge and that's where i think it changed. |
maybe to clarfify: Below you see the result on teslemetry: 8.25 which matches the 8hrs15minutes which i see in the official tesla app. however in HA i see: which is in fact 9minutes from now. Maybe I am just being stupid. But something must have changed |
So my guess is- but I am completely unqualified to confirm this - maybe this field before was sending minutes only, i.e. 495 minutes, and now instead it reports it as hours, i.e. 8.25. mathematically this would match my findings. Meanwhile - a huge thanks for all your hard work! Best |
Yes, I believe you are right about the minutes vs hours thing. I thought I had already fixed that but seemly not. |
Thank you so much - at least I read the information not entirely wrong then. Take your time to fix it, I've done some workaround in the meantime. And thanks again so much. Let me know if I can "buy you a coffee" in some way. Best |
Checklist
Describe the issue
Hi
I noticed that the field "time_to_full_charge" might have changed in the past couple of days. Before, this was showing the expected time by when the charging will be completed in the format of "2025-02-12T20:12:29+00:00". I noticed, that with potentially some recent changes on Teslemetry(?) this is wrong. The API result now is "time_to_full_charge": 9.25 which is probably 9hrs 15 Minutes. I think the integration however treats this as 9mins15 seconds? Do you see the same? Strangely enought, "Time_to_arrival" is still correct. I was trying to find if the API has changed but failed to find an answer.
It's the first time I am raising an issue on Github. Apologies if i missed something.
Reproduction steps
Debug logs
The text was updated successfully, but these errors were encountered: