2021-04-24 11:50:12 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: tesla
2021-04-24 11:51:12 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: tesla
2021-04-24 11:52:12 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: tesla
It looks like it’s trying to use the Tesla integration, which is broken. Any suggestions on how to make TeslaMate work in HA?
I have it working via MQTT. You obviously need MQTT running on HomeAssistant, but that is pretty straight forward to setup. Once that is done, you’ll need to create a user for teslamate.
After that, you’ll need to update your .env’ file on teslamate with the following variables:
@Chacsam Teslamate is likely installed outside of HAos. An option is to use Docker. Teslamate has templates to setup everything required with support of mqtt. Once Teslamate is all setup, I believe HAos should be able to integrate with “Teslamate’s mqtt service”.
I’ve been trying to move away from an old Docker hass installation to a vm (HAos) on a newer Synology. I wish “HAos mqtt integration” could expose the network port outside of HAos, it doesn’t seem possible.
Resurrecting this older post. I’ve had Teslamate working perfectly via MQTT but am now getting a warning that the use of platform: mqtt in configuration.yaml is being deprecated.
How do I move to the ‘proper’ method of having HA’s MQTT listen to the topics teslamate/cars/1/***
And how do I add the name and icon as per the Teslamate guide linked above?
I’d love some help setting this up, I have Teslamate, the DB, Grafana, and Mosquitto running on a NAS. Home Assistant is on a Pi. Can’t seem to find a good walkthrough to getting it all integrated into HA. Thanks
Hi, thanks, first thing is figuring out MQTT and Home Assistant grabbing the data from Teslamate. What do I have to configure on the Teslamate side and what needs to be done on the Home Assistant side.
2、check your 1883 port whether it can be accessed, like “telnet ip:1883" in your windows CMD
3、Add integration in home assistant ,with your user&password
OK, thanks, I configured the docker.compose.yml file with the updated MQTT info, as well as the port information. From Home Assistant I added MQTT and entered the IP, port, user, and pass, and it said it was successful. I added the sensors, binary sensors, mqtt sensors, and mqtt binary sensors to my configuration.yaml. I created a test dashboard and copied/pasted the lovelace ui, the entities mostly appear, but status is unknown/unavailable for all. I don’t think the data is coming over from Teslamate and I don’t know how to test for sure.
I tried going to the MQTT configuration to Listen to a topic manually and hit start listening, but no data comes back. How do I know if the MQTT server is publishing the data to Home Assistant?
Hi, I figured I would power the car up to see if that forced some data and sure enough it started populating some of the dashboard entities. So it looks like the basic setup is complete. I have a couple of missing entities that I need to check on as they are not working. Thanks for pointing me in the right direction to get this working. Next is to figure out how to control things from HA back to the Tesla.
What information do you want to bring to the Home assistant?
If your teslamate is installed correctly then MQTT should have many topics from teslamate.
the official documentation helped me set it up in Home Automation. Here is the link
Start with mqtt_sensor.yaml section of the document.
I couldn’t find a better way to add all the sensor data from Teslamate so I created an autodiscovery script for Home Assistant. It’s just a YAML script that will bring in all the Teslamate MQTT topics as sensors and put them under a single device, which is something that can’t be accomplished with manually-created MQTT sensors. Since it’s a YAML script you can easily edit/add/remove any sensors you like. This includes renaming them, setting the preferred units and the conversion factors, changing the icons, etc.
Is this add-on still maintained?
As it is now im using a seperate PI4 for TeslaMate, but it feels like a waste of hardware if this add-on is still maintened.