Replies: 1 comment 6 replies
-
|
Definitely lost previous charges data. There's no way to backfill. But pull the database and TeslaMate logs at the expected timestamps plus an hour before. Edit: Edited for clarity. |
Beta Was this translation helpful? Give feedback.
6 replies
-
Typos. My fault. Edited for clarity. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, a bit confused. Can you give me a summarization of the timeline? What happened between 1:08 and 3? There is nearly a two hour gap. Why? If Docker is offline, the service is not running. Thus no data is being polled and stored. And there's no backfill way to fill your data. |
Beta Was this translation helpful? Give feedback.
-
|
Between 1:08 and 2:13 there are no entries on the log, I am guessing simply no events received from the API, nor anything else happened. At 2:13 the docker container has been shut down for a RPI backup, and brought back up at 3:00. So that backup is the most likely culprit. I did not realise there was no "recovery" in the streaming API (coming from financial background, it's certainly not how I would design any feed, but it is what it is). I have now disabled the shutting down of docker for the backup, hopefully that should fix it. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
I had to delete the comment with the log due to it containing some personal info, re-posting it here: @cwanja So this happened again. Docker was restarted around this time (to perform raspberry PI backup) and also there are a lot of API timeout errors, which I can see are very common. I am not aware of how the API works - can the data be lost because of docker restart and/or these API timeouts? I suspect the restart is the culprit, as TeslaMate was offline for 47 minutes, and the events are somehow not recoverable? Here's the UI, the SoC jumps from 48% to 66%. There are multiple charging sessions because charging is controlled by ev.energy trying to only charge when electricity is cheap (prices change every 30 mins). teslamate logs: |
Beta Was this translation helpful? Give feedback.
-
|
If Docker is not running, no data is being pulled. Thus the gaps you are seeing. I should mention, I am sure there is a a way to backfill the data. Tesla does not make that available via this unofficial API. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have not been checking this frequently, but starting at some point in the past, I can see some uninterrupted charge sessions shown in the "charges" graphana panel as starting at a time that's a few hours later than the actual start time, and the start percent value wrong. For example I know the car started charging at 2:30am beginning with 19% SoC and continued till 7:00am till say 66% SoC. the row in Graphana shows stat time 4:10am and start percentage 30%. The end percentage and end time are correct. How do I diagnose this? Running in docker. Just upgraded so I think I have lost all the previous logs.
Beta Was this translation helpful? Give feedback.
All reactions