-
Notifications
You must be signed in to change notification settings - Fork 768
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
Documentation: Upcoming breaking change for Homeassistant mqtt sensor definition #2888
Comments
I adopted to the changes in Home Assistant and placed all the teslamate related configurations in one file, so that I could include it as a package: In configuration.yaml:
File includes/tesla.yaml:
I also fixed some templating issues in case of a missing source, which mostly happens when HA is starting. |
@Mosibi Thanks! Did you also include the known_devices.yaml code linked in the official documentation? Because that gives me errors, namely "missing devices section" |
The known_devices.yaml file is deprecated, but still working. So I still have a small known_devices.yaml file with only the tesla_location entry in it.
|
@bogie I took a second look and I have it working with the know_devices.yaml file. This is the change I made
Edit: Aha!!! Home Assistant creates the know_devices.yaml for this entry. |
On my end there is an error in known_devices.yaml: "Missing property "devices"." I have the same entry in there as you do and my configuration.yaml has:
|
@bogie the file known_devices.yaml is created when a device_tracker is configured. In your case, you should probably remove the ‘device_tracker’ line. Device tracker configuration should not be placed in that file. |
@Mosibi got it, my bad. I misread the documentation on the wiki. Not sure how I came up with that idea :D |
@Mosibi This is fabulous, it should be what's in the documentation, which currently use deprecated syntax and is all over the place. |
@ybizeul See https://jinja.palletsprojects.com/en/latest/templates/#jinja-filters.default If you change it to float(0), it will apply the float filter on the value before the pipe. If that value is not defined you will get an error, so it should be default(0) |
Ok, so with your template I'm getting :
Should it be |
I tried to reproduce the error you have, but I failed. You could use Btw, maybe you know or not, but these templates are easy to check in HA self using the http://:8123/developer-tools/template |
It could be that since reinstalling teslamate I didn't move the car, it seems elevation and speed messages were not sent yet |
But still the default should catch that. But anyway, a double default does not harm 😄 |
Can you wrap the output like this, Good finding!! |
And that is solved by the float(0). At least we know it now. Cool! |
Is there updated guidance on doing it without known_devices.yaml? I was able to duplicate what you've got but I get entity not available for proximity.home_tesla. Edit: When in doubt, restart HA. The docs still don't quite make sense in the example automation. My device_tracker doesn't have a simple "home" or "not_home", instead it returns:
https://www.home-assistant.io/integrations/device_tracker/ Edit: Here's what I ended up with if it's useful for anyone in the future. alias: Tesla Arrival/Departure
description: Open/Close Garage Based on if Tesla is coming or going
trigger:
- platform: zone
entity_id: device_tracker.tesla_location_tracker
zone: zone.approaching_home
event: leave
id: tesla_leaving
- platform: zone
entity_id: device_tracker.tesla_location_tracker
zone: zone.approaching_home
event: enter
id: tesla_arriving
condition: []
action:
- choose:
- conditions:
- condition: trigger
id: tesla_arriving
sequence:
- device_id: 42e0694050f8b1542dce99a147629cd2
domain: cover
entity_id: cover.ratgdo_41084
type: open
- conditions:
- condition: trigger
id: tesla_leaving
sequence:
- device_id: 42e0694050f8b1542dce99a147629cd2
domain: cover
entity_id: cover.ratgdo_41084
type: close
default: []
mode: single |
Hi everyone, today i used most of the existing config from https://docs.teslamate.org/docs/integrations/home_assistant/#automationyaml. Everything is working, but yeah some stuff is deprecated. The known_devices was already mentioned here, what is the new way? Will HA create the device automatically? By the way, data_template is also deprecated in the automation.yaml. It should be replaced by data. |
Should be fixed by #3344 |
My automation stopped working on Dec 3rd. I'm still trying to troubleshoot to figure out why. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Just wondering if #3344 fixed this issue? Noticed the documentation still lists |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
where to set the MQTT url? or configuration_url property in the official doc? |
Ideally somebody needs to update the docs to use the new |
Not sure how to handle the proximity which is now in the ui. |
Is there an existing issue for this?
What happened?
HA will update the configuration format for its mqtt configuration. Please find the new format below:
https://www.home-assistant.io/integrations/sensor.mqtt/#new_format
The following integration page requires an update:
https://docs.teslamate.org/docs/integrations/home_assistant/
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v124
The text was updated successfully, but these errors were encountered: