Repeat interval not right since update 2.1.6.118

C-4 hub, platform 2.1.6.118

I have a rule which announces when the garage door is open - during the day. I'm not getting
the 15 minute repeats that the rule calls for. Any ideas what is happening?

trigger: GD changed

Rule:
cancel delayed actions
set count to 0
if GD open
if time between sunrise and sunset
delay 15 minutes cancelable
if GD closed exit rule
repeat every 45 minutes
if GD closed exit rule
add 1 to count
log: Daytime GD open msg # %count% ....
END-REP
END IF
END IF

app:18552019-12-04 02:40:54.946 pm info@@Daytime garage door open message # 6
app:18552019-12-04 02:32:47.667 pm info@@Daytime garage door open message # 5
app:18552019-12-04 02:25:08.464 pm info@@Daytime garage door open message # 4
app:18552019-12-04 01:55:55.367 pm info@@Daytime garage door open message # 3
app:18552019-12-04 01:47:47.440 pm info@@Daytime garage door open message # 2
app:18552019-12-04 01:40:08.967 pm info@@Daytime garage door open message # 1
app:11912019-12-04 01:32:41.862 pm info@@ Garage Door opened at 01:32 PM on 04-Dec-2019

It appears this developed with my last update.....see logs below

2019-12-04 02:40:54.946 pm Daytime garage door open message # 6
2019-12-04 02:32:47.667 pm Daytime garage door open message # 5
2019-12-04 02:25:08.464 pm Daytime garage door open message # 4
2019-12-04 01:55:55.367 pm Daytime garage door open message # 3
2019-12-04 01:47:47.440 pm Daytime garage door open message # 2
2019-12-04 01:40:08.967 pm Daytime garage door open message # 1

2019-12-04 11:25:07.723 am Daytime garage door open message # 3
2019-12-04 10:55:53.858 am Daytime garage door open message # 2
2019-12-04 10:40:10.270 am Daytime garage door open message # 1

2019-12-04 10:10:53.575 am Daytime garage door open message # 1

2019-12-03 06:13:06.320 pm Daytime garage door open message # 1

2019-12-03 12:58:04.840 pm Daytime garage door open message # 1

2019-11-30 12:02:46.612 pm Daytime garage door open message # 5
2019-11-30 11:17:46.404 am Daytime garage door open message # 4
2019-11-30 10:32:47.111 am Daytime garage door open message # 3
2019-11-30 09:47:45.557 am Daytime garage door open message # 2
2019-11-29 12:37:00.895 pm Daytime garage door open message # 1

2019-11-28 03:58:49.496 pm Daytime garage door open message # 2
2019-11-28 03:13:49.265 pm Daytime garage door open message # 1

2019-11-28 02:28:49.111 pm Daytime garage door open message # 3
2019-11-28 01:43:48.963 pm Daytime garage door open message # 2
2019-11-28 12:58:48.698 pm Daytime garage door open message # 1

2019-11-27 05:43:16.672 pm Daytime gar door open message # 2
2019-11-27 04:58:20.008 pm Daytime gar door open message # 1

2019-11-27 04:13:16.040 pm Daytime gar door open message # 3
2019-11-27 03:28:16.666 pm Daytime gar door open message # 2
2019-11-27 02:43:17.084 pm Daytime gar door open message # 1

Now it appears to be working properly again . Perhaps it had something to do with the hub slowing or something unusual. I can't explain it.

@Bravenel - please comment

I didn't get any response from the posts above. So today I did another test. It seems if two conditions 1) time and 2) switch are reversed the repeat intervals specified will go bonkers. For the life of me I can't figure out why this is happening.

2.1.6.118 and Chrome on a WIN10 computer

Could I suggest that you remove your Log actions and turn on Action logging, so we can see what is happening with the rule. That will show the repeat logic.

Also, there are a number of things that unnecessarily complicate things. Two IF-THENs in a row should be a single expression with AND. No point in having a stopable REPEAT without anything that ever stops it.

Generally, the way I'd troubleshoot something like this is first to use much shorter time intervals to see if the structure works as expected or not. Then switch to longer time intervals once its solid -- makes it easier to find out the issues.

Screenshots are the preferred way to show things here.

I hope I have it to your liking Bruce. I'm so used to using the Snipping tool that I had to google screen capture. Anyway, in this short run two similar rules started together and should have repeated every 5 minutes. The two rules are identical except for the order of the AND statement, and the trigger virtual switch Vsw1 and Vsw2. It appears to me that the rule with Vsw1 died very soon after starting.

Looking at scheduled jobs for Vsw1 - there are none. For Vsw2 the one captured here is listed.

image

That's pretty strange.

Please show both rules, and turn on all logging for the rules (events, triggers, actions). You didn't by chance hit Done in that rule while it was running? as that would have stopped it.

What happens when you run the failing rule by itself?

I have them both running now with a 10 minute repeat, so by morning I should have a pretty long log.

I doubt that I hit DONE, I start the two with a rule that turns on both the virtual switches.

I don't have this totally figured out, but in the beginning it seems like if the repeat interval was in seconds everything worked fine. I originally came upon this situation because my wife is in the habit of leaving the garage door up. So I have a rule to give a message every 45 minutes - but the messages would come in as little as 10 minutes. They would be random lengths. That's when I started trying to figure this out. Get back to you tomorrow. Thanks for all you do Bruce. Like most others I'm crazy about Hubitat.

I switched to a 45 min period and they ran perfectly overnight. I'm going to have to work to recreate the problem that seems to have slipped away for now.

Well Bruce, please put this on the far back burner for now. I cannot reproduce the observations I documented in my initial post above. Sorry to have wasted your time.

No worries, and not a waste. There are times that mysteries like yours reveal hidden issues, so I'm happy to investigate.