Possible bug with RM 3.0 - push button Actions

I have two Lutron bridges (one downstairs, one upstairs) and have them integrated into HE. I use the Lutron app to define various scenes, which I then call within HE by sending a push button with the appropriate button number. For example: I will push "button 1" for my Lutron - Downstairs device (keypad), which is supposed to turn off all lights downstairs.

It works fine if I do it manually within the device properties page, but it doesn't seem to work in RM 3.0 as an action. Screenshot below shows where I call this action, all subsequent actions are not executed.

I also attached a log screenshot showing a Java type error when the rule was executed.

Curious if anyone else is having problems with RM 3.0 and push button actions...



What release are you running? If not the latest, please try it (129).

Hi Bruce,

I'm currently running the latest release (129), it also happened with the previous (126), and only with new rules I've created with RM 3.0. My existing rules created with RM 2.5 that use the push button actions work fine.

Yes, I can reproduce this bug. Investigating....

Glad to hear it's reproduce-able on your end. Thanks Bruce!

Found and fixed. Will be in next release.

1 Like

Awesome, thanks for the quick reply and resolution!

I hate bugs... The quicker they are gone the better.

3 Likes

If you hate bugs so much why did you create them in the first place. :wink:

@bravenel

Thanks Bruce! Confirmed this has been resolved in hotfix 2.0.9.132

2 Likes

I also think there is a bug in “control switches, capture or Restore”
When I click on “Restore” it only gives me an option to “Cancel this action”

Restore without a preceding Capture is meaningless. Put in a Capture action first and then this is what you'll get: