lost mqtt connexion?

[vbarrier]

Hi! thank you for this great addon :)

However, I have a problem since I use it :(. It seems that the backend loose the connection with the Mosquitto server or doesn't not refresh the cached data.

I'm polling the api/v1/cars/*/status every 1 minutes to populate a tracking database.

[vbarrier]

I can confirm that of the docker container fix the problem. Any insight on what happen is happening?

[tobiasehlert]

Hi @vbarrier,
What version of TeslaMateApi and Mosquitto are you using in your setup?
Has this issue appeared after you have done some upgrade?
You you see some suspicious entries in the container logs?

I can confirm that of the docker container fix the problem. Any insight on what happen is happening?

What you mean with docker container fix?

[vbarrier]

Hi I'm using the latest version of TeslMateApi (1.14) and MQTT version is 2.

It seems that the api lost connexion or doesn't take any more mqtt updates..

1652680291: Client teslamateapi-Lv85 closed its connection.
1652680293: New connection from 172.18.0.11:53518 on port 1883.
1652680293: New client connected from 172.18.0.11:53518 as teslamateapi-Jp2A (p2, c1, k2).

About docker container, I mean, that a restart of the docker container fix the issue for couple hours..

[virusbrain]

Hi @vbarrier,

have you done some more debugging for this issue? I currently experiencing the exact same behavior.

[vbarrier]

Hi, still facing the bug I ended up restarting the container every 4 hours. :(

[LelandSindt]

I looks like connections should be re-established...

teslamateapi/src/v1_TeslaMateAPICarsStatus.go

Lines 134 to 135 in 27d2044

	opts.SetAutoReconnect(true) // if connection drops automatically re-establish it
	opts.AutoReconnect = true

but also.. it looks like there are some some handlers that could be better utilized at a minimum for the purpose of logging... for example....
https://pkg.go.dev/github.com/eclipse/paho.mqtt.golang#ClientOptions.SetConnectionLostHandler

... again.. might be worth adding some logging.. then we may be able to better determine the nature of the failure.

[virusbrain]

I have forked the project and tried to add some debugging output as suggested. This version is running now inside a docker container. We will see if the problem occurs again, then I will keep you informed. If you look in my forked sourcecode you may see that I am not a go developer ;-).

[virusbrain]

I have forked the project and tried to add some debugging output as suggested. This version is running now inside a docker container. We will see if the problem occurs again, then I will keep you informed. If you look in my forked sourcecode you may see that I am not a go developer ;-).

The problem occurred again. For me it looks like there is no MQTT issue. I cannot see any log entries regarding lost connections or reconnecting. But if I call the status api end point I get:

teslamateapi_1 | 2022/09/21 16:27:00.611535 [debug] TeslaMateAPICarsStatusV1 - (/api/v1/cars/1/status) returned data:
teslamateapi_1 | 2022/09/21 16:27:00.611642 [debug] {"data":{"car":{"car_id":1,"car_name":"XXXXXX"},"status":{"display_name":"","state":"suspended", [...]

In the TeslaMate UI I see the state as "online" not "suspended".

I have tried to restart the my MQTT-Server (mosquitto in this case) and got the following messages in the logfile:

teslamateapi_1 | 2022/09/21 16:25:55.177510 [error] MQTT connection lost: %s
teslamateapi_1 | 2022/09/21 16:25:55.177578 [info] mqtt reconnecting...
teslamateapi_1 | 2022/09/21 16:25:56.209363 [info] mqtt reconnecting...

So the "extended logging" seems to work. Maybe there is a problem with the cache?

[virusbrain]

I have tried to restart the my MQTT-Server (mosquitto in this case) and got the following messages in the logfile:

teslamateapi_1 | 2022/09/21 16:25:55.177510 [error] MQTT connection lost: %s
teslamateapi_1 | 2022/09/21 16:25:55.177578 [info] mqtt reconnecting...
teslamateapi_1 | 2022/09/21 16:25:56.209363 [info] mqtt reconnecting...

So the "extended logging" seems to work. Maybe there is a problem with the cache?

Another example:
teslamateapi_1 | 2022/09/27 01:30:03.468099 [error] MQTT connection lost: pingresp not received, disconnecting teslamateapi_1 | 2022/09/27 01:30:03.468264 [info] mqtt reconnecting...

Maybe we have to "resubscribe" the topics after a reconnect? Does anybody know?

[vbarrier]

I also think this is a cache problem somewhere. I'm querying the teslamate-api every minutes and after sometime not working anymore. The restart thing remove all cache.. I will try to have a mirror setup as I don't want to break my current production setup.

[virusbrain]

I have another point found and currently do some tests with this patch implemented: virusbrain@3ce7126

Test is currently ongoing and as I am not a MQTT expert I am not sure which side effects this patch would produce... But if it will help I may be able to make the code a bit more fancy and create a pull request for this.

[LelandSindt]

virusbrain@3ce7126#r85320141

If I read your response correctly, I should be able to re-create this scenario by restarting the MQTT service, is that correct?