Replies: 2 comments 1 reply
-
... At one point in time things started to behave as projected and the problem dissolved. The biggest change I made was disabling another mqtt service (snap version) which was unknowingly running. Not sure if this was the reason. It had been auto-installed for one or another purpose. So consider this question solved! |
Beta Was this translation helpful? Give feedback.
1 reply
-
Sorry, no idea why it isn't working for you. All I can say is it works fine for me... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, i enabled in the docker-compose.yml
However if I look in the mosquitto log it says:
- New client connected from 172.18.0.2:55520 as TESLAMATE_302E3731333 (p2, c1, k60).
It lacks the u'teslamate'. In this case the updated messages are denied.
If I connect with the tesla credentials via a mqtt explorer, the mosquitto log says:
- New client connected from 192.168.1.191:55995 as mqtt-explorer-08aaaefb (p2, c1, k60, u'teslamate').
This is the way and messages are accepted.
Is this a teslamate bug or must I put somewhere else (in grafana?) the mqtt userid and password?
Regards,
Henk
Beta Was this translation helpful? Give feedback.
All reactions