-
Hi guys I have been running TeslaMate for some months now and am quite happy with it, very nice tool for geek'ing out with stats. :-) Unfortunately it has stopped updating the data, that is I can access the web site and it all looks to be working perfectly fine but none of the drives, charges, status etc. is being updated. I'm uncertain if it's a issue here at my installation or something in general. I had some unfortunate power failures earlier this week, with some network/ntp/etc. issues to follow, maybe that has corrupted something in TeslaMate? I have rebooted, pulled new version, restarted docker etc. but it didn't really make any changes. I have just now attempted a complete reinstall of the docker images, where I stopped and removed all containers and images, then did a new pull request, ran "docker-compose up -d", stopped teslamate and restored backup (according to guide on backup and restore page) and then started teslamate again. I noticed this in the teslamate log Any recommendations on what logfiles to look closer at? Any ideas on how to get TeslaMate working (right) again? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Pardon my french, but suck me sideways... I was just out shopping and now that I came back I can see the drive and everything else. So apparently it started working again, maybe the drive triggered something in the Tesla cloud, maybe it wasn't enough just to wake the car from the app? Anyways, I'm still uncertain what made this go wrong in the first place, but it might have been some kind of corruption in the database or expired token or whatever. AND... keep up the good work with TeslaMate, it's a fantastic tool. |
Beta Was this translation helpful? Give feedback.
Pardon my french, but suck me sideways...
I was just out shopping and now that I came back I can see the drive and everything else. So apparently it started working again, maybe the drive triggered something in the Tesla cloud, maybe it wasn't enough just to wake the car from the app?
Anyways, I'm still uncertain what made this go wrong in the first place, but it might have been some kind of corruption in the database or expired token or whatever.
AND... keep up the good work with TeslaMate, it's a fantastic tool.