I am having an odd issue with automations. First I should say that this happened after an update. I believe it was either the update of the matter server or updating HA core 11.1-11.3. I have since moved to 2024.12.0 and nothing seemed to change. Running OS 14. All running on HA Yellow.
Anyway, suffice to say when I update 2 things happened (only 2 that I know of), all my thread TRVs dropped to unavailable and most all my automations stopped working.
The TRV issues I think are a separate issue not yet delved into. I am assuming I have to reconnect them all back to HA through matter but maybe the Automation problem is somehow related. This is next.
I am no YAML expert and I am very new to HA, but after the updates and upon inspection of the not working automations, I see this code…
conditions:
- condition: device
type: is_off
device_id: 4b73aa456c6f75286a56b1862806e191
entity_id: 66b8925c66b0507c2b89f228ee2fbcfb
domain: light
Note the entity_id. Again, not an expert, but I don’t think this is a the correct format for an entity id. In the action part of the code, the entity id is correct for the device and, indeed, when I swap the this very long number to the correct entity id, the automation comes to life. But why is this happening? Even newly created automations have this behavior. Seems very odd, as if the automation creator is pulling data from the wrong place. It looks like a device id. When I use the device id in a web address to find the device it says device/service not found . So it seems there is no device with this number.
Any help or insight would be appreciated. Perhaps I need to inform the developers, although not exactly sure if it is update related. Of course, I am happy to know how to fix my automations, but really would like the root cause fixed.