TeslaMate on Synology NAS (Quick Guide)

[lyrebird]

Hi @Red Beard Ops,
Thanks for this post, it's very clear and concise, not a problem with your guide or method, unfortunately it leaves me in exactly the same situation as when I try installing TM using the SSH method.

I'm hoping that you or any other Synology & TM users might have some suggestions I can try, I've been pulling my hair out for a few weeks now trying various Internet suggestions, including yours of course.

Basically via this method and the SSH method leave me with the 4 containers running without errors apart from the TM Containers continually logging it can't connect to the Db and I assume because of this I can't connect to the TM webpage on port 4000.

Again, great guide and hoping someone might have the magic answer to help me

I'm also going to log a Ticket with Synology Support in case something is broken on my Synology Box.

Thanks,
Bob

I am facing the exact same issue where http://ip:4000 does not bring up anything, just an error: ERR_EMPTY_RESPONSE.

Have you got any solution yet?

Sponsored

 

[AlmostHuman]

I have TM running on my linux server and already collecting data for my wifes MYP. Im expecting to get my CT Oct - Nov '24.

How do I ensure to have two vehicles in the same TM instace? Just restart the container once the vehicle is added to the account? any ideas?

FYI - CT "added" to the app with just the RN# but no VIN / assignment yet- I did restart the container in this app state and nothing showed up in TM so im assuming I'll need Telsa to actually add the car to my account upon pickup and restart the container for it to work.

Yes, you just have to restart the services. Did this when we picked up the Cybertruck, already had the Model X in there. I took my laptop with me and had it connected to the house VPN before the delivery started. Once the Cybertruck showed up in the app I restarted TeslaMate and it was there! Awesome to have stats from minute 1!!

 

[AlmostHuman]

I am facing the exact same issue where http://ip:4000 does not bring up anything, just an error: ERR_EMPTY_RESPONSE.

Have you got any solution yet?

Crap it was so long ago that I did my install I truly don’t remember the specific details. Mine is also on an Ubuntu box, not directly in a Docker on my Synology. :/

Hope someone can help soon!

 

[BobA]

I am facing the exact same issue where http://ip:4000 does not bring up anything, just an error: ERR_EMPTY_RESPONSE.

Have you got any solution yet?

Hi,
Yes, just a few mins ago, but I'm not sure how 100% as either something changed on my system (unlikely) or I tried so many things over so many late nights I got in a muddle (most likely).

Anyway, I started using none default ports for the db as when I originally tried using the default 5432 it complained they were already in use, someone in another forum suggested those port settings were for external use and to remove them, I didn't really believe or understand how removing could work given the previous error and as the logs showed the db was waiting on ports I'd set up for TM to connect to, but I'm always willing to try any suggestions anyone's taken the time to offer so I removed those custom port settings and went back to the defaults and I'm back up and running at last.

To be clear I used the method on the TM website and not the guide at the start of this thread and now it's working I'm too nervous to break it, so leaving as is for now.

Regards,

Bob

 

[lyrebird]

checked the logs of the containers and found out the database gives an error:

The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.4 (Debian 16.4-1.pgdg120+1).

This is a fresh installation and I don't have any database yet. Wonder how we can solve this?

add: I changed the yml to use version 15. now database works, but teslamate has error in log:

[error] Postgrex.Protocol (#PID<0.172.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "teslamate"

I did have the DATABASE_PASS POSTGRES_PASSWORD DATABASE_PASS set to the same password. Any hint?

 

[BobA]

If all appear to match in your docker-compose.yml the only things I can think of/suggest, but again I'm no expert:
1) Is it possible that there are unprintable characters in one your password entries that you do not see, retype them?
2) If passwords provided by password Manager is it too long or contains unacceptable characters?
3) I'm not sure how the password side works, if it's dynamic on each start up or set when Db 1st created, if set at creation, have you changed it in the docker-compose.yml

 

[L3it3R]

I’ve been considering setting up a Tesla mate instance. How many vehicles can it support? I want to do some research around fleet management and I have 4 teslas to monitor currently.

 

[lyrebird]

Followed the work by marius and finally made it to work.

Marius used protainer, which is not necessary. I simply use his yaml settings when create the project, and changed the passwords. Couple things I noticed:

used postgres:14
changed the port to 20002 20003 for teslamate and database
created local folders

Hope it can help somebody who can find this post.

Thanks everyone!

 

[alindner]

Right now teslamate, for new installations, is broken by default. See:
https://github.com/teslamate-org/teslamate/issues/4233

Just need to change your docker compose to use postgres 16 instead of 17.

    image: postgres:16

Note if you made it with 17 already, will need to remove the database volume.

 

[sedetweiler]

Right now teslamate, for new installations, is broken by default. See:
https://github.com/teslamate-org/teslamate/issues/4233

Just need to change your docker compose to use postgres 16 instead of 17.

    image: postgres:16

Note if you made it with 17 already, will need to remove the database volume.

Any guidance on how to remove that old volume? I have deleted and started over a few times and can't find where this is being stored. I am getting the error that the db already exists and it is the wrong version. Would love some help here, as I am so close to finally getting this thing to work. Much appreciated!

 

[alindner]

Any guidance on how to remove that old volume? I have deleted and started over a few times and can't find where this is being stored. I am getting the error that the db already exists and it is the wrong version. Would love some help here, as I am so close to finally getting this thing to work. Much appreciated!

How is buried in that link.

This comment:
https://github.com/teslamate-org/teslamate/issues/4233#issuecomment-2382467633

 

[sedetweiler]

Thank you! I will go digging around. Cheers!

 

[sedetweiler]

Well, at least all containers are showing green now, but can't seem to connect to port 4000. Getting " ERR_EMPTY_RESPONSE " Frankly this is further than my efforts using the portainer method had gotten me, so now to buckle up and see where this is going wrong.
Teslamate process logs show "waiting for postgres at database:5432", but the database shows are ready for connections.

 

[sjordzis]

Thank you very much for the comprehensive guide.
Where do you create this?
" The second was createing the path docker/TeslaMate_CT/opt/app/import"

Sponsored