Not compatible with PostgreSQL 17.4?

[driehle]

I am using the PostgreSQL image from https://github.com/expaso/hassos-addon-timescaledb and recently, I have upgraded it to the latest version, which comes with PostgreSQL 17.4. I am aware that the version I am using is not the one by alexbelgium, which you recommend in the docs. Since the upgrade, the Teslamate add-on fails to start with the following error message:

I did a bit of research and found out that this likely is from an incompatibility between the psql command included in this add-on and the command included in my PostgreSQL image (i.e. the server version). Here is a somehow related post from Stackoverflow.

There is one \list call in the start-up script which seems to cause this issue:

ha-addon-teslamate/rootfs/etc/s6-overlay/s6-rc.d/teslamate/run

Line 64 in a5180bc

if [[ -n $(PGPASSWORD="$DATABASE_PASS" psql -h "$DATABASE_HOST" -p "$DATABASE_PORT" -U "$DATABASE_USER" postgres -Atqc "\list \"$DATABASE_NAME\"") ]]; then

Running the same command in my PostgreSQL container works fine and delives the expected output:

Running the same command from the Teslamate add-on causes the same error message as in the logs:

Now, it seems as this add-on image still comes with PostgreSQL client 15.10 and the \list command of that one seems to be incompatible with a PostgreSQL server 17.4. While we could simply say the Teslamate add-on is not compatible with newer PostgreSQL versions, I am suprised as the Teslamate docs explicitly mention PostgreSQL v17+ as a requirement.

So, if this add-on comes with Teslamate 1.32.0 (since 1.4.0), and Teslamate itself requires PostgreSQL 17 since 1.31.0 (although it is somehow a soft requirement according to release notes), why does this add-on still come with a bundled PostgreSQL 15 client?

What do you suggest? Are there plans to upgrade this add-on to PostgreSQL 17 as suggested to be used by Teslamate?

[BVGorp]

I'm also using the timescaledb add-on for the postgress installation for another add-on.
I'm running into the same issue.

[driehle]

Thanks, good to hear I am not the only onw having this issue 😆

I did another short check to verify, wheter the issue is comming from this addon. When starting the original teslamate image directly, there is no postgresql-client installed:

This means that the installation the this repositories Dockerfile doesn't overwrite anything, but actually adds the client here:

ha-addon-teslamate/Dockerfile

Line 32 in a5180bc

postgresql-client \

Now, when I run a teslamate container as root and simulate the installation procedure, i.e. running apt update and apt install postgresql-client, it installs v15, as that is the one from the Debian repositories:

root@homeassistant /home/driehle # docker run --rm -it --network hassio --entrypoint /bin/bash -u root teslamate/teslamate:1.32.0
root@e567253426de:~# apt update
[...]
root@e567253426de:~# apt install -y postgresql-client
[...]
root@e567253426de:~# psql -V
psql (PostgreSQL) 15.12 (Debian 15.12-0+deb12u2)
root@e567253426de:~# cat /etc/debian_version
12.8

Therefore, upgrading postgreql-client to v17 is not really straight forward. We'd need to use a custom repository. I simulated this as well, the following seems to work:

root@homeassistant /home/driehle # docker run --rm -it --network hassio --entrypoint /bin/bash -u root teslamate/teslamate:1.32.0
root@ea22f3fea256:~# apt update && apt install -y postgresql-common
[...]
root@ea22f3fea256:~# /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -y
This script will enable the PostgreSQL APT repository on apt.postgresql.org on
your system. The distribution codename used will be bookworm-pgdg.

Using keyring /usr/share/postgresql-common/pgdg/apt.postgresql.org.gpg
Writing /etc/apt/sources.list.d/pgdg.sources ...

Running apt-get update ...
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Get:4 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease [129 kB]
Get:5 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg-snapshot InRelease [128 kB]
Get:6 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main amd64 Packages [360 kB]
Get:7 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg-snapshot/17 amd64 Packages [421 B]
Fetched 618 kB in 1s (783 kB/s)
Reading package lists... Done

You can now start installing packages from apt.postgresql.org.

Have a look at https://wiki.postgresql.org/wiki/Apt for more information;
most notably the FAQ at https://wiki.postgresql.org/wiki/Apt/FAQ
root@ea22f3fea256:~# apt install -y postgresql-client-17
[...]
root@ea22f3fea256:~# psql -V
psql (PostgreSQL) 17.4 (Debian 17.4-1.pgdg120+2)
root@ea22f3fea256:~# psql -h 77b2833f-timescaledb -U teslamate postgres -Atqc "\list \"teslamate\""
Password for user teslamate:
teslamate|teslamate|UTF8|libc|C|C.UTF-8|||

So, technically the installation of postgresql-common, followed by running /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh -y allows the installation of postgresql-client-17, which does the trick.

[lildude]

I am suprised as the Teslamate docs explicitly mention PostgreSQL v17+ as a requirement.

As you pointed out, it's not a hard requirement, and it wasn't a requirement at all when I took over maintaining this addon. There has also been no notification that this is now a hard requirement so I've not acted upon it. I've also not tested with PostgresSQL v17+ as I'm not using it (mainly because I've not found an HA PostgreSQL that only provides v17+ and nothing else) and if it aint broke, don't fix it 😁

This is the first issue to indicate this isn't the case for everyone.

As for the rest of your questions… you've already answered why we've got the v15+ client and thanks for the example solution.

I'll have to do some testing with this (mainly to see if it's backwards compatible with v15) and see if I can come up with a solution that works for all, or as many as possible, as I'm reluctant to start recommending something like the TimescaleDB addon as it includes more than what peeps need for this addon.

[BVGorp]

thanks for looking into it!
is there a way to get us running in the mean time? :)

[lildude]

Unfortunately not, however I've managed to repro this and find a very simple solution and just merged #77 and have kicked off building a new release.

Updating the addon to v1.4.3 as soon as it appears in HA should fix this and allow your addon to start.

[driehle]

I was able to trigger the update by hitting the refresh button at the top right of the add-on page in HA.

Startup of the new 1.4.3 seems to run withough any issues:

[12:13:15] INFO: Checking for database 'teslamate' on 77b2833f-timescaledb
[12:13:15] INFO: Database teslamate already exists
[12:13:16] ERROR: Unable to access the API, forbidden
[12:13:16] INFO: Configure TeslaMate settings by adding these values
                 to the URL you use to access your Home Assistant instance:
  => Web App: /api/hassio_ingress/xIZ8XgesIg58vZV4Zr8hOsVQywtPrvqa5-rZ22BbU6g
  => Dashboards: /api/hassio_ingress/xIZ8XgesIg58vZV4Zr8hOsVQywtPrvqa5-rZ22BbU6g
  
[12:13:16] INFO: Starting TeslaMate...
2025-03-19 12:13:17.809 [info] Migrations already up
2025-03-19 12:13:20.441 [info] No tzdata release files found in custom data dir. Copying release file from tzdata priv dir.
2025-03-19 12:13:20.567 [info] System Info: Erlang/OTP 26 (jit)
2025-03-19 12:13:20.567 [info] Version: 1.32.0

Looks like everything is working fine for me, though I haven't been driving yet. Thank you for the quick bugfix release!

[lildude]

Woohoo!! I've got another patch update comming to address the ERROR in the output which is what is causing identical URLs to be shown in the message below it. I missed this before when I introduced that helpful info.