Postgres issue starting up / vid "has already been taken" about teslamate HOT 6 CLOSED

FYI, the user needs to run the docker-compose in one ssh window and let it continue to error itself out, while you connect to that docker install with the command to command line Postgres in another SSH window:

sudo docker-compose run --rm db psql -h db -U teslamate

I didn't know much about how Docker worked until today. Even less about Postgres. Took me forever to figure out how to connect to a Postgres database inside of a Docker container.

from teslamate.

Thanks for your quick help. It's working again!

Awesome!

There may be others affected by this problem as well. I'll pin this issue 👍

from teslamate.

Someone else reported the same issue today. The underlying problem is actually a quirk on Tesla's end.

They recently changed the IDs (!!!) of some cars. See timdorr/tesla-api#139

Unfortunately you have to fix it manually by updating the entry in the database table "cars". Change the eid of entry that has the vid 1749778265 to "36230209430047724" (I got those values from the log output you posted).

Edit: This is how it should be

eid: 36230209430047724
vid: 1749778265

from teslamate.

Well that's annoying of Tesla to do that.

kevin@NUC-TV:~/teslamate$ sudo docker-compose run --rm db psql -h db -U teslamate
[sudo] password for kevin:
Password for user teslamate:
psql (11.5 (Debian 11.5-1.pgdg90+1))
Type "help" for help.

teslamate=# SELECT * from cars;
id | eid | vid | model | efficiency | inserted_at | updated_at
----+-------------------+------------+-------+------------+---------------------+---------------------
1 | 19822922099185452 | 1749778265 | M3 | 0.153 | 2019-07-31 17:46:32 | 2019-07-31 17:46:32
(1 row)

teslamate=# UPDATE cars set vid=36230209430047724 ;
UPDATE 1
teslamate=#

That fixed that issue... now it's saying this:

teslamate_1 | Server: 192.168.10.51:4000 (http)
teslamate_1 | Request: GET /
teslamate_1 | ** (exit) exited in: :gen_statem.call(:"1", :summary, :infinity)
teslamate_1 | ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started

This happens whenever I attempt to view the page at port:4000. Ideas?

from teslamate.

You might have changed the wrong id :)

This is how it should be:

eid: 36230209430047724
vid: 1749778265

from teslamate.

Yup, I did that wrong, had to delete the new car.

teslamate=# DELETE FROM cars where eid=36230209430047724;
DELETE 1
teslamate=# SELECT * from cars;
id | eid | vid | model | efficiency | inserted_at | updated_at
----+-------------------+-------------------+-------+------------+---------------------+---------------------
1 | 19822922099185452 | 36230209430047724 | M3 | 0.153 | 2019-07-31 17:46:32 | 2019-07-31 17:46:32
(1 row)

teslamate=# update cars set eid=36230209430047724 ;
UPDATE 1
teslamate=# update cars set vid=1749778265 ;
UPDATE 1
teslamate=# SELECT * from cars;
id | eid | vid | model | efficiency | inserted_at | updated_at
----+-------------------+------------+-------+------------+---------------------+---------------------
1 | 36230209430047724 | 1749778265 | M3 | 0.153 | 2019-07-31 17:46:32 | 2019-07-31 17:46:32
(1 row)

Thanks for your quick help. It's working again!

from teslamate.