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?

  • thehatfox@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    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.tfOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

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

      • sue_her_birds
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 months ago

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

        • sabreW4K3@lemmy.tfOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          10 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
          
          
            • sue_her_birds
              link
              fedilink
              English
              arrow-up
              2
              ·
              10 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.tfOP
                link
                fedilink
                English
                arrow-up
                1
                ·
                10 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.