TeslaMate [megathread]

robbo100 · Apr 2, 2022

Hi all,

I have managed to completely destroy my Raspberry Pi Teslamate install, but updating to the latest version, before installing Bullseye. I have now updated to bullseye, but it is a mess, with a horrendous log file, with hundreds of lines saying: "teslamate_1 | waiting for postgres at database:5432"

Does anyone know the best way to completely remove the teslamate install, so I can start again and reinstate my last good backup?

Thanks

init6 · Apr 2, 2022

robbo100 said:
Hi all,

I have managed to completely destroy my Raspberry Pi Teslamate install, but updating to the latest version, before installing Bullseye. I have now updated to bullseye, but it is a mess, with a horrendous log file, with hundreds of lines saying: "teslamate_1 | waiting for postgres at database:5432"

Does anyone know the best way to completely remove the teslamate install, so I can start again and reinstate my last good backup?

Thanks

How to uninstall and delete everything? · teslamate-org teslamate · Discussion #1125

Does anyone have instructions on how to cleanly 'uninstall' Teslamate from a Docker setup? I have decided not to use TeslaMate anymore and would like to remove all containers and would like to be s...

github.com

acatwith12 · Apr 2, 2022

init6 said:
Weird. What commands did you use to restart the services & docker? Did you try a reboot before pulling the power? That's a better way to restart.

I tried `docker restart $(docker ps -q)` was that correct?

robbo100 · Apr 2, 2022

Thanks @init6

I don't know what I have done to be honest. I have deleted by teslamate files, and started from scratch, but I still have the issue with not being able to connect to port 4000. The log file just says: "[36mteslamate_1 |[0m waiting for postgres at db:5432"

Any suggestions

init6 · Apr 2, 2022

acatwith12 said:
I tried `docker restart $(docker ps -q)` was that correct?

I usually just use docker-compose down followed by docker-compose up -d

init6 · Apr 2, 2022

robbo100 said:
Thanks @init6

I don't know what I have done to be honest. I have deleted by teslamate files, and started from scratch, but I still have the issue with not being able to connect to port 4000. The log file just says: "[36mteslamate_1 |[0m waiting for postgres at db:5432"

Any suggestions

Let's start from the beginning.

Did you upgrade to bullseye or do a fresh install?
What versions of Teslamate have you installed?
Have you upgraded the DB separately? (IIRC there was a problem a while back where a newer version of the DB corrupted some of the teslamate components)

can you show us the results of a docker ps please?

and the contents of your docker-compose.yml please.

acatwith12 · Apr 2, 2022

init6 said:
I usually just use docker-compose down followed by docker-compose up -d

Looking through my command history I used those too! Do you think `sudo reboot` would work?

robbo100 · Apr 3, 2022

init6 said:
Let's start from the beginning.

Did you upgrade to bullseye or do a fresh install?

I did an update, using this guide: The Idiot-Proof Guide to Upgrading Raspberry Pi from Buster to Bullseye

Code:

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

What versions of Teslamate have you installed?

I have pulled the latest version using "docker-compose pull", so I am assuming it is 1.26.1. I have manually set the version to "1.26.1" in the docker-compose.vml, rather than "latest" because I had read that this was a work-around for some issues with the update.

Have you upgraded the DB separately? (IIRC there was a problem a while back where a newer version of the DB corrupted some of the teslamate components)

No, I haven't done this.

can you show us the results of a docker ps please?

Code:

CONTAINER ID   IMAGE                        COMMAND                  CREATED         STATUS                          PORTS                                       NAMES
2a8937624062   postgres:13                  "docker-entrypoint.s…"   3 minutes ago   Restarting (1) 25 seconds ago                                               pi_database_1
2324a67f94f7   teslamate/grafana:latest     "/run.sh"                3 minutes ago   Up 3 minutes                    0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   pi_grafana_1
a203d0baf9ed   eclipse-mosquitto:2          "/docker-entrypoint.…"   3 minutes ago   Up 3 minutes                    1883/tcp                                    pi_mosquitto_1
577ffc11af72   teslamate/teslamate:1.26.1   "tini -- /bin/sh /en…"   3 minutes ago   Up 3 minutes                    0.0.0.0:4000->4000/tcp, :::4000->4000/tcp   pi_teslamate_1

and the contents of your docker-compose.yml please.

Code:

version: "3"

services:
  teslamate:
    image: teslamate/teslamate:1.26.1
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
    cap_drop:
      - all

  database:
    image: postgres:13
    restart: always
    environment:
      - POSTGRES_USER=teslamate
      - POSTGRES_PASSWORD=secret
      - POSTGRES_DB=teslamate
    volumes:
      - teslamate-db:/var/lib/postgresql/data

  grafana:
    image: teslamate/grafana:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
    ports:
      - 3000:3000
    volumes:
      - teslamate-grafana-data:/var/lib/grafana

  mosquitto:
    image: eclipse-mosquitto:2
    restart: always
    command: mosquitto -c /mosquitto-no-auth.conf
    # ports:
    #   - 1883:1883
    volumes:
      - mosquitto-conf:/mosquitto/config
      - mosquitto-data:/mosquitto/data

volumes:
  teslamate-db:
  teslamate-grafana-data:
  mosquitto-conf:
  mosquitto-data:

Thanks again @init6 for your help with this, I really appreciate it.

init6 · Apr 3, 2022

robbo100 said:

Code:

