Button #5 controls 2 triggers - on & off - that manage a single z-wave device. It behaves very nicely, cycling the device, and the button LED reflects the status of the device.
Button #2 also controls 2 triggers - on & off - that manage 2 on & off action groups.
Button #2 behaves unpredictably:
- 1) Only sending ON signals, and the LED always on
- 2) Sending an ON signal, followed by the OFF trigger (the event log below illustrates this case)
(I have no idea what I do to switch between these two results, neither of which is satisfactory).
The event log after pressing the keypad button with the LED off:
- Code: Select all
May 31, 2022 at 6:16:31 PM
Lutron RRA2/Caséta Debug Received a keypad button/LED status message: ~DEVICE,64,2,3
Lutron RRA2/Caséta Debug buttonTriggerCheck: deviceID: 64, componentID: 2, gatewayID: 68394
[b]Trigger b off/TV Audio ON
Action Group b off/TV Audio ON[/b]
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" on
Lutron RRA2/Caséta Debug buttonMultiPressCheck: Timeout reached for keypadid = 68394:64.2, presses = 1
Lutron RRA2/Caséta Debug Received a keypad button/LED status message: ~DEVICE,64,2,4
[b]Trigger b off/TV Audio OFF
Action Group b off/TV Audio OFF[/b]
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" off
Above, the off trigger followed the on quickly (1-2 secs, with no additional button presses).
The Lutron iOS app only sends ON signals, and the button on the iOS never indicates on, but there is no off signal, as there is above with the keypad.
When the device is off, pressing ON on the Lutron app:
- Code: Select all
May 31, 2022 at 7:11:26 PM
Lutron RRA2/Caséta Debug Received a keypad button/LED status message: ~DEVICE,64,2,3
Lutron RRA2/Caséta Debug buttonTriggerCheck: deviceID: 64, componentID: 2, gatewayID: 68394
Trigger b off/TV Audio ON
Action Group b off/TV Audio ON
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" on
Lutron RRA2/Caséta Debug buttonMultiPressCheck: Timeout reached for keypadid = 68394:64.2, presses = 1
Pressing the app a second time, it does nothing:
- Code: Select all
May 31, 2022 at 7:11:44 PM
Lutron RRA2/Caséta Debug Received a keypad button/LED status message: ~DEVICE,64,2,3
Lutron RRA2/Caséta Debug buttonTriggerCheck: deviceID: 64, componentID: 2, gatewayID: 68394
Lutron RRA2/Caséta Debug buttonMultiPressCheck: Timeout reached for keypadid = 68394:64.2, presses = 1
To test the triggers and action groups in Indigo, I did the following:
1) executed the triggers manually, they performed as desired:
ON
- Code: Select all
May 31, 2022 at 6:49:10 PM
Trigger b off/TV Audio ON
Action Group b off/TV Audio ON
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" on
and OFF
- Code: Select all
May 31, 2022 at 6:49:26 PM
Trigger b off/TV Audio OFF
Action Group b off/TV Audio OFF
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" off
To be absolutely certain, I also tested the Action Groups by manually executing them:
- Code: Select all
May 31, 2022 at 6:17:34 PM
Action Group b off/TV Audio ON
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" on
May 31, 2022 at 6:17:58 PM
Action Group b off/TV Audio OFF
Sent INSTEON "b off/TV AnthemSonySonos AV aud vid" off
Since the triggers and the associated action groups behave as expected when manually executed from Indigo, my guess is that the problem is the is the Lutron/Indigo interaction. And since the keypad button presses differs from the iOS app, perhaps this is a clue?
I'm going a little crazy trying to implement the Lutron keypads, that sometimes work, and sometimes not.
If anyone has had a similar experience and has an idea what I might be doing wrong, or how I might fix this, I'd be very grateful. (Note - I tried manually turning both the buttons and the button LEDs on/off in the action groups, with no success).
