Solved: Help using Cooper Aspire RF9500 and Device Handlers

I am trying to use the Cooper Aspire RF9500 battery operated wireless controller
https://www.smarthome.com/cooper-wiring-rf9500aw-aspire-rf-wireless-remote-switch-alpine-white.html

And I can’t seem to get it to work. I have added it to my smartthings hub. However, whenever I push one button on the switch, it looks like it sends multiple button presses events instead of just one.

For instance, here is the Smartthings log, for one button press (pushing down) using the Cooper RF9500 Beast controller, registering several virtual button press events:

6:10:45 PM: info postEventToEndpoint: event successfully posted.

6:10:45 PM: debug Property Change Event switch: on (source: DEVICE)
6:10:45 PM: info postEventToEndpoint: event successfully posted.
6:10:45 PM: debug Property Change Event switch: off (source: DEVICE)
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is on.
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is on.
6:10:45 PM: debug CRF9500 – parse – Button Pressed

6:10:45 PM: debug description === zw device: 13, command: 2003, payload: 01
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is on.
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is on.
6:10:45 PM: debug CRF9500 – parse – Button Pressed

6:10:45 PM: debug description === zw device: 13, command: 2003, payload: 01
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is off.
6:10:45 PM: debug CRF9500 – parse – returned z basement guest switch is off.
6:10:45 PM: debug CRF9500 – parse – Button Pressed

6:10:45 PM: debug description === zw device: 13, command: 2001, payload: FF
6:10:45 PM: debug CRF9500 – parse – Button Pressed

6:10:45 PM: debug description === zw device: 13, command: 2001, payload: FF

If you look at the above log, you’ll notice that just one physical button press seems to register multiple button presses on the smart things log, and the switch seems to be toggling several times for just one button press.

I have tried this with using some different device handlers, and get similar results:
For instance, here is the log output using a different device handler, the Cooper RF Device Handler for one button push:

6:12:23 PM: debug Property Change Event level: 1 (source: DEVICE)
6:12:23 PM: info postEventToEndpoint: event successfully posted.
6:12:23 PM: debug Property Change Event level: 100 (source: DEVICE)

If you notice, this too seems to send two opposite events, 100 and 1, for just one physical push. The result is that the lights go off and immediately back on because one button push is sending two opposite events.

Any thoughts on how to deal with this? Many thanks!

Edit: I wound up using this device handler from thegilbertchan - GILBERT CHAN and that finally got it working

This worked in conjunction with a series of core rules that toggled the light.

1 Like