Delay Actions per Mode in Rule 5.1.3 is Hanging up on a non-delayed Mode

I recently created a Rule 5.3.1 and added a Delay Actions per Mode action. The rule is terminating/failing to continue for a mode that does not have a delay specified. I have it set up this way in rules I previously created, and the rule continues without a delay for a mode which is not specified. Here's a test rule to show what's happening:

Hub in Home mode but no delay specified for Home:
Screen Shot 2022-04-10 at 09.20.28
Off action Never happens:

app:68206422-04-10 09:13:16.758 trace[time_utc:1649596130, Rain:0, sum_rain_24:0, sum_rain_1:0]
app:11492022-04-10 09:10:13.501 info Action: Delay per mode:
                                     Away: 0:00:02
                                     Night: 0:00:02
                                     Out: 0:00:02
app:11492022-04-10 09:10:13.481 info Action: On: Kitchen Lights

Hub in Home mode and delay IS specified for Home:
Screen Shot 2022-04-10 at 09.25.24
Off action happens after specified delay for home:

app:11492022-04-10 09:26:26.469 info Action: Off: Kitchen Lights
app:11492022-04-10 09:26:26.451 info Delay Over: Delay per mode:
                                     Away: 0:00:02
                                     Home: 0:00:05
                                     Night: 0:00:02
                                     Out: 0:00:02
app:11492022-04-10 09:26:21.444 info Action: Delay per mode:
                                     Away: 0:00:02
                                     Home: 0:00:05
                                     Night: 0:00:02
                                     Out: 0:00:02
app:11492022-04-10 09:26:21.332 info Action: On: Kitchen Lights

@bravenel - Can you take a look at this when you have moment? This is still happening in my rules, and I don't think it's an expected behavior. My assumption is if there is no delay set for a mode the rule will continue but it's just stopping at that action. Here's another example of trying to run actions (2x tries here), and it just stops at the delay because the mode is other than away.

Also, even if I add the other modes and set the delay to 0 seconds, it still hangs up. It requires me to add at least a 1-second delay for every mode.

app:12502022-05-27 07:58:49.842 infoAction: Delay per mode:
                                                                                                   Away: 0:00:10
app:12502022-05-27 07:58:49.834 infoAction: On: Well Pump (Command only switches that are off)
app:12502022-05-27 07:58:49.817 infoAction: Set irrigationActive to true
app:12502022-05-27 07:54:25.886 infoAction: Delay per mode:
                                                                                                   Away: 0:00:10
app:12502022-05-27 07:54:25.876 infoAction: On: Well Pump (Command only switches that are off)
app:12502022-05-27 07:54:25.871 infoAction: Set irrigationActive to true

Bad assumption. Why include a mode for the action with no delay? You pick which modes to delay in. I will look into it.

You must show the rule main page here for me to have some idea what's going on.

Below is the rule. I only want a delay when AWAY, so as you can see in the first instance (action line 3) in this rule, I only selected AWAY as a mode for delay. This is where the rule just stops completely on other modes and never continues. The second instance of the delay (action line 9) is what I had to do to get the rule to continue for every mode. But I don’t want any delay for those modes. I can’t keep the modes deselect, and I can’t select 0 delay. If, for this action, I need to put in a delay for every mode, then each mode should not have a tick/check box next to it for which modes to select… they should just all appear as required fields to have a delay entered. Even if what I’m expecting isn’t intended, the rule should never just STOP running indefinitely. The action “Switches per Mode” doesn’t make you select every mode and stop if you don’t have every mode selected.


The work-around would be to use an (IF mode = away THEN Delay) statement.

Thanks. I will investigate this. And, I can replicate it. I think it has an easy fix.

1 Like

Fixed. Next release.

1 Like

Thanks, Bruce!