TeslaMate [megathread]

[zknobody]

How long does it wake up for and how often? An status graph would be handy.

parked the car at 22:00
the vehicle woke up 3 times so far, all for under 13mins

i never had this problem before, not sure if the updated version really has anything to do with it
i doubt my wife is launching the Tesla app on her phone because most of the time this happens in the early hours

i'm still on 2023.44.30.8
I did reboot the MCU and docker since the upgrade

 

[touchton]

parked the car at 22:00
the vehicle woke up 3 times so far, all for under 13mins

My car typically wakes up two or three times a night for about 30 minutes each time. It's done that well over a year now. I assumed that was normal behavior.

 

[init6]

Sub 15 minutes wake up are nothing new. You seem to get them in batches and then they go away again. You can check the status graph for past time periods to see if this has happened before.
Edit: This has nothing to do with Teslamate.

 

[Blokie]

My TM installation (on Google Cloud free tier) has been working flawlessly for over 3 years, until this morning......

I spotted there was a TM update available, so did my usual update procedure:

Login to my GCP instance via SSH
sudo docker-compose down
sudo docker-compose pull
sudo docker-compose up -d

..however I am now getting Bad Gateway as opposed to my TM page. It's definitely somewhat up, as it asks me for my TM username and password which authenticates correctly, but then I just get the Bad Gateway presented. I've stopped and started services, even did a full reboot of the server, but same result.

I'm suspecting something related to postgres based on the outputs from docker-compose ps, as the db seems to be in a restartiung/up loop:

Tue Feb 13 12:40:13 UTC 2024
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Restarting
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

my_instance@tm-f1-micro:~$ date;sudo docker-compose ps
Tue Feb 13 13:05:13 UTC 2024
Name Command State Ports
------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Up 5432/tcp
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

my_instance@tm-f1-micro:~$ date;sudo docker-compose ps
Tue Feb 13 13:07:23 UTC 2024
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Restarting
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

 

[init6]

What do the logs say?

 

[Blokie]

Thanks for the reply init6 - I spotted it was a space issue - / had run out!

/var/cache/apt/archives was the culprit - had built-up to over 13G over the last 3 years.

Ran sudo apt-get clean to sort and gave it a reboot - came up straight away.

 

[shyboy]

My TM installation (on Google Cloud free tier) has been working flawlessly for over 3 years, until this morning......

I spotted there was a TM update available, so did my usual update procedure:

Login to my GCP instance via SSH
sudo docker-compose down
sudo docker-compose pull
sudo docker-compose up -d

..however I am now getting Bad Gateway as opposed to my TM page. It's definitely somewhat up, as it asks me for my TM username and password which authenticates correctly, but then I just get the Bad Gateway presented. I've stopped and started services, even did a full reboot of the server, but same result.

I'm suspecting something related to postgres based on the outputs from docker-compose ps, as the db seems to be in a restartiung/up loop:

Tue Feb 13 12:40:13 UTC 2024
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Restarting
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

my_instance@tm-f1-micro:~$ date;sudo docker-compose ps
Tue Feb 13 13:05:13 UTC 2024
Name Command State Ports
------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Up 5432/tcp
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

my_instance@tm-f1-micro:~$ date;sudo docker-compose ps
Tue Feb 13 13:07:23 UTC 2024
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------
my_instance_database_1 docker-entrypoint.sh postgres Restarting
my_instance_grafana_1 /run.sh Up 3000/tcp
my_instance_mosquitto_1 /docker-entrypoint.sh /usr ... Up 127.0.0.1:1883->1883/tcp
my_instance_portainer_1 /portainer -H unix:///var/ ... Up 8000/tcp, 0.0.0.0:9000->9000/tcp, 9443/tcp
my_instance_proxy_1 /entrypoint.sh --global.se ... Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
my_instance_teslamate_1 tini -- /bin/sh /entrypoin ... Up 4000/tcp

Do you TM on Google Kubernetes Engine or just on compute?
can you write a tutorial and link it here?

TIA

 

[init6]

There's already a guide. Let me google that for you...

 

[init6]

There you go:

How to setup and run TeslaMate for free on Google Cloud - TeslaEV.co.uk

A guide on how to install and run TeslaMate in GCP (Google Cloud) for free. Use the excellent TeslaMate data logger in the cloud for £0

www.teslaev.co.uk

I would have been quicker but the forum forces a pause between posts

 

[Olyts]

Stealing @init6 thunder here. What do the logs say?

