submitted 10 months ago by sabreW4K3@lemmy.tf to c/homeassistant@lemmy.world

10 comments fedilink hide all child comments

Sometimes some of my automations don't trigger, so when I look at the trace to find out why, I'll see something like unknown entity. Does anyone know what's happening and how to fix it?

you are viewing a single comment's thread
view the rest of the comments

[-] sue_her_birds@sh.itjust.works 6 points 10 months ago* (last edited 10 months ago)

My guess is that at some point you had a lux sensor (illuminance) as a condition and that entity has either had its name changed or has been deleted.

Check out the automation (either in the builder or in the yaml) to see if you have this condition. Then see if that entity still exists or if it’s name has changed.

Edit: for clarity

[-] sabreW4K3@lemmy.tf 2 points 10 months ago

See that's the weird thing. I haven't removed or renamed any devices and most of the time everything works, but once in awhile I get these errors.

[-] thehatfox@lemmy.world 3 points 10 months ago* (last edited 10 months ago)

Once I had devices that replaced entities with new ones with a different ID after a firmware update. It happened to some ESPHome devices I had after upgrading the firmware. Have you checked the device the entity belongs to?

[-] sabreW4K3@lemmy.tf 2 points 10 months ago

Yup, once I manually trigger the automations, everything starts working again

[-] sue_her_birds@sh.itjust.works 2 points 9 months ago

Very strange. Are you yaml based or automatic builder based? Can you post your code/screen shots?

[-] sabreW4K3@lemmy.tf 1 points 9 months ago* (last edited 9 months ago)

Automatic builder. Just had it happen again

alias: Illuminate Bathroom
description: ""
trigger:
  - type: occupied
    platform: device
    device_id: 59772f660e8f058102f9e94a02403969
    entity_id: d4e7dc31bf50b3a2302c611bbf16bc94
    domain: binary_sensor
condition:
  - type: is_illuminance
    condition: device
    device_id: 59772f660e8f058102f9e94a02403969
    entity_id: c192872a4d9f435658f8e84c4ad110b5
    domain: sensor
    below: 1200
  - type: is_motion
    condition: device
    device_id: 0ae8165edc6622b670e24f99a7911c07
    entity_id: 2314ba20932943fdb166814cfa6156b0
    domain: binary_sensor
action:
  - service: switch.turn_on
    metadata: {}
    data: {}
    target:
      device_id: bd72cd3e24be2facbf8e6bf459e93b09
mode: single

[-] sabreW4K3@lemmy.tf 1 points 9 months ago

Screenshot of the build

[-] sue_her_birds@sh.itjust.works 2 points 9 months ago

Have you looked at your logs to see if anything looks fishy? Check your main logs but also the logs in your zigbee integration

Also it may be time to submit it as a bug.

[-] sabreW4K3@lemmy.tf 1 points 9 months ago

So I've been going through whatever the search engines would throw at me and it seems some people have become so accustomed that they have automations to send alerts. I'm gonna try and track down more info so I can file a decent bug. Hopefully they squash it for once and for all.

this post was submitted on 14 Jan 2024

12 points (100.0% liked)

homeassistant

11921 readers

7 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

GreatAlbatross@feddit.uk