TeslaMate [megathread]

wayner · Feb 21, 2021

I actually get pertty much the same message from Postgres about listening on a zero IP address:

Code:

PostgreSQL Database directory appears to contain a database; Skipping initialization

2021-02-13 17:02:28.275 EST [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2021-02-13 17:02:28.275 EST [1] LOG: listening on IPv6 address "::", port 5432
2021-02-13 17:02:28.283 EST [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-02-13 17:02:28.304 EST [26] LOG: database system was shut down at 2021-02-13 17:02:27 EST
2021-02-13 17:02:28.310 EST [1] LOG: database system is ready to accept connections
2021-02-13 17:03:05.632 EST [33] LOG: incomplete startup packet
2021-02-13 17:04:05.176 EST [35] LOG: incomplete startup packet

Let me show you all of my parameters and you can see if you have the same.

Name: Postgres11
Repository: Postgres11
Network Type: Host
Privileged:OFF
POSTGRES_PASSWORD: secret
POSTGRES_USER: teslamate
POSTGRES_DB: teslamate
Database Storage Path: /mnt/cache/appdata/postgres
Web Interface Port: 5432

Name: Grafana
Repository: grafana/grafana
Network Type: Bridge (I don't know if this matters)
Privileged:OFF
Host Port 1: 3000
Host Path1: /mnt/user/appdata/grafana
Key 1: http://192.168.1.99 (IP address of my unRAID server)
Key 2: secret

Name: teslamate
Repository: teslamate/teslamate
Network Type: Bridge
Privileged: OFF
DATABASE_USER: teslamate
DATABASE_HOST: 192.168.1.99 (IP address of my unRAID server)
MQTT_HOST: 192.168.1.99 (IP address of my unRAID server which also runs a MQTT broker)
webui: 4000
import: /mnt/user/appdata/teslamate
DATABASE_NAME: teslamate
DATABASE_PASS: secret

If you click the Basic View button in the top right to go to Advanced you can then add in the following, although these are more optional (this gives you an icon and a working WebUI link from the Dashboard page)

Icon URL: https://assets.materialup.com/uploads/922c35bd-940d-4f26-bbd5-ff8b7075f53b/preview.jpg
WebUI: http://[IP]:[PORT:4000]

frankie666 · Feb 21, 2021

wayner said:

I actually get pertty much the same message from Postgres about listening on a zero IP address:

Code:

PostgreSQL Database directory appears to contain a database; Skipping initialization

2021-02-13 17:02:28.275 EST [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2021-02-13 17:02:28.275 EST [1] LOG: listening on IPv6 address "::", port 5432
2021-02-13 17:02:28.283 EST [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-02-13 17:02:28.304 EST [26] LOG: database system was shut down at 2021-02-13 17:02:27 EST
2021-02-13 17:02:28.310 EST [1] LOG: database system is ready to accept connections
2021-02-13 17:03:05.632 EST [33] LOG: incomplete startup packet
2021-02-13 17:04:05.176 EST [35] LOG: incomplete startup packet

Let me show you all of my parameters and you can see if you have the same.

Thanks a lot @wayner, much appreciated!

I have exactly the same parameters but still an issue with database - 1) "teslamate role does not exist" (postgres log) and 2) "the database does not exist" (teslamate log).

Thanks again but I give up and I will install Teslamate on a linux VM on my UNRAID.

darkNstormy · Feb 21, 2021

Had lots of trouble with missed drives and charges but the new 1.21.5 update seems to have fixed that. The changelog mentioned some issues about login tokens expiring so I think that must have kept happening. Recommend updating asap.

wayner · Feb 21, 2021

A question on upgrading - I week ago I got Teslamate up and running on my unRAID server with a bunch of custom work. I see that there is an update of the docker package. If I run the upgrade is there any risk of breaking things? Or should I likely be good.

ParHunter · Feb 22, 2021

26ct2143 said:
So if you look here:
MQTT Integration | TeslaMate
the docs say under the MQTT section, it's the health of the logger.
not exactly sure whether that means the in car logger, or a logger on the Tesla api servers for this car, or maybe the teslamate logger.

My Teslamate reports 'Health Check Failed' again. So how can I fix that? It fixes itself when I restart Teslamate so my guess is it is a bug in TeslaMate.

26ct2143 · Feb 22, 2021

ParHunter said:
My Teslamate reports 'Health Check Failed' again. So how can I fix that? It fixes itself when I restart Teslamate so my guess is it is a bug in TeslaMate.

Are you running on a Raspberry Pi or such like?
The SD cards are very susceptible to data corruption after awhile, (well a lot of the lower cost ones are).
If this is correct then the SD is going bad.
But I am guessing a bit here...

doats1 · Feb 22, 2021

ParHunter said:
My Teslamate reports 'Health Check Failed' again. So how can I fix that? It fixes itself when I restart Teslamate so my guess is it is a bug in TeslaMate.

I was getting this too with 1.21.4, but then 1.21.5 has just been released and so far so good.

init6 · Feb 22, 2021

ParHunter said:
My Teslamate reports 'Health Check Failed' again. So how can I fix that? It fixes itself when I restart Teslamate so my guess is it is a bug in TeslaMate.

There was a problem wit the Tesla API or Tesla at the weekend. Details here:

Login timeout issue · Issue #1369 · adriankumpf/teslamate

Oddbin · Feb 22, 2021

Has anyone figured out how change a price per kw/h? I added the price per kw in Teslamate but thought it was pence when it is set to £. At the time it updated all the previous entries for this location but now I can't figure out how to change them from £ to pence. I've tried removing and re-adding the geo-fence but no luck.

Oddbin · Feb 22, 2021

wayner said:
A question on upgrading - I week ago I got Teslamate up and running on my unRAID server with a bunch of custom work. I see that there is an update of the docker package. If I run the upgrade is there any risk of breaking things? Or should I likely be good.

Depends what custom work you did. As long as you don't change anything and the docker file has all the same settings then updating it shouldn't be an issue. Saying that I've had permission issues previously when updating between versions and the like so I would make a full backup just in case.

wayner · Feb 28, 2021

ParHunter said:
My Teslamate reports 'Health Check Failed' again. So how can I fix that? It fixes itself when I restart Teslamate so my guess is it is a bug in TeslaMate.

Is there any way to send a notification when you get one of these Health Check Failed issues? It would be great to get notified so that you could try to fix it.

DaveW · Feb 28, 2021

wayner said:
Is there any way to send a notification when you get one of these Health Check Failed issues? It would be great to get notified so that you could try to fix it.

If you externally host you could use uptimerobot or similar, not sure if you are hosting locally

wayner · Feb 28, 2021

I am hosting locally in a docker but the web page is (or was) still up. It was just giving the Health Check Failed error. I guess I could write a python script to grab the page and parse the html for "Health check failed" but it would be nice to have TeslaMate send you an email or other type of notification.

26ct2143 · Feb 28, 2021

Just monitor the mqtt topic and send an email

wayner · Feb 28, 2021

Does anyone know if the servers are having issues? I am getting the following errors in my logs:

2021-02-28 18:08:32.838 [error] POST https://auth.tesla.com/oauth2/v3/token -> error: "timeout" (60196.284 ms)
2021-02-28 18:08:32.838 [warn] Token refresh failed: %TeslaApi.Error{env: nil, message: "timeout", reason: :token_refresh}

goRt · Feb 28, 2021

wayner said:
Does anyone know if the servers are having issues? I am getting the following errors in my logs:

2021-02-28 18:08:32.838 [error] POST https://auth.tesla.com/oauth2/v3/token -> error: "timeout" (60196.284 ms)
2021-02-28 18:08:32.838 [warn] Token refresh failed: %TeslaApi.Error{env: nil, message: "timeout", reason: :token_refresh}

Yes the refresh headers were changed again, TM will require an update which I haven't seen I git yet

wayner · Mar 2, 2021

I updated my TeslaMate and now I am good again.

aCilnv · Mar 5, 2021

hi all,

I hire someone here can point me in the right direction:

I've installed teslamate via docker on my Synology NAS.

I can see Teslamate working fine - but when I go to the Grafana dashboard, I get an error:

"Error updating options: Metric request error"

I've googled it but cant seem to find anyone else with this issue - anyone got any pointers?

Thanks

s88ats · Mar 5, 2021

aCilnv said:
hi all,

I hire someone here can point me in the right direction:

I've installed teslamate via docker on my Synology NAS.

I can see Teslamate working fine - but when I go to the Grafana dashboard, I get an error:

"Error updating options: Metric request error"

I've googled it but cant seem to find anyone else with this issue - anyone got any pointers?

Thanks

View attachment 642329 View attachment 642330

I'm no expert by any stretch, but I used to get multiple errors like that too. IIRC it came after I updated Teslamate and most of them were from values being changed and my own 'dashboard' I created still using the old ones. I customized my grafana where I populated different panels from sections within TM so everything I find important to check is all on the one screen. I just copied the panels again which resolved my issue.

I hope that helps, if not try giving it an update;
docker-compose pull
docker-compose up -d

If that doesn't help then sorry, I'll see myself out and leave it to one of the pros here

26ct2143 · Mar 5, 2021

The changelog said there was an incompatibility and then on the latest updated the grafana had to be downgraded to make compitbile, what version you on?

TeslaMate [megathread]

Active Member

Member

Member

Active Member

Member

Member

Member

Active Member

Member

Member

Active Member

Active Member

Active Member

Member

Active Member

Active Member

Active Member

Member

Member

Member

Similar threads