-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Only way I know of is to talk to support. When mine was losing 6-8% a day and showing as online/awake in TeslaMate all the time I called up and they were able to look at the more detailed logs they have and see a "buses not sleeping" issue which showed an ECU problem. Eventual fix was a replacement car computer once one became available, so if you are sure it is never sleeping over the course of, say a week, it might be worth giving them a call as Tesla have far more detailed information available than any logging app can show.
Just to put this out there in case someone is wondering how long an update of Teslamate 1.25.0 to Teslamate 1.26.1 takes on Google Cloud Platform: it took about 75 minutes (1 hour and 15 mins.) to complete the update. The virtual machine instance is running on e2-micro machine type, Intel Broadwell as the CPU platform, with about 1 GB of RAM. The first session, I closed out on the SSH on accident. Initiating a SSH session to reconnect wouldn't, and I would have to wait for the previous SSH session processes to kill itself. Second session, I was wondering why the Pulling was stuck on extracting at a certain percentage early on and not updating for minutes when compared to my first session, but saw that the CPU utilization was oscillating around 100% (or more). I decided to start all over again because normally the extraction % was updated more often when I was in the first SSH session. Third time was the charm. I just let it go regardless if the extracting process didn't update, but I saw that the CPU utilization was above the normal 5-6% that Teslamate uses.
Howdy
Did you get it to work?
Also did you try http and https version of the domain name. Cant remember what teslamate uses
Im not sure of the issue without more details. Just wanted to mention zero w2 came out and its pretty life changing.
Did some googling and found errror (Restarting (139) ) has to do with the database system not running.
Can you try the following command
docker start eclipse-mosquitto
What version of Teslamate are you running?
Have you made any changes recently? e.g. password, updates, etc.
I updated my Tesla to the most recent version 2022.4.5.17 but Teslamate has not been updated - I am on 1.25.0 but I was there last week and everything worked
Which should I check? I don't see any specific connection errors
pi_teslamate_1 logs
```
2022-03-26 18:58:07.123 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/<<ID>>/vehicle_data -> 408 (9375.434 ms)
2022-03-26 18:58:07.124 [warn] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
2022-03-26 18:58:07.124 car_id=2 [error] Error / :unknown
```
pi_grafana_1 logs
```
t=2022-03-21T16:09:47+0000 lvl=info msg="Initialized channel handler" logger=live channel=grafana/dashboard/uid/1EZnXszMk address=grafana/dashboard/uid/1EZnXszMk
t=2022-03-26T17:46:01+0000 lvl=info msg="Shutdown started" logger=server reason="System signal: terminated"
t=2022-03-26T17:46:03+0000 lvl=info msg="The state of unified alerting is still not defined. The decision will be made during as we run the database migrations" logger=settings
t=2022-03-26T17:46:03+0000 lvl=warn msg="falling back to legacy setting of 'min_interval_seconds'; please use the configuration option in the `unified_alerting` section if Grafana 8 alerts are enabled." logger=settings
t=2022-03-26T17:46:03+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2022-03-26T17:46:03+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2022-03-26T17:46:03+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2022-03-26T17:46:03+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
```
pi_mosquitto_1 logs
```
1648316758: Socket error on client TESLAMATE_302E3530333, disconnecting.
1648316763: mosquitto version 1.6.15 terminating
1648316765: mosquitto version 1.6.15 starting
1648316765: Config loaded from /mosquitto/config/mosquitto.conf.
1648316765: Opening ipv4 listen socket on port 1883.
1648316765: Opening ipv6 listen socket on port 1883.
1648316765: mosquitto version 1.6.15 running
1648316770: New connection from 172.18.0.2 on port 1883.
1648316770: New client connected from 172.18.0.2 as TESLAMATE_ID (p2, c1, k60).
```
What URL do you have in your browser?
Also how did you fix the issue you had earlier?
teslamotorsclub.com
Did you just revert back to 1.25.0?
Also how did you fix the issue you had earlier?
TeslaMate [megathread]
ok with that command: docker container list you should see the 'NAMES' at the end, mine is: teslamate_teslamate_1 so now do: docker container logs teslamate_teslamate_1 this should show the log for the container.. does it say anything interesting? ``` teslamate_1 |...
teslamotorsclub.com
Did you just revert back to 1.25.0?
Ok, here's a simple question for a linux noob:
I can do some very simple tasks, googling commands...
But how to make automatic data backups? For example: make data backup once a month and upload it once a month to cloud (google drive) or local NAS?
Many thanks in advance
I can do some very simple tasks, googling commands...
But how to make automatic data backups? For example: make data backup once a month and upload it once a month to cloud (google drive) or local NAS?
Many thanks in advance
How to perform an automated TeslaMate backup to Google Drive - TeslaEV.co.uk
You've setup the awesome TeslaMate, now let's automate the backup to Google Drive so you never lose any of that precious data!
www.teslaev.co.uk
Similar threads
