GE 46203 association group 3 not acting on tapped device on up_2x, down_2x events about smartthingscode HOT 2 CLOSED

If you're trying to do a direct association with another Zwave device, they both need to be the same level of security. If one device is S2 encrypted, and the other is S2 failed, or ZWAVE_LEGACY_NON_SECURE, they will not be able to communicate with eachother. If all devices are S2 capable and one failed, you'll need to exclude, and reinclude it being sure to scan the QR code during inclusion. If all devices don't support S2 inclusion, you can exclude the S2 secure device, and not scan the barcode, forcing it to downgrade the security and communicate with older non S2 devices. Because 2 of your 3 devices work to associate, I highly suspect the security settings not being on the same page as the problem.

Workaround also could be just to use an automations (automation screen in new app, smartlighting, or webcore) to control the third light that can't be controlled by association. Also, the trigger of direct associations between this switch and other devices will not show in the logs, as they bypass the hub entirely and the devices communicate direct with each other. Generally when the device turns on, it then communicates back to the hub that it turned on/off, but that's after the fact and could be delayed.

To further diagnose if its a security issue you can attach screenshots of the device's data box obtained from the IDE. Let me know what you find.

from smartthingscode.

Closing issue as problems appear unrelated to the code of the device handler

from smartthingscode.