Here's what I see in the log segment above (redundant lines deleted):
- Code: Select all
Lutron RRA2/Caséta Debug Received a keypad button/LED status message: ~DEVICE,22,18,4
The plugin sees the status update that button 18 (raise) on device 22 was released. This is normal, button presses fire on the release.
- Code: Select all
Lutron RRA2/Caséta Debug A linked device (2 mBdRm rssBurLmps 003 - Both Switches) has been updated: True
That button press activated a linked device (set to True).
- Code: Select all
Lutron RRA2/Caséta Debug 2 mBdRm - kPd N - Button 063.04 - RSS Bur LED: actionControlDimmerRelay sending: '#DEVICE,63,84,9,1' to gateway 68394
The linked device was apparently Lutron device 63, LED 4, ON.
Please don't do this. Linked devices are for controlling NON-Lutron devices from Lutron keypads. Don't use them to control Lutron loads. Use Essentials to program Lutron devices to buttons.
- Code: Select all
Lutron RRA2/Caséta Debug Lutron IP Gateway: Sending: '#DEVICE,63,84,9,1'
The command was sent to Device 63.
- Code: Select all
Lutron RRA2/Caséta Debug Received command: ~ERROR,2 from Gateway 68394
The Lutron reported an Error for that command. Error 2 is "Object does not exist". So I guess you don't actually have a device 63, or the device doesn't have the LED specified.
So, get rid of the any linked devices that point to Lutron devices.
Separately from all that, I created a normal Lutron button press trigger for the raise/lower buttons on one of my keypads. The triggers fired as expected, so there's no problem using those buttons to trigger actions. HOWEVER, you need to be realize that the Lutron system is probably going to try to do other things any time you press those buttons. The default behavior for those buttons is to perform the appropriate raise/lower on whatever device(s) were last activated by that keypad. So if one of the other buttons was programmed to a scene, then you pressed the raise button, all of the lights in that scene would get bumped up. That might not be what you want to happen.
I do not have any custom engraved keypads with a single button replacing both raise/lower buttons. Apparently it defaults to "raise".