Motion sensor to action problem

[Jiran]

Helo. I have Philips Hue motion sensor. This sensor is able to turn ON Tuya light. I prepared automation where I would like to turn the light on after movement detection and turn it off after there is nothing moving for at least 30 seconds. This should work only 30 minutes before sunset until 30 minutes after sunrise.

Here is my automation which will turn light on but won´t turn it off. I tried many variations but without success. Please help.

alias: Motion light
description: ""
trigger:
  - type: motion
    platform: device
    device_id: c2fed70c6156d87017fd306e718c43ad
    entity_id: 20025762d69061f4471ab9e331b1bcd2
    domain: binary_sensor
condition:
  - condition: and
    conditions:
      - condition: sun
        before: sunset
        before_offset: "00:30:00"
      - condition: sun
        after: sunrise
        after_offset: "00:30:00"
action:
  - type: turn_on
    device_id: 52a50d56724524d0d71f8c8550fc0945
    entity_id: 05a4e9426a9fb4d964c42d2ceb9d300d
    domain: light
    brightness_pct: 100
  - delay:
      hours: 0
      minutes: 0
      seconds: 30
      milliseconds: 0
  - if:
      - condition: state
        entity_id: binary_sensor.pracovna_motion
        state: "off"
        for:
          hours: 0
          minutes: 0
          seconds: 30
    then:
      - type: turn_off
        device_id: 52a50d56724524d0d71f8c8550fc0945
        entity_id: 05a4e9426a9fb4d964c42d2ceb9d300d
        domain: light
    else:
      - repeat:
          sequence: []
          until:
            - condition: device
              type: is_off
              device_id: 52a50d56724524d0d71f8c8550fc0945
              entity_id: 05a4e9426a9fb4d964c42d2ceb9d300d
              domain: light
mode: restart

[aceindy]

Hi there…

Not sure exactly where you go wrong, but i can’t happen to notice a few ‘beginner’ mistakes:

Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [image] It works… but it is certainly not a “great way to start” because it is storing up problems for the future. Far better to use an entity, with state or numeric_state. Device_id problems The yaml will be longer and harder to follow, which may make maintenance difficult, especially a few months down the line when y…

And regarding your automation, have a look at the cookbook tip abt motion activated automations:

Motion activated lights automation

This gets asked a lot so here is an example for automating a light to come on with movement and go off after there is no movement for a short time. trigger: - platform: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'on' - platform: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'off' for: minutes: 2 # adjust as necessary action: - service: "light.turn_{{ trigger.to_state.state }}" target: entity_id: …

In your case, you can add the time condition to it, which would be as simple as:

conditions:
  - condition: sun
    before: sunrise
    before_offset: "00:30:00"
    after: sunset
    after_offset: "00:30:00"

NB: for a condition goes that all of them must be true in order to work, so it is automatically and (and therefor no need to specify it)

[Jiran]

Hello and thank you. I found a blueprint which uses light sensor which is ideal for this. I recomend blueprints because you can found plenty of them…

Blueprints Exchange