What Am I missing

[Spudjr]

New to HS3. Created an event to make an announcement that when the door is open for more than 1 minute it speaks a message. The problem is it keeps repeated the message over and over. Under option I can select not to re-run for X amount of minutes. Is there some way in the event so it will only run once per door opening. In other words I want it to run each time the door is open but only announce the message once per opening. Thanks

[sparkman]

Use This Device Changes and Becomes Open instead.

[Spudjr]

Thanks. How would I delay this announcement as I only want to have it speak if the door is open more than 1 minute?

[bsobel]

Thanks. How would I delay this announcement as I only want to have it speak if the door is open more than 1 minute?

Change the for at least to for exactly. At least will trigger once a second after the time has passed, exactly will trigger just once at the time...

[Dan-O]

Change it to Exactly 1 minute instead of at least 1 minute.


Edit: We must have been typing at the same time.

[Spudjr]

Thanks for the quick reply. Lots of learning but a huge improvement over Vera

[Dan-O]

I've been using HS for 20 years and I learn something new all the time!

[Uncle Michael]

Another approach is to use 'has been open for at least' as the trigger, but specify in the advanced section a 'cannot rerun for' time. For instance if you trigger after the door has been open for at least one minute, then restrict the rerun time to 5 minutes, it will announce at 1 min, then continue to nag every 5 minutes after that. (Of course, if all you want is the initial warning, then the exact time trigger is the way to go.)

[Guest]

Another approach is to use 'has been open for at least' as the trigger, but specify in the advanced section a 'cannot rerun for' time. For instance if you trigger after the door has been open for at least one minute, then restrict the rerun time to 5 minutes, it will announce at 1 min, then continue to nag every 5 minutes after that. (Of course, if all you want is the initial warning, then the exact time trigger is the way to go.)

I was using a recuring trigger .
but i like your idea !. Will change some event

[kideon]

I was using a recuring trigger .
but i like your idea !. Will change some event

Does this have any repercussions with processor / memory?

[Guest]

Does this have any repercussions with processor / memory?

I do not think cheking conditions every 5 minutes have a big impact. I always stay on low on my pc.

[Uncle Michael]

Does this have any repercussions with processor / memory?

Not that I'm aware of. Randy has probably studied the issue as carefully as anyone and concludes that once an event is constructed, it has almost no impact unless it actually runs. That is also my impression. It appears that the triggers, conditions and other constraints are handled very efficiently by HS, so the overhead to evaluate them is negligible.

[Guest]

Not that I'm aware of. Randy has probably studied the issue as carefully as anyone and concludes that once an event is constructed, it has almost no impact unless it actually runs. That is also my impression. It appears that the triggers, conditions and other constraints are handled very efficiently by HS, so the overhead to evaluate them is negligible.

haha I almost tagged @rprade for that, to confirm. Did it now lol

[Rvtravlr]

Another approach is to use a timer. In the event below, it will trigger after 6 minutes, reset to 5 minutes and if still open, announce and trigger in another minute. This way you could have a 1 minute trigger, reset to 0 and it would trigger again at 1 minute until the door is closed.