Camera Motion doesn’t trigger automation

Configuration
1

I’ve gone round the bend getting this automation to work, and it does now—but only when triggered manually.

I’m using the Camect integration through HACS, and I can see in the device the history of motion being noticed by HASS, but the following automation never triggers:

alias: Front Porch Camera Motion
description: prototype for all camera motion
triggers:
  - type: motion
    device_id: 267e7fc35eadc83d88626913b2161f1d
    entity_id: 413296f02876d4de64d8e684e0f0eb67
    domain: binary_sensor
    trigger: device
conditions:
  - condition: device
    device_id: 249e41676a6817992966feb27e46d0d3
    domain: device_tracker
    entity_id: 0263339712c99b093a4e6c856e856ea0
    type: is_home
    enabled: false
actions:
  - action: browser_mod.popup
    metadata: {}
    data:
      title: Front Porch Motion
      dismissable: true
      autoclose: false
      content:
        type: picture-entity
        entity: camera.front_porch
        name: Front Porch
        timeout: 30000
        target: null
        device_id: d2ab9242428350849390ec3c451f9bc8
      browser_id:
        - d2ab9242428350849390ec3c451f9bc8
        - 9d7b0adcea0bb0ebf56afeddfd76473f
mode: single

How can I troubleshoot this further? I’m very new to this.

2

I really hate device_id stuff. I have no idea what that is…

3

OK, I was just following the path of least resistance, but I see your point.

Changed it to:

alias: Front Porch Camera Motion
description: prototype for all camera motion
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.front_porch_motion_2
    to:
      - "on"
conditions:
  - condition: device
    device_id: 249e41676a6817992966feb27e46d0d3
    domain: device_tracker
    entity_id: 0263339712c99b093a4e6c856e856ea0
    type: is_home
    enabled: true
actions:
  - action: browser_mod.popup
    metadata: {}
    data:
      title: Front Porch Motion
      dismissable: true
      autoclose: false
      content:
        type: picture-entity
        entity: camera.front_porch
        name: Front Porch
        timeout: 30000
        target: null
        device_id: d2ab9242428350849390ec3c451f9bc8
      browser_id:
        - d2ab9242428350849390ec3c451f9bc8
        - 9d7b0adcea0bb0ebf56afeddfd76473f
mode: single

Still doesn’t trigger.

4

How did you trigger it? By doing motion that changes the trigger to on? The change is when it triggers.
If it’s just on when you reload the new automation it won’t trigger.

Also if you do change the binary_sensor, the condition, whatever that is, needs to be true.

5

I triggered it by walking in front of the camera.

And yes, the conditions are true. but I’ll disable them and test again.

6

If the binary sensor changes to on (which you can check in the entity history), then it’ll trigger and create a trace which you can view. The action may be blocked by the condition, or the action itself might fail — the trace will tell you.

7

seems like Camect isn’t being good about triggering motion notifications and sending them to HASS.

I’ll take this up in the Camect forums.