Help with Rule Design - Linking Lutron Ra2 and Z-Wave Lights

[Bullfrog]

I feel like this has a simple solution that I simply can't think of, so I'd appreciate your grace if this ends up being a, "duh" question.

I have 2 Lutron Ra2 Dimmers that are predominantly controlled by a seeTouch keypad (button 2, specifically) programed in the Inclusive Software set to a simple toggle (press it once, it fades the 2 dimmers on, press it again and it fades the 2 dimmers off). I'm trying to figure out a way to add 2 Z-Wave dimmers to that and keep them sync'd (so I don't end up with button presses turning the Lutron lights on and the Z-Wave lights off and vice-versa), but I'm struggling with how to program it. Basically, if any of the Lutron lights are on, I want the button press to turn off the Z-Wave lights (and the Lutron lights) and if the Lutron lights are off at the time of the press, I want the button press to turn on the Z-Wave lights (and the Lutron lights).

The reason it's a bit tricky is that you can't do a simple conditional action since the Lutron lights start moving as soon as the button is pressed, so no matter what, the state of the dimmers and LEDs on the keypad will be 'on' immediately after a button press - whether it is on it's way to 'on' or on its way to 'off'.

I'd prefer to not have to build in a wait for 2 seconds to check the state after the button press, though I suppose that could be an inelegant, utilitarian solution.

Any thoughts on how to accomplish this?

I know that another solution would be to remove the programming from the RadioRa2 software and do all of the programming via Hubitat instead, but I'd prefer to not do that.

Other possibly relevant thoughts: my Lutron keypad for some reason only reports button 'release' over the Telnet. Presses aren't reported. Also, since the the button is programed by the Lutron software, doubletap/hold functions of the Hubitat driver aren't available.

I have a feeling that the answer may be found in room lighting rather than in Button Controller/RM, but I actually haven't played with room lighting yet. If what I'm trying to do can be found there, you don't have to lay it all out for me, I can go do the research on it.

[rlithgow1]

Use the mirror app

[Bullfrog]

Thanks, I'll try that for now. I may keep tinkering though. I don't know that I want them constantly mirrored, I really only wanted the button to control it as described but still be able to manually control them individually.

[rlithgow1]

@Bullfrog

Other possibly relevant thoughts: my Lutron keypad for some reason only reports button 'release' over the Telnet.

This one is probably one for @bravenel or @mike.maxwell

[mike.maxwell]

Unlike picos the keypad events change if they have RA2 programming associated with them.

[Bullfrog]

I went with this combination of rules for the solution. As long as someone doesn't use the keypad to toggle both directions within 3 seconds, it should accomplish what I was looking for (3 second delay is fade + 1s cushion). I probably should have bought another dimmer during the BF sales so this wouldn't look so lame in execution.

[bill.d]

Your keypads should be reporting presses on Telnet, not releases. Here is one of mine:

And from the device:

I think the easiest way is to track the setting of the Lutron button LED in a Rule. When the Lutron scene is toggled on the LED goes on and then so will your non-Lutron lights. And vice-versa.

[Bullfrog]

@bill.d

our keypads should be reporting presses on Telnet, not releases. Here is one of mine:

And here's mine:

That said, is the 'w' type new and I missed it? I have all of my seeTouch keypads set as 'k'. Maybe I'll play around with that (Edit: I did and it changed nothing, which should have been obvious to me because it's not like it would change the Telnet communications from Ra2).

@bill.d

I think the easiest way is to track the setting of the Lutron button LED in a Rule. When the Lutron scene is toggled on the LED goes on and then so will your non-Lutron lights. And vice-versa.

Right,..that's sort of what I did in my solution above, so I think that we're on the same page there.

[Bullfrog]

@bill.d

Your keypads should be reporting presses on Telnet, not releases. Here is one of mine:

I'm a bit confused. It seems like you had the same issue a few years back:

Lutron RadioRA2 Keypad Press or Release?

I'd call it a "feature". You can use the keypad that sends 4 instead of 3 now to trigger something in Rule Machine, as it allows pushed and released for a Button trigger on a keypad device. If you want to send a Release in an action, you will need the next release of the platform. [50%20PM]

maybe I'm misunderstanding what happened in that thread.

[Bullfrog]

I figured out what you were discussing there 3 years ago. Looks like I had all of my keypads set to "save on hold" or whatever it's called, which makes the telnet report releases rather than presses. I changed them and now I see presses.

Of course, now I either have to change it back or change a ton of rules.

[bill.d]

Interesting. I've never used that feature. Others have, though, with similar issues.

Potential Bug Affecting 3rd Part Integration