RM 5.0 Stop Repeating Actions Bug?

@bravenel

I have created a RM 5.0 rule that notifies me when I have left the refrigerator door open more than 5 minutes. It repeats every 2 minutes until the door is finally closed. I have a similar RM legacy rule for the freezer and it works perfectly. However, the RM5.0 does not stop the repeating actions as I think it should. For full transparency, for the purposes of this rule, I am using a virtual switch so I don't have to have the actual door open and I have lowered the times.

Here is the rule:

Here are the logs. As you can see, it appears that RM commanded the Stop Repeating Actions but it did not stop and is still notifying. The only way to break the cycle is to go into the Rule and Click the Update Rule button.

Has something changed from RM4 to RM5 in regards to stopping the repeatable actions or is this a bug?

Thanks,

Scott

1 Like

Probably just a bug -- no reason it shouldn't work. I'll investigate...

Yep, it's a bug. Found, fixed, will be in next hotfix release.

4 Likes

Yeah broken for me too (even on 2.2.8.136 ), I thought I was going insane! I even made a test rule and switched between simple conditions and full conditions to see if Simple conditions was broken.

But, stopping a repeat is definitely broken - this test rule will run forever unless I manually stop it:

Same issue reported above. Fix in next release.

2 Likes

Are we there yet? :wink:

I made the mistake of moving all of my door lock and HVAC automatons over and SWMBO is not impressed. :tired_face:

No. Not sure when we will push this out. It IS the weekend... Sorry. Turns out that Repeat was pretty messed up. Now, all fixed.

4 Likes

Love it !!

2 Likes

Soft! :rofl: It's Sunday morning here in Aus and I'm in my study working .... :crazy_face:

It looks like Button Rule 5.0 has this bug as well since it's based on the same code. Hotfix for both?

Yes, same code base.

Is not more a cosmetic thing? My rule stops with repeating but the text (Repeating) is not disappearing.
image

Yes, this is a known bug. Fixed in upcoming (today) hotfix release.

5 Likes

Confirmed fixed in 2.2.8. Thanks @bravenel :sunglasses: