-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Nope. Once you input your tokens to TeslaMate, you are good.
Nothing short of simply dropping the database and starting fresh. That size for two years of ownership sounds about right. It all depends on how much you drive. Curious, what is your mileage in those two years?
thanks, would that make any difference to the size? Actually 1.6 years, got the car March 22, on 21k miles.
Yes it records the position of the car when you are driving (or parked and not asleep). So more mileage = more records in the position table.
If you start with a fresh database and "archive" the current state, yes as the database would be zero. But you lose looking at the archived data in Grafana. Give and take. What are you running TeslaMate on? And is storage a concern?
Also what @init6 said
3.1GB since September 2019. So sounds about right. 93k miles on odometer.
paulkva
part of the supercharge.info dev team
My TeslaMate DB backups are ~1.2GB each, but the scheduled backup job that I set up runs gzip after grabbing it, and it's only 145MB compressed.
paulkva
part of the supercharge.info dev team
I'm running Teslamate in containers on Linux via
docs.teslamate.org
To run it regularly, I simply have that line in an executable shell script in
I have a separate daily script that copies the .gz file (and a bunch of other stuff) to a different computer on my local network, which in turn has its own (more robust) backup capability. Storage isn't a big concern for me, but I figured the uncompressed file will continue to grow quickly, and the extra compute power required to gzip is relatively small.
Note that the restore command would also be slightly different from what's in the documentation:
And of course those code snippets expect that
docker-compose. My script is just a slight variation of the command shown in the documentation:Backup and Restore | TeslaMate
If you are using docker-compose, you are using Docker Compose v1, which has been deprecated. Docker Compose commands refer to Docker Compose v2. Consider upgrading your docker setup, see Migrate to Compose V2
docs.teslamate.org
Code:
docker-compose exec -T database pg_dump -U teslamate teslamate | gzip > /backuplocation/teslamate-db.gzTo run it regularly, I simply have that line in an executable shell script in
/etc/cron.daily. Until recently, I was running Docker on Windows, where my backup job was a very similar Powershell script set up to run as a Scheduled Task. (Notably, I verified that my backup & restore processes worked when I moved Teslamate from one computer to the other.)I have a separate daily script that copies the .gz file (and a bunch of other stuff) to a different computer on my local network, which in turn has its own (more robust) backup capability. Storage isn't a big concern for me, but I figured the uncompressed file will continue to grow quickly, and the extra compute power required to gzip is relatively small.
Note that the restore command would also be slightly different from what's in the documentation:
Code:
gunzip /restorelocation/teslamate-db.gz | docker-compose exec -T database psql -U teslamate -d teslamateAnd of course those code snippets expect that
docker-compose and gzip and gunzip are in your executable path.yeah don't want to lose data! I'm on a Pi, no issues with space there, but I move it to a free Dropbox account that has limited space, the gzip solution adding to my script seems the perfect answer.
This is the script I've been using (seems to have gone from it's origional home) Automatic Backup to Dropbox on Raspberry Pi Tutorial (archive.org)
Thank you!I'm running Teslamate in containers on Linux viadocker-compose. My script is just a slight variation of the command shown in the documentation:
Backup and Restore | TeslaMate
If you are using docker-compose, you are using Docker Compose v1, which has been deprecated. Docker Compose commands refer to Docker Compose v2. Consider upgrading your docker setup, see Migrate to Compose V2Code:docker-compose exec -T database pg_dump -U teslamate teslamate | gzip > /backuplocation/teslamate-db.gz
To run it regularly, I simply have that line in an executable shell script in/etc/cron.daily. Until recently, I was running Docker on Windows, where my backup job was a very similar Powershell script set up to run as a Scheduled Task. (Notably, I verified that my backup & restore processes worked when I moved Teslamate from one computer to the other.)
I have a separate daily script that copies the .gz file (and a bunch of other stuff) to a different computer on my local network, which in turn has its own (more robust) backup capability. Storage isn't a big concern for me, but I figured the uncompressed file will continue to grow quickly, and the extra compute power required to gzip is relatively small.
Note that the restore command would also be slightly different from what's in the documentation:
Code:gunzip /restorelocation/teslamate-db.gz | docker-compose exec -T database psql -U teslamate -d teslamate
And of course those code snippets expect thatdocker-composeandgzipandgunzipare in your executable path.
paulkva
part of the supercharge.info dev team
I'm running Home Assistant within the same instance of Docker as TeslaMate, but I don't integrate the two directly with each other. Instead I'm using the "Tesla Custom Integration" component via HACS:
GitHub - alandtse/tesla: Tesla custom integration for Home Assistant. This requires a refresh token be generated by third-party apps to login.
Tesla custom integration for Home Assistant. This requires a refresh token be generated by third-party apps to login. - GitHub - alandtse/tesla: Tesla custom integration for Home Assistant. This re...
github.com
TeslaMate docs do include instructions on Home Assistant integration via MQTT, but I haven't tried it:
HomeAssistant Integration | TeslaMate
Whilst HomeAssistant provides an official component for Tesla vehicles, the component has not been updated recently, and does not have the sophistication of TeslaMate's polling mechanism, resulting in the component's default values keeping the vehicle awake and draining the battery.
docs.teslamate.org
And it looks like there's a custom Home Assistant add-on for TeslaMate, which can't be used when running HA in Docker, so I haven't tried that either:
GitHub - matt-FFFFFF/hassio-addon-teslamate: Teslamate addon for Home Assistant
Teslamate addon for Home Assistant. Contribute to matt-FFFFFF/hassio-addon-teslamate development by creating an account on GitHub.
github.com
Zilla91
Active Member
Can anyone explain how to use Teslamate/Grafana with two cars? Dashboard only seems to show data for one car and I can't find anywhere to select the other car even though both show up on the Teslamate homepage
Thats odd as I get my old car and my current car on the dashbaords, one below the other. I had to google how to deleted my old car which involved executing a SQL command.
Zilla91
Active Member
That's what I get on Grafana. Can't see any option to select a specific car.
Teslamate does definitely see both cars
Similar threads
