You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a strange behavior sending values from teslamate vis MQTT bridge to another system.
For testing I set teslamate/cars/1/battery_state to 76 (the SoC of the car at that time) manually using MQTT Explorer and checking the retention checkbox. I did the same with the respective topic on the other side.
Now once a while the other system shows this random value especially after starting up their MQTT broker (also a mosquitto).
My hope is to get rid of this strange behavior by deleting the mosquitto.db file in both systems.
Is ist save for teslamate operation to delete this file while mosquitto container is stopped?
In other words: does teslamate depend on anything permanently stored in this file?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a strange behavior sending values from teslamate vis MQTT bridge to another system.
For testing I set
teslamate/cars/1/battery_stateto 76 (the SoC of the car at that time) manually using MQTT Explorer and checking theretentioncheckbox. I did the same with the respective topic on the other side.Now once a while the other system shows this random value especially after starting up their MQTT broker (also a mosquitto).
My hope is to get rid of this strange behavior by deleting the mosquitto.db file in both systems.
Is ist save for teslamate operation to delete this file while mosquitto container is stopped?
In other words: does teslamate depend on anything permanently stored in this file?
Beta Was this translation helpful? Give feedback.
All reactions