I have 15 rule in RM that use a button device as the trigger. All 15 of them are titled "Button controller - xxxx" where xxxx = the name of the device.
I have a couple existing button rules in RM4 and do not see this error on the newest firmware. It must be some certain setting or combination of settings causing it.
Honestly i planned to move the button controllers back into the resurrected app to clean up my RM section. I will take screenshots & then reapply the update tomorrow.
This is one of teh rules i was unable to access on 2.2.0.212
It’s always been like this. If I go in and create a new rule, select button device and just create an action for say button 1 double tap, I will get the same error when saving.
All my button devices are Zooz zen21,22,26 and 27. Maybe something funky with the Zooz driver???
Cannot duplicate this with the Zen22. I built a clone of your rule using all the pushed/held/released selected, and then was able to delete without error all but pushed 1 and pushed 2.
I know where the problem is, and will find a fix for it. We will see about getting that out in a hot fix release. There was a "fix" that broke it on line 274.
Thank you Bruce for confirming that it you have it covered. I will be happy to test any hotfix when available.
@neonturbo. I have confirmed that I am able to delete unused button actions from Zen21 and Zen22 button controller rules but I can not from Zen26 or Zen27 button controller rules. Interesting.
And this issue is actually affecting 8 (not 7) of my 15 button controllers. 7 are zen26 and one is Zen27. But I also have a couple zen26 and one Zen27 button controllers that did not show the issue. So definitely inconclusive.
I am also having trouble accessing a few of my rules. I am in the process of moving to Simple Automation and Motion Lighting as well as setting up modes instead of global variables and I am getting the following
