Trigger "Immediate Actions" not honoring Break Time

Moderators: HeneryH, TimG

Post Reply
geaux
Posts: 3
Joined: Tue Feb 07, 2023 11:42 am

Trigger "Immediate Actions" not honoring Break Time

Post by geaux » Tue Feb 07, 2023 11:59 am

New to posting on the forum, but incredibly grateful for the support I've received reading posts here. Couldn't find an answer to a new issue for me, so I'm hoping someone can help me.

For any motion on a camera, I want the outside lights to immediately turn on. This is done via a web request to my smarthome hub. Separately, the AI evaluates for a person and sends a push notification if someone is detected.

This seems to be working, but the Immediate Actions trigger in BI sends nearly constant http messages while there is motion (3-4 per second), which is more than I want my hub responding to. So it doesn't seems like the Immediate Actions are not honoring the break time.

My current settings are:
End trigger unless re-triggered within 15.0 sec
Maximum trigger/alert duration 90 sec

If there is constant motion, my understanding is those settings should suppress any repeat triggers for 90 seconds. If that is accurate, any ideas on how to make Immediate Actions honor the break time?
MikeBwca
Posts: 1183
Joined: Thu Jun 20, 2019 5:39 am

Re: Trigger "Immediate Actions" not honoring Break Time

Post by MikeBwca » Tue Feb 07, 2023 6:58 pm

On the Alerts tab, 'When:"... is this set for 'New and re-triggers'? Is so, set it to 'New Triggers only'.
geaux
Posts: 3
Joined: Tue Feb 07, 2023 11:42 am

Re: Trigger "Immediate Actions" not honoring Break Time

Post by geaux » Tue Feb 07, 2023 7:20 pm

Confirmed it was set to New Triggers Only. Also, minimum time between alerts is 180 sec.
User avatar
TimG
Posts: 2592
Joined: Tue Jun 18, 2019 10:45 am
Location: Nottinghamshire, UK.

Re: Trigger "Immediate Actions" not honoring Break Time

Post by TimG » Tue Feb 07, 2023 8:01 pm

I'm guessing, but I would think "Immediate Actions" bypasses any BI5 control.

As a matter of interest, how quickly do your lights work ? I'm doing the same thing with Homeseer, but I am using Alerts rather than "Immediate Actions" and they seem rather slow to illuminate. OK, changed to try "Immediate Actions", but I think I had moved to Alerts to prevent nuisance triggering. Alerts may be a bad idea with CPAI ! Hmm...
Forum Moderator.
geaux
Posts: 3
Joined: Tue Feb 07, 2023 11:42 am

Re: Trigger "Immediate Actions" not honoring Break Time

Post by geaux » Tue Feb 07, 2023 8:13 pm

The Immediate Actions trigger seems to work very fast, maybe 1-2 seconds at the most. I'm using Hubitat, which responds to the http request almost instantly.

My camera is far from a lot of the action and IR illumination is not great, so I wouldn't trust the AI to reliably notice a person. So my hope is that the lights are enough to spook someone, and if they stick around, the AI will eventually trigger and send the push notification.

Sounds like getting Immediate Actions to follow break time would be a feature request. Appreciate everyone's help.
User avatar
TimG
Posts: 2592
Joined: Tue Jun 18, 2019 10:45 am
Location: Nottinghamshire, UK.

Re: Trigger "Immediate Actions" not honoring Break Time

Post by TimG » Sat Feb 11, 2023 12:55 pm

FWIW I did a test with Blue Iris motion detection on my drive camera triggering my lights in Homeseer, as it is very sluggish with those outside lights - somebody can be almost passed my house before the lights come on. Cue motion on the drive, anddddd....... ACTION:

A. "Immediate" JSON triggers from BI5 triggering the Homeseer Blue Iris plug-in to turn on one light. (Present solution).
B. "Immediate" MQTT trigger turning on a different light with Homeseer.
C. "Alert" MQTT trigger turning on a third light with Homeseer.

Now watch to see which light comes on first. Where is the popcorn when you need it ?

1. The "Immediate" MQTT (B) was around 3.5 seconds faster than the "Immediate" Homeseer plug-in (A) every time.
2. Obviously the "Alert" (C) didn't trigger unless CPAI allowed it to, and even then there was a variable delay; however it always triggered after the "Immediate" Homeseer Blue Iris plug-in.
3. Homeseer mcsMQTT showed the expected variable delay between the two MQTT triggers, the "Immediate" (B) and "Alert" (C) triggers.

I need to be watching the video feed as well as watching the lights, but the real test will be tonight when it gets dark :shock:
Forum Moderator.
Post Reply