Motion sensor to action problem

[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)