-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
display_name is not publish on MQTT #4497
Comments
Thanks for reporting. You can find all the MQTT topic here: https://docs.teslamate.org/docs/integrations/mqtt display name is the name you give your car via the touch screen in the menu |
Others topics like : teslamate/cars/$car_id/model are missing. I wouldn't know how long, but in the first installation I did of teslamate, (Dec 2024) it did show that information. I think there has been neither teslamate nor mqtt updates. |
I don't understand the issue here. I see all of those values in the referenced MQTT documentation, and I believe all of these values are being published to MQTT. What is not working? |
Your car need to be awake at least once to populate the values |
the values was populated when the app was, launched and configured the first time, but sometime later the values went to unknow. Stopping the TESLAMATE docker stack, and deploying it again, the values are populated again and published in MQTT messages |
Is there an existing issue for this?
What happened?
I was browsing my teslamate MQTT topics for a 3rd party integration with the help of Teslamate documentation as I notice there is no
teslamate/cars/$car_id/display_name
topic.Expected Behavior
Not sure if it's the "good" display name but i was expecting something similar to what I can read on my teslamate homepage.
Steps To Reproduce
No response
Relevant log output
No relevant output as everything else is working as expected.
Screenshots
Additional data
Here below all the topics on my teslamate.
Type of installation
Docker
Version
1.32.0
The text was updated successfully, but these errors were encountered: