You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
They seem pretty clear in the Readme it has a way to do fleet comparison:I've noticed that Teslalogger are publishing aggregated stats a bit like Teslafi. The relevance is I believe Teslamate originated from the same kernel as Teslalogger, and runs in the same way - a self hosted docker environment - so for me I'm now concerned that these docker environments are sending data back to a central database.
The link to see one is - teslalogger 'dot' de 'slash' firmware.php (I'm loathed to put a working link in as I have a real problem wth the idea of undermining the benefits)
I've no idea if Teslamate is doing the same, it's certainly always been assumed they didn't and I've not seen similar centralised dashboards with Tedslamate although I guess they could be feeding teslalogger, but what teslalogger are doing seems to be somewhat contrary to one of the prinary benefits of these slef hosted solutions.
Fleet Statistics
Fleet Statistics can be used by anyone without Teslalogger. To compare your degradation and charging curves with the fleet, you need a Teslalogger.
It wasn't accessing the fleet comparison, it was contributing to it. My point was more the perception that if you're self hosting a data logger on your own docker environment you may have been expecting it to be ring fenced in the way teslamate seems to be. The fact your data then leaves your docker environment and sent centrally is what seems to be missing and potentially in controvension of the EU data protection laws if it tracks in any way the location of the car.They seem pretty clear in the Readme it has a way to do fleet comparison:
GitHub - bassmaster187/TeslaLogger: TeslaLogger is a self hosted data logger for your Tesla Model S/3/X/Y. Actually it supports RaspberryPi 3B, 3B+, 4B, Docker and Synology NAS.
TeslaLogger is a self hosted data logger for your Tesla Model S/3/X/Y. Actually it supports RaspberryPi 3B, 3B+, 4B, Docker and Synology NAS. - bassmaster187/TeslaLoggergithub.com
Yes thanks - I'll keep my Teslamate running. It just surprised me, and in doing a bit of digging I've also found websites that will run Teslalogger for you for a fee thats very similar to Teslafi which seems a little odd (unless it is Teslalogger) as they do no development and just run the code and pocket the cash. I guess anyone could do that with Teslamate too, but its easy to be fooled. I had "Personal Docker = Safe as you can probably get" on one side and "Teslamate descended from Tesla Logger which Aggregates = Potentially not safe" on the other and it was uncomfortableHopefully your initial query about the origins of Teslamate have put your mind at rest.
There is another thread that deals with Teslalogger and he does mention early on that sharing is optional. I'm not going to install Teslalogger to see what the default setting is, but my rating is that you have to opt-in rather than it being the default:
Open Source Teslalogger on Raspberry / Docker with ScanMyTesla integration
How do you get it to appear on a browser screen at the moment? You must setup port forwarding in your router, so you can access it trough the browser in your Tesla.teslamotorsclub.com
It should auto restart. Easy to check by looking at the overview page.Hello everyone,
quick question :
If RaspberryPi is restarted by mistake, is it auto-logging in?, and starts normally all the services and the statistics recordings ?
If not, what is the config to force this ?
Thanks!
V 1.27.2Standard questions for any problem:
What version are you on?
Anything in the logs?
Specifically for your issue:
If MQTT is getting the data then Teslamate is getting the data, so it is either not storing it in the database or Grafana is not reading it properly.
The Mileage chart gets data from the drives table. What does your drives table look like?
Can you share an image of your drives dashboard? Would be interesting to see if anything is amiss with the parameters. Set it for a range that captures before and after the problem occurred.
Edit: Check the drive ids of the drives before and after the problem, you may have unclosed drives.
I believe there was a thread on GitHub that was referring to the database timeout and increasing that helped prevent drives from remaining open. Will try to find it. Believe it also included a script to close all open drives.Here's four views from the same date range.
Teslamate drives (lots of missing drives)
Teslamate mileage
Teslamate trip (lots of blank entries here)
Home assistant MQTT entity from teslamate `teslamate/cars/1/odometer`
I don't really know how to add drive ids to the grafana view but I can see in the drives view that they have large gaps between the drive ids in the url. In that they aren't increasing sequentially.
What would cause drives to not be closed, and how would I go about fixing this moving forward? It does seem that recent drives still aren't showing.
View attachment 937206
View attachment 937207
View attachment 937209
View attachment 937210
Ah awesome. I'll have a search on github. I'm now away from home for a week or so and don't have remote access to my teslamate, so will need to come back to it then.I believe there was a thread on GitHub that was referring to the database timeout and increasing that helped prevent drives from remaining open. Will try to find it. Believe it also included a script to close all open drives.