Why the light stays on when motion is long gone?

[BruceB1 (Bruce B)]

Using Motion-activate-light to turn ON when Reolink camera via Frigate shows All Occupancy (motion of people) instead of a full automation and it works well for turning ON but does not turn OFF. How to go about finding the reason?

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

blakeblackshear/frigate · Discussions · GitHub is the official Frigate support hub and is another good place to get help with Frigate if you don’t get an answer here.

[tom_l]

Do you have an off automation action?

e.g.

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. triggers: - trigger: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'on' - trigger: state entity_id: binary_sensor.your_motion_sensor_here # change this to: 'off' for: minutes: 2 # adjust as necessary actions: - action: "light.turn_{{ trigger.to_state.state }}" target: entity_id: l…

[BruceB1 (Bruce B)]

I forgot to show the picture. At the bottom I see 10 seconds set for turn off time. Isn’t that what should turn off the lights?

[tom_l]

Oh this is a blueprint.

No idea how that operates.

Ask the blueprint author.

[BruceB1 (Bruce B)]

Thanks.

Blueprint means a custom thing added after to HaOS? It says by Home Assistant. I thought this camera with my fresh install. I guess not?

Below is the code for this that I see in automations.yaml. How to change it to make it turn off after 10 seconds of no motion?

- id: '1763682313721'
  alias: Backyard wall light on Motion
  description: ''
  use_blueprint:
    path: homeassistant/motion_light.yaml
    input:
      motion_entity: binary_sensor.back_right_all_occupancy
      light_target:
        entity_id:
        - light.backyard_wall_light
        - light.back_right_backyard_floodlight
      no_motion_wait: 10

[bob.t (Bob)]

It’s likely because the turning off the light is interpreted as motion.

I couldn’t figure out how to over come that w/o a separate motion detector used in my lighting automations, anyway.

[BruceB1 (Bruce B)]

I have seen that type of behavior before but that actually turns the light OFF and then ON again. This does not turn off at all.

[tom_l]

And this is why blueprints are terrible.

You have no idea what is going on inside them.

Write your own automations, that way you learn and know what you are doing.

[pixi]

Or, download the blueprint, take control of the blueprint, by opening it and click the 3 dots in the top right corner, and look what the blueprint does, instead of blindly using it…

[ShadowFist]

@tom_l

Ask the blueprint author

That’s one of balloob’s earliest blueprints. Found the yaml here.

@BruceB1 can you share the automation traces when it triggers but fails to switch off the light again? Also, the history of binary_sensor.back_right_all_occupancy during that time would help too.