- It happens on BOTH of my hubs.
- It works on .135 and earlier.
Did you happen to try my simple example driver?
The problem is the attribute name "mode". This is colliding in RM with hub modes. That's a bug. Will look into a fix for this.
In the interim as a work-around, change the attribute name to something other than "mode".
Fix will be in the next release.
2 Likes
Thanks for figuring that out. Wow... A deeper problem than I'd have guessed.
@morse.caleb this is a tougher one for you apparently. I'd suggest considering creating a second attribute with a different name that mirrors "mode" so it doesn't break existing rules?
Or we just live with it for now?? Thoughts?
Given that there is a simple work-around, don't bother changing the driver. Just use all of the mode values as individual triggers, and you get the same effect as *changed*.
2 Likes
For sure, the work around is a good interim solution.
Somehow, I missed that you were going to fix it in the next release--I was only suggesting changing the driver if there wasn't a feasible fix. 
Glad you found the issue thanks so much!
And, it's a relief to know it isn't potentially affecting other "changed" triggers in RM 5.1.
2 Likes
Fix for this released.
4 Likes
