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 Zeddy with a Renault Zoe R110 ZE50 (2020) and first of all: The charge history seems to work just fine. I do get "-- Charges" and "-- on charge", and also, it usually takes a few seconds with a black screen until the charge history shows up (so, a little "loading" animation would help ... I also need to still implement that for the highscore lists in our game, lalala ;-) ).
But other than that, it all looks correct.
As we have only had the car for about a week (first charge was 2021-02-27), I don't know if Renault still deletes the charge history ... if so, I'd appreciate it being persistent in the app (it's my favorite feature of the app).
One thing that I'm missing is the amount of charged kWh. I could probably calculate that by either using the charged percentage (55% -> 63% would probably be 8% of 52 kWh, so that should be 4,16 kWh), or speed * duration (14 minutes, 19 kW would be 4.43 kWh) ... but why let a human do things that machines do so much better. Not sure if the API maybe even delivers the charged amount of kWh, or if the numbers delivered by the API are more precise than what is displayed.
The text was updated successfully, but these errors were encountered:
I'm using Zeddy with a Renault Zoe R110 ZE50 (2020) and first of all: The charge history seems to work just fine. I do get "-- Charges" and "-- on charge", and also, it usually takes a few seconds with a black screen until the charge history shows up (so, a little "loading" animation would help ... I also need to still implement that for the highscore lists in our game, lalala ;-) ).
But other than that, it all looks correct.
As we have only had the car for about a week (first charge was 2021-02-27), I don't know if Renault still deletes the charge history ... if so, I'd appreciate it being persistent in the app (it's my favorite feature of the app).
One thing that I'm missing is the amount of charged kWh. I could probably calculate that by either using the charged percentage (55% -> 63% would probably be 8% of 52 kWh, so that should be 4,16 kWh), or speed * duration (14 minutes, 19 kW would be 4.43 kWh) ... but why let a human do things that machines do so much better. Not sure if the API maybe even delivers the charged amount of kWh, or if the numbers delivered by the API are more precise than what is displayed.
The text was updated successfully, but these errors were encountered: