Hi all, I found a previous thread that indicated that driver support was coming soon for RA2 keypad hold/double-tap actions "Lutron Pico Keypads: Held/Double-Tap?"
Does anyone know if this actually occurred? I just tried to create a Rule Manager rule for hold and double-tap and it doesn't seem to work, nor do any hold/double-tap events show up in Hubitat logs.
What driver are you using?
Yes, these commands are implemented for Lutron See Touch Keypad driver.
I'm using the default Lutron Integrator "app". I'll see if I can find the driver mentioned by @bravenel.
The app creates devices, and the devices use a driver. You shouldn't need to do anything spcecial (unless you chose the wrong device type in the app).
What hub platform version are you on? Check in Settings > Hub Details.
I'm using Platform Version 188.8.131.52, Hardware Version Rev C-8.
If I open up a keypad device, I see the commands "Led Off, Led On, Lutron Keypad, Parse, Push, Release, Updated". The devices are set as "k" type in the configurator.
You need to update your hub to 184.108.40.206, the latest. Also, confirm that the driver (Type) shown is Lutron See Touch Keypad. If it isn't that, change to that.
OK, thanks, I updated the hub and set the type correctly for all the keypads.
However I'm still not getting double-tap triggers; when I look at the logs after a double-tap I see some errors of the form:
dev:10 2023-11-12 07:00:04.808 PM info rcvd: OUTPUT,12,1,100.00
dev:10 2023-11-12 07:00:04.736 PM info rcvd: OUTPUT,21,1,100.00
dev:210 2023-11-12 07:00:04.707 PM error java.lang.NullPointerException: Cannot invoke method size() on null object on line 111 (method parse)
dev:10 2023-11-12 07:00:04.693 PM info rcvd: DEVICE,104,1,3
dev:10 2023-11-12 07:00:04.566 PM info rcvd: OUTPUT,12,1,100.00
dev:10 2023-11-12 07:00:04.492 PM info rcvd: OUTPUT,21,1,100.00
dev:210 2023-11-12 07:00:04.460 PM error java.lang.NullPointerException: Cannot invoke method size() on null object on line 111 (method parse)
dev:10 2023-11-12 07:00:04.445 PM info rcvd: DEVICE,104,1,3
Hit Save Device or Save Preferences. That device is not properly initialized.
Just had a chance to dig in here again. Turns out I'm seeing this across many (all?) keypad devices, even after explicitly hitting Save Device/Preferences.
Here's a screenshot of one particular keypad throwing these errors, anything jump out at you?