That's very odd, that it doesn't show the ~DEVICE,54,6,3 for that keypad. Please push a different button on that same keypad, and see what is in the Lutron Telnet logs from it.
Could you try an experiment: Open a telnet connection to your RA2 system. Username is lutron, password is integration.
Type in this command: DEVICE,54,6,3
Then see if (a) that activates the Away scene, and (b) what comes back from the system via telnet.
Good idea bravenel. FWIW, from the Telnet prompt you need a # sign in front of the command.
Anyway, #DEVICE, 54, 6, 3 does crickets. #DEVICE, 54, 6, 4 fires off the scene. It sure seems like the release is what is needed for a Lutron RadioRA2 keypad - at least with the latest software. I haven't played around with the Lutron integration protocol in quite some time so I can't tell you whether it worked differently before.
It sounds like your sw release that supports "release" on the keypad will solve my problem. Just not sure why no one ran into this before...
I will have to upgrade my RA2 system, which I have not done yet. I haven't seen this behavior before, and I have many RA2 scenes that are fired by "pushing" a RA2 keypad button, either physically or from Hubitat apps. It may be something that changed in the latest RA2 firmware, don't know.
Very interesting. 12.2.1 comes with some other not-so-nice-to-haves including (silently) dropping support for the Connect Bridge 1. I was an early adopter of the Connect Bridge so have a 1 instead of a 2. It is a strange drop of support since my Connect Bridge appears to still work as before - but it shows up as unavailable (or something like that) from the RA2 desktop software when you update the system. This is reported on the Lutron forums as well, but I didn't see that until after I upgraded. Anyway, I'll either have to buy an upgraded bridge at some point if Lutron won't provide an upgrade.
Anyway, this shouldn't matter for integrating with Hubitat (since you are using telnet protocol) though could trip people up if they delete the default logins on the device - as is suggested on the Lutron upgrade to 12.2.1
I'm certain they will replace it if need be.
We are aware of the logins issue. For now we will deal with that through documentation. As if changing the default somehow makes it more secure?
My keypads (regular and hybrid) only send push events (3) for buttons 1-6. There are no releases. Buttons 18 and 19 (the down and up arrows) do send both push and releases. And that is the spec as far as I know. It will be interesting to see how Hubitat derives a release for buttons 1-6. I'm on 12.2.1 Essentials.
We can't if Lutron doesn't send it. The reason for adding release was to support 18 and 19. But here we have a keypad sending a release instead of a push for button 6, which I've never seen before. The fix to support release will allow this to be used.
I took a quick (not thorough) look through the integration docs and didn't see any device with a 4 as a push. So unless there is some other device that I didn't see the updated app programming seems more of a way of routing around an issue. I would think that all releases would have a preceding push.
@arno - what model keypad is this?
It would be easy to test. I'm thinking this is indeed a release. But, the way to tell is to have a telnet session open, hold the button down, and then release it. The DEVICE,,4 should come then, not on the initial push.
It is a regular keypad - RRD-W6BRL. I haven't checked a hybrid keypad but will and report back what I see.
Bravenel - I opened a telnet session and held button 6 on the keypad. Nothing in the Telnet logs, no response from the system. When I released the button, the log showed the release and then executed the scene.
Also, while I don't think this is relevant, this is an old RadioRA2 system, installed in 2012. Originally started on 5.0.1 software, been continuously upgraded to the latest version of software over the past 7.5 years.
The button in question is tied to a "shared scene" that is my Away scene.
Thanks. I will update my system tomorrow and investigate a bit more.
i wonder if the "Scene Saver" feature - which is an advanced feature of the keypad and turned off by default - is what is causing this behavior difference. i have "Scene Saver" enabled on all my keypads which allows press and hold to save levels after initial programming. It is an advanced option you can control by right clicking on the keypad from the Inclusive software.
I ran a test. It is the scene saver setting ("Save changes on button hold" in the software) that is causing the press event to be 4 instead of 3.
Well, there you go. So, I don't think the "push" event is a 4 - it is a release event and the semantics of the way keypads work with scene saver is that "release" (i.e. 4) is what fires off the scene. There is no "push" event that has any meaning with scene saver on - except to the extent the system gobbles it up and does something if you hold long enough.
Anyway, it sounds like the sw update that allows a release to be sent for a particular button will address the issue.
Maybe. But I'd call it a bug. Releases always are preceded by a push. And all other Lutron button pushes are 3s. Telnet is for 3rd party control and this issue will screw them all up unless the 3rd party system also has a setting for this scene saver function.
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.
OK. Sounds good. I need the release in an action so will need to wait. FWIW, "scene saver" has been part of RadioRA2 since 6.0 - early 2013. So, feature or bug, it is just a question of how many people have it turned on. It is off by default so perhaps is not tripped over much in the wild.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
