Automation disabled?

Configuration
1

Does anyone know why my extremely simple automation keeps getting disabled automatically? As I say, it’s very simple and runs when no activity is observed by motion sensor for 20mins and then activates a scene if so. Can’t see why it would be disabled? …very bizarre!!

2

Please share the automation.

3 
alias: Cloud OFF
description: ""
trigger:
  - type: no_motion
    platform: device
    device_id: a86f7a7b4b179bf45f581671aa95ace5
    entity_id: 720dcfdeaa732afe43ec6d6cb1991662
    domain: binary_sensor
    for:
      hours: 0
      minutes: 20
      seconds: 0
condition: []
action:
  - metadata: {}
    target:
      entity_id: scene.cloud_off
    action: scene.turn_on
mode: single
4

You have 2 device IDs listed, don’t believe that’s allowed. Also, going forward, it’s advisable to not use devices in automations (there’s lots of info on the forum as to why).

1 Like
5

I only see one.

Hayden, it would be preferable to only use entity IDs as indicated above, here’s why: Why and how to avoid device_ids in automations and scripts

And a concrete example of where this helped: Moving from Aqara hub to Z2M advice on entity changes

As to why your automation is being disabled, it could be because the motion sensor is going unavailable. Can you show it’s history graph?

6

My eyes definitely saw 2. :joy:

7

Still another reason to NOT use device triggers and actions…
32 character gobbledygook makes people see double. :smiley: