You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This template is great, I've implemented it for all my light groups that are triggered by motion sensors.
I'm useing the Philips HUE Motion sensors.
For example for the bathroom the automation is configured to trigger when motion is detected and LUX is >= 7.
It will turn-off when there is no motion for longer than 120 sec (2minutes).
There some behavior I'm observing with this;
When for some reason there is no motion for 120 sec (for example because you are standing still or w/e the lights turn of as per design. But when motion starts again it should (re)trigger again which does not happen.
When you wait a while eventually the motion is picked-up again and the lights will turn-on again.
Is this related to some reset/delay timer in the template or is this related to some hardware/firmware timers in the HUE sensor?
Or should I look to the restart behavior? Assumption: When motion is detected within a short period after the light turns off, the automation is being restarted, which can cause a delay before it retriggers.
mode: queued instead of restart: mode: queued max_exceeded: silent
FYI
Before I was using basic/simple automation for this that basically only trigger on motion without the dependency on LUX which worked fine so im not sure.
The text was updated successfully, but these errors were encountered:
This template is great, I've implemented it for all my light groups that are triggered by motion sensors.
I'm useing the Philips HUE Motion sensors.
For example for the bathroom the automation is configured to trigger when motion is detected and LUX is >= 7.
It will turn-off when there is no motion for longer than 120 sec (2minutes).
There some behavior I'm observing with this;
When for some reason there is no motion for 120 sec (for example because you are standing still or w/e the lights turn of as per design. But when motion starts again it should (re)trigger again which does not happen.
When you wait a while eventually the motion is picked-up again and the lights will turn-on again.
Is this related to some reset/delay timer in the template or is this related to some hardware/firmware timers in the HUE sensor?
Or should I look to the restart behavior?
Assumption: When motion is detected within a short period after the light turns off, the automation is being restarted, which can cause a delay before it retriggers.
mode: queued instead of restart:
mode: queued max_exceeded: silent
FYI
Before I was using basic/simple automation for this that basically only trigger on motion without the dependency on LUX which worked fine so im not sure.
The text was updated successfully, but these errors were encountered: