Replies: 2 comments
-
I've been having the same issue as well for around a month and a half after upgrading my 2017 Model S 100D to MCU2 and HW3. The MCU upgrade + Teslamate errors seems to be a common thread based on what I've seen. Here's a screenshot from my Teslamate, which looks very similar to yours. The error in the log also seems to be identical. Were you ever able to find a solution to this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
see here #3084 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi guys. I observed a relatively high phantom drain on my 85D Model S and the state graph looks like this on a day when the vehicle is not being moved. That does not look right to me. It is a pre-FL car, but has the MCU2 upgrade (Atom based), so there is no energy save setting like on the legacy ones.
Therefore, I have attached the whole log of the 21st of January. Any insights? What am I doing wrong?
Infos about setup: Teslamate latest/greatest, ruinning in a Proxmox LXC container based on Debian Bullseye.
What concerns me are all the error messages and also teh frequent occurence of this 'stale stream data'.
Apart from that everything works fine. The vehicle and also the data logging of tesla mate.
But something keeps the car awake, which causes a concerning amount of phantom drain.
log21Jan23.txt
Beta Was this translation helpful? Give feedback.
All reactions