Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Open Source Teslalogger on Raspberry / Docker with ScanMyTesla integration

This site may earn commission on affiliate links.
I see some sql dump files located here, could those be used to restore my historical data?
/docker/TeslaLogger/TeslaLogger/bin/backup
Looks like I was able to delete EVERYTHING related to docker (I probably didn't need to do that) and then restore the latest DB file located in that directory using the restore option from the portal. I think I am good now.

1687919085123.png
 
  • Like
Reactions: bassmaster
Hi All.
I use Teslalogger about 3 month now and I'm very happy with it. But for about 2 weeks ago, it has begone, that my Tesla MS 2015 MCU won't go in sleep mode.
I have tried to reboot (soft, hard) the car, changed password, but nothing seems to work.
After that I have tried to suspend the teslalogger and the car is gone offline. 3 times i tried it and every time only after the teslalogger is off, the car can go offline (sleep).
The teslalogger is always cycling this log:
02.12.2023 20:21:26 : #1[Car_1:19]: Waiting for car to go to sleep 18
02.12.2023 20:21:46 : #1[StreamAPIThread_1:2253]: shift_state: Power: 0 Datetime: 02.12.2023 20:21:43

02.12.2023 20:22:26 : #1[Car_1:19]: Waiting for car to go to sleep 19
02.12.2023 20:22:40 : #1[StreamAPIThread_1:2253]: shift_state: Power: 0 Datetime: 02.12.2023 20:22:36

02.12.2023 20:23:11 : #1[StreamAPIThread_1:2253]: Stream: Timeout
02.12.2023 20:23:26 : #1[Car_1:19]: Waiting for car to go to sleep 20
02.12.2023 20:23:27 : #1[StreamAPIThread_1:2253]: shift_state: Power: 0 Datetime: 02.12.2023 20:23:24

02.12.2023 20:24:21 : #1[StreamAPIThread_1:2253]: shift_state: Power: 0 Datetime: 02.12.2023 20:24:16

I think the steamapi is preventing the car to go to sleep. This was before the 2 week no problem.
So, my question: has Tesla changed something in this api?

P.S. Sorry for my english!
 
Hello. Newbie question here. I accidentelly wrote 80 in the teslalogger http port column in the settings portal and saved it. And know i only get this, and i cant change anything, anyone who have an idea what i should do?
 

Attachments

  • IMG_2447.jpeg
    IMG_2447.jpeg
    266.1 KB · Views: 12
Hello. Newbie question here. I accidentelly wrote 80 in the teslalogger http port column in the settings portal and saved it. And know i only get this, and i cant change anything, anyone who have an idea what i should do?
I did the same thing at one point, so don't feel too bad (I'm a linux/docker noob myself). Are you using a Snyology docker container?

I think what I did to restore it was
  1. Log into your Synology
  2. Open the "File Station" app
  3. Browse to /docker/TeslaLogger/TeslaLogger/www/admin
  4. Right click on settings.php, open with text editor
  5. Look for the HTTP port of 80, and change it to the default 5000
  6. Save and you should be able to restart the docker container and be good.
1708965227814.png


Hopefully that works for you. I made that mistake a long time ago and I think that is what the fix was.
 
I did the same thing at one point, so don't feel too bad (I'm a linux/docker noob myself). Are you using a Snyology docker container?

I think what I did to restore it was
  1. Log into your Synology
  2. Open the "File Station" app
  3. Browse to /docker/TeslaLogger/TeslaLogger/www/admin
  4. Right click on settings.php, open with text editor
  5. Look for the HTTP port of 80, and change it to the default 5000
  6. Save and you should be able to restart the docker container and be good.
View attachment 1022102

Hopefully that works for you. I made that mistake a long time ago and I think that is what the fix was.
Thanks, this is how it looks in my settings, think it looks ok.Its a raspberry pi. Not sure were i should look.