CONTAINER ID   IMAGE                        COMMAND                  CREATED         STATUS                          PORTS                                       NAMES
2a8937624062   postgres:13                  "docker-entrypoint.s…"   3 minutes ago   Restarting (1) 25 seconds ago                                               pi_database_1
2324a67f94f7   teslamate/grafana:latest     "/run.sh"                3 minutes ago   Up 3 minutes                    0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   pi_grafana_1
a203d0baf9ed   eclipse-mosquitto:2          "/docker-entrypoint.…"   3 minutes ago   Up 3 minutes                    1883/tcp                                    pi_mosquitto_1
577ffc11af72   teslamate/teslamate:1.26.1   "tini -- /bin/sh /en…"   3 minutes ago   Up 3 minutes                    0.0.0.0:4000->4000/tcp, :::4000->4000/tcp   pi_teslamate_1

Looks like your database isn't starting, hence Teslamate will get errors.
What do you see in the db logs?

docker-compose logs database

init6 · Apr 3, 2022

acatwith12 said:
Looking through my command history I used those too! Do you think `sudo reboot` would work?

sudo reboot will restart the whole computer so should shut things down more cleanly.

init6 · Apr 3, 2022

robbo100 said:
I did an update, using this guide: The Idiot-Proof Guide to Upgrading Raspberry Pi from Buster to Bullseye

Just read this guide. What did you do when you got to this part:

Upgrading Caveats
Before you begin, I can’t stress enough that the best (and frankly, supported) way to upgrade to Bullseye is to backup all of your critical files and perform a clean install using the Raspberry Pi Imager. However, if you’re like me and choose to live dangerously, be sure to backup your files anyway and buckle up for the ride.

Did you do the clean install or buckle up?

robbo100 · Apr 3, 2022

init6 said:
Did you do the clean install or buckle up?

I buckled up and crossed my fingers!

Will post logs in a bit.

init6 · Apr 3, 2022

robbo100 said:
I buckled up and crossed my fingers!

Will post logs in a bit.

If they're big feel free to DM them to me.

robbo100 · Apr 3, 2022

init6 said:
If they're big feel free to DM them to me.

Not much in there, basically a continual repeat of this:

Code:

Attaching to pi_database_1
[36mdatabase_1   |[0m
[36mdatabase_1   |[0m PostgreSQL Database directory appears to contain a database; Skipping initialization
[36mdatabase_1   |[0m
[36mdatabase_1   |[0m 2022-04-03 07:16:58.321 UTC [1] FATAL:  database files are incompatible with server
[36mdatabase_1   |[0m 2022-04-03 07:16:58.321 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 13.6 (Debian 13.6-1.pgdg110+1).

robbo100 · Apr 3, 2022

I presume I need to follow this: Upgrading PostgreSQL to a new major version | TeslaMate

But I am unsure if this line should have any substituted parameters, or if I literally copy and past it exactly as it is, into the terminal?

Code:

docker volume rm "$(basename "$PWD")_teslamate-db"

init6 · Apr 3, 2022

robbo100 said:
I presume I need to follow this: Upgrading PostgreSQL to a new major version | TeslaMate

But I am unsure if this line should have any substituted parameters, or if I literally copy and past it exactly as it is, into the terminal?

Code:

docker volume rm "$(basename "$PWD")_teslamate-db"

Yes, I think so. For obvious reasons I don't want to try that command

robbo100 · Apr 3, 2022

@init6 - AMAZING

Thanks for your help. I had to do a little bit more fiddling, but after running that update of the PostgreSQL, it has all come back to life again. My last backup was on Friday night at 03:00, so I have missed out on collecting a couple of days of data, but in the grand scheme of things, no harm done.

Cheers

w3zly · Apr 3, 2022

Hey guys,
So I've had to re-setup Teslamate on my Raspberry Pi from scratch -which is all done and working, however, now i am trying to setup the Gdrive backups using Dave's guide on How to perform an automated TeslaMate backup to Google Drive - TeslaEV.co.uk

I'm running into an issue where it will not start the web browser to create the token (on the step highlighted below). I have even tried to launch a web browser and point to http://127.0.0.1:53682/auth but again, I get a page not found error

Any ideas where i'm going wrong? i've done this directly on the Pi and also tried via ssh on another computer. Same issue

init6 · Apr 3, 2022

w3zly said:
Hey guys,
So I've had to re-setup Teslamate on my Raspberry Pi from scratch -which is all done and working, however, now i am trying to setup the Gdrive backups using Dave's guide on How to perform an automated TeslaMate backup to Google Drive - TeslaEV.co.uk

I'm running into an issue where it will not start the web browser to create the token (on the step highlighted below). I have even tried to launch a web browser and point to http://127.0.0.1:53682/auth but again, I get a page not found error

Any ideas where i'm going wrong? i've done this directly on the Pi and also tried via ssh on another computer. Same issue

View attachment 789622

Does your pi have a browser installed?

Edit: I ran the commands on my teslamate server and then ran the rclone authorise command on my mac. This fired up a browser window which let me continue with the instructions.

See also:

Remote Setup

Configuring rclone up on a remote / headless machine

rclone.org

w3zly · Apr 3, 2022

init6 said:
Does your pi have a browser installed?

Edit: I ran the commands on my teslamate server and then ran the rclone authorise command on my mac. This fired up a browser window which let me continue with the instructions.

See also:

Remote Setup

Configuring rclone up on a remote / headless machine

rclone.org

Hi init6, yep, Pi has a browser installed, but still wont auto launch the browser. Sorry im a newbie to this - How do i run the rclone authorise command on my PC? what program am i using to do that? if you have step by step for that part i would really appreciate that

TeslaMate [megathread]

Member

Active Member

Member

Member

Active Member

Active Member

Member

Member

Active Member

Active Member

Active Member

Upgrading Caveats​

Member

Active Member

Member

Member

Active Member

Member

Member

Active Member

Member

Similar threads

Upgrading Caveats