Open c2ho5ohx2 opened 1 month ago
Sometimes tesla route is detected as "home", sometimes as "Home", see screenshot
Did a workaround to match with OR, between "home" and "Home". Here one execution of the automation: alias: Tesla coming home description: "" trigger:
Execution on step for the route: Executed: September 19, 2024 at 8:32:34 PM Result:
result: true
conditions/0 Executed: September 19, 2024 at 8:32:34 PM Result:
result: false state: Home wanted_state: home
conditions/1 Executed: September 19, 2024 at 8:32:34 PM Result:
result: true
conditions/1/entity_id/0 Executed: September 19, 2024 at 8:32:34 PM Result:
result: true state: Home wanted_state: Home
Trigered by: type: distance platform: device device_id: ac2308f19695082b51577ebdb4206785 entity_id: 79c71be6fd5e8cc589e85f9747d94080 domain: sensor below: 0.1
unfortunatelly, since I recreated the autoamtion, I do not have a trace to show when the state is reported with lower letter, even though in previous autiomation, I've seen it.
The problem
When doing Automation and condition to match for Tesla Route: condition:
condition: device device_id: ac2308f19695082b51577ebdb4206785 domain: device_tracker entity_id: 8a5ec73b1a6dc440d85e3cb92cabbef1 type: is_home
It will never match, since the value returned from Tesla is Home (with capital H) and the condition will always evaluate to false
What version of Home Assistant Core has the issue?
core-2024.9.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tesla Fleet
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response