Cancelling Running Event

[brmeeke]

I have events like the one shown below which cancel another event. I have noticed that when it runs, I typically see the following Warning message.

3/13/2023 12:02:06 PM HomeSeer Warning Only events with 'WAIT' actions can be cancelled.
3/13/2023 12:02:06 PM HomeSeer Warning Event Basement Workshop On could not be cancelled, it was not found.
3/13/2023 12:02:06 PM HomeSeer Warning Only events with 'WAIT' actions can be cancelled.
3/13/2023 12:02:06 PM HomeSeer Warning Event Basement Freezer On could not be cancelled, it was not found.
3/13/2023 12:02:06 PM HomeSeer Event Event Trigger "Basement Creative Off

For the record, both of the events named here do include WAIT commands so it is quite likely that they could be executing.

Is there something that I am not doing correctly?

[stubble36]

I assume the wait commands from a different event were used... Were you using the wait commands as part of turning the lights off? For example, you had it wait for 30 minutes and then lights off? If the messages states no wait found, then the wait would have expired from the prior event I believe. I personally like the use of a timer in these cases. The timers seem to work much better than the wait and you have so much more control.

[randy]

The only way a running Event can be cancelled is if it is in a wait state. Your errors indicate the Event was not running.

This Error “3/13/2023 12:02:06 PM HomeSeer Warning Only events with 'WAIT' actions can be cancelled” is just a generic warning that will be issued any time a running event cancellation action fails to find the event. It does not indicate there was no Wait in the Event, just that the Event wasn’t found.

[brmeeke]

Hi Randy

i did some more testing and you are correct that the Warning messages are only triggered when the event is not active. What confuses me a bit is why does system throw the Warning in the first place when the Event says that it should “cancel the running event if it is executing”. If the event is not executing then to my mind, the handler should just keep going without the 2 warning messages.

It is not a big deal to rework the logic and eliminate the embedded WAIT commands in which case the issue goes simply away.