2024/02/10 19:31:52,stdout, (phoenix_live_view 0.17.14) lib/phoenix_live_view/diff.ex:494: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/7
2024/02/10 19:31:52,stdout, (teslamate 1.28.3) lib/teslamate_web/live/car_live/summary.html.heex:157: anonymous fn/2 in TeslaMateWeb.CarLive.Summary.render/1
2024/02/10 19:31:52,stdout,"2024-02-11 00:31:52.738 [error] #PID<0.2783.0> running TeslaMateWeb.Endpoint (connection #PID<0.2770.0>, stream id 4) terminated
2024/02/10 19:31:52,stdout, (timex 3.7.11) lib/format/datetime/formatter.ex:55: Timex.Format.DateTime.Formatter.lformat!/4
2024/02/10 19:31:52,stdout,"2024-02-11 00:31:52.738 [error] #PID<0.2783.0> running TeslaMateWeb.Endpoint (connection #PID<0.2770.0>, stream id 4) terminated

 

[init6]

@cwanja we need to be more specific

What do the teslamate logs say?

 

[Olyts]

@cwanja we need to be more specific

What do the teslamate logs say?

Nothing at the time I observe the “500 error”. These before and after in the log

docker-teslamate-1 | 2024-02-10 18:37:39.151 [notice] :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}

docker-teslamate-1 | 2024-02-10 22:01:57.217 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}

 

[init6]

Where do you get the Error 500? On the teslamate page or a grafana dashboard?

 

[Olyts]

Where do you get the Error 500? On the teslamate page or a grafana dashboard?

Teslamate home page, grafana is fine.

 

[cwanja]

Teslamate home page, grafana is fine.

Open an issue on GitHub. Since you said it’s only when you are charging, my gut tells me the new feature of estimated time to completion is throwing the ISE. Plus the errors reference DateTime.

Tag #3646 and @NirKli in your post.

 

[cwanja]

Also @Olyts, what is your timezone environment variable set to? Reference:

TZ environment variable name confusion · Issue #3678 · teslamate-org/teslamate

I don't know why or how your reply explains my confusion. The fact is using "TZ=" was not enough but instead a line with "TM_TZ=" works yet is not in the documentation written as "TM_TZ=". Am I jus...

github.com

WebView crashes while charging, if time_zone_not_found · Issue #3651 · teslamate-org/teslamate

Is there an existing issue for this? I have searched the existing issues What happened? When charging the car, the web interface report "Internal Server Error". Stopping the charge cause Teslamate ...

github.com

Environment Variables | TeslaMate

TeslaMate accepts the following environment variables for runtime configuration:

docs.teslamate.org

 

[Olyts]

Also @Olyts, what is your timezone environment variable set to? Reference:

TZ environment variable name confusion · Issue #3678 · teslamate-org/teslamate

I don't know why or how your reply explains my confusion. The fact is using "TZ=" was not enough but instead a line with "TM_TZ=" works yet is not in the documentation written as "TM_TZ=". Am I jus...

github.com

WebView crashes while charging, if time_zone_not_found · Issue #3651 · teslamate-org/teslamate

Is there an existing issue for this? I have searched the existing issues What happened? When charging the car, the web interface report "Internal Server Error". Stopping the charge cause Teslamate ...

github.com

Environment Variables | TeslaMate

TeslaMate accepts the following environment variables for runtime configuration:

docs.teslamate.org

Will Check that, thanks for the info!

 

[Olyts]

Will Check that, thanks for the info!

Wow, changing variable name from TZ to TM_TZ fixed it. Thanks again!

 

[MrFixit1094]

First, I want to thank everyone who has been willing to step up and provide support since Adrian moved on to other things.
TeslaMate is an awesome program. I have been using it for around 6 months since we got our Tesla. It is running on a dedicated Raspberry Pi 4.
I would like to get to the point where I could assist too, but I currently know nothing about Elixir or Docker so I am at the beginning of a learning curve.

I am a little confused by these recent Teslamate API issues. I have been running 1.28.2 with no problems. I am aware that 1.28.3 is now available which incorporates a fix for the API change. But, I have re-started (just re-started again a couple of hours ago) and TeslaMate continues to work just fine for me. My impression was that it would work with the old version until it was re-started and then it would break,

Am I missing something? Should I update even though it does not appear that I need to right now?

 

[spooksman]

First, I want to thank everyone who has been willing to step up and provide support since Adrian moved on to other things.
TeslaMate is an awesome program. I have been using it for around 6 months since we got our Tesla. It is running on a dedicated Raspberry Pi 4.
I would like to get to the point where I could assist too, but I currently know nothing about Elixir or Docker so I am at the beginning of a learning curve.

I am a little confused by these recent Teslamate API issues. I have been running 1.28.2 with no problems. I am aware that 1.28.3 is now available which incorporates a fix for the API change. But, I have re-started (just re-started again a couple of hours ago) and TeslaMate continues to work just fine for me. My impression was that it would work with the old version until it was re-started and then it would break,

Am I missing something? Should I update even though it does not appear that I need to right now?

I’m pretty much in the same position - everything is fine on 1.28.2, and I’ve avoided updating as I’m really not sure what will happen. The biggest difference is mine hasn’t restarted recently…

Interested in the replies…