I have a bunch of Lutron devices that I finally moved over to the Pro Hub so I could add them to my Hubitat. However, there doesn't appear to be a way to integrate the Lutron "4-Group Remote Control" properly.
I initially tried adding it to the Lutron Integrator as a pico remote, but for almost all buttons I get this error in the logs
java.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 74 (method parse)
I'm guessing it's just that the button is out of range as this remote has 37 buttons (or at least that's what the Lutron integration report contains). And, as I mentioned, some buttons do not throw the exception, probably the ones that are the lower button number. The driver for picos only goes up to 5 buttons, so I can't bump it up to see if that fixes it.
I've searched around but haven't had much luck finding any similar reports. Is there any way to either bump up the number of buttons on a pico or to natively support the shade remote?
I might be able to fix this without having one of these to test with if you're willing to do some debugging.
open live logging, then in the lutron telnet driver for the RA2 bridge, enable descriptionText logging.
Then for each button on the remote copy or write down the info text from the live log, there will be one entry for pushed and another for held, they look like this: rcvd: DEVICE,38,11,4
Once I get those I can create a driver for this.
@rlithgow1 Setting up as a keypad actually did work! And the driver for it, lets you specify how many keys you have as well. I'm not sure if I actually need to though since it seems to work if that field is blank (probably just error checking). It's a bit clunky as I still need to figure out all the key mappings, but it will do for now. I was trying to figure out what else would work, but "keypad" didn't trigger for me that it might work. Thanks!
@mike.maxwell Thanks! I'm not at the device right now, but it looks like using a keypad works too. It has a wonky set of keys though. You can select group 1-4 or all groups and then there is an "open", "close", "up" and "down" button after selecting the group. There's also a preset button too, but I'm not sure if it's tied to a group. Then each group+button combo selected shows up as a different button number (hence the large number of "buttons" in the integration). I'll still post the mapping tonight anyway, in case you want to create something more specific for the 4-Group remote.
I just realized the buttons are not contiguous in their numbering: there are only 25 (which makes sense from all the possible combinations of groups and commands). The integration report shows this as well but I missed the gaps initially. Anyway, here are all the entries with each button being held down and then released. The device ID is 4 in the Lutron Integration.
Shade
Button
Pressed
Released
All
Open
rcvd: DEVICE,4,2,3
rcvd: DEVICE,4,2,4
All
Preset
rcvd: DEVICE,4,3,3
rcvd: DEVICE,4,3,4
All
Close
rcvd: DEVICE,4,4,3
rcvd: DEVICE,4,4,4
All
Up
rcvd: DEVICE,4,5,3
rcvd: DEVICE,4,5,4
All
Down
rcvd: DEVICE,4,6,3
rcvd: DEVICE,4,6,4
1
Open
rcvd: DEVICE,4,10,3
rcvd: DEVICE,4,10,4
1
Preset
rcvd: DEVICE,4,11,3
rcvd: DEVICE,4,11,4
1
Close
rcvd: DEVICE,4,12,3
rcvd: DEVICE,4,12,4
1
Up
rcvd: DEVICE,4,13,3
rcvd: DEVICE,4,13,4
1
Down
rcvd: DEVICE,4,14,3
rcvd: DEVICE,4,14,4
2
Open
rcvd: DEVICE,4,18,3
rcvd: DEVICE,4,18,4
2
Preset
rcvd: DEVICE,4,19,3
rcvd: DEVICE,4,19,4
2
Close
rcvd: DEVICE,4,20,3
rcvd: DEVICE,4,20,4
2
Up
rcvd: DEVICE,4,21,3
rcvd: DEVICE,4,21,4
2
Down
rcvd: DEVICE,4,22,3
rcvd: DEVICE,4,22,4
3
Open
rcvd: DEVICE,4,26,3
rcvd: DEVICE,4,26,4
3
Preset
rcvd: DEVICE,4,27,3
rcvd: DEVICE,4,27,4
3
Close
rcvd: DEVICE,4,28,3
rcvd: DEVICE,4,28,4
3
Up
rcvd: DEVICE,4,29,3
rcvd: DEVICE,4,29,4
3
Down
rcvd: DEVICE,4,30,3
rcvd: DEVICE,4,30,4
4
Open
rcvd: DEVICE,4,34,3
rcvd: DEVICE,4,34,4
4
Preset
rcvd: DEVICE,4,35,3
rcvd: DEVICE,4,35,4
4
Close
rcvd: DEVICE,4,36,3
rcvd: DEVICE,4,36,4
4
Up
rcvd: DEVICE,4,37,3
rcvd: DEVICE,4,37,4
4
Down
rcvd: DEVICE,4,38,3
rcvd: DEVICE,4,38,4
I'm also not sure of the "official" name of the buttons (see here for a picture). Only "Open" and "Closed" are labeled and they usually make the shades open or close fully. What I'm labeling as "Up" and "Down" is the rocker next to "Open" and "Close": pushing the top of the rocker raises the shades (go up) while you hold it and pushing the bottom lowers the shads (go "down"). I guess alternate names could be "raise" and "lower" too. The "preset" button is just a grey/silver circular button on its own (somewhat similar to the 5 button Pico remotes).
this is an interesting one.
normally we would take a device like this and number the buttons left to right top to bottom.
However in this case the shade and all buttons modify the button numbers emitted by the top five buttons.
So we can just leave the mappings as is, which i think is confusing, or create a child button controller for each of the 4 shades, each of which would then have 5 buttons:
open:1, up: 2, close:3, down: 4 and favorite 5...
Agreed, it's a bit goofy the way the emitted button numbers change depending on the group selection.
The child controller idea is interesting, but how would you handle the "all" case? I can see why Lutron treats it as a separate button so that it can coordinate all shades well: They are incredibly well coordinated when opening and closing all of them, something that I haven't been able to do well by trying to trigger them individually with external automation.
I guess the "all" case could just trigger all the child buttons (unless someone needs to automate something different for "all" vs group X buttons being pressed). Alternatively, the "all" group could be conditionally created so that it could be a separate child if you wanted access to it directly.
