RFWC5AW Cooper scene controllers do NOT work with Vera Lite or Edge

I’ve spent the better part of 100 hours trying to get these to work. I have 6 of them. I’ve repaired, switched from Lite to Edge. The best I can do is put in a 1 second delay in the scene, and the scene will turn on, but NOT off. There also seems to be communication issues. The UI7 interface will say something like: ‘Setting User Association’, and then eventually go ‘red’. The Edge controller is line of site in a Church sanctuary to all the scene controllers.

My process: 1) add device, choose ‘Generic’. 2) when device is paired, choose ‘Select scenes for device buttons’, and enter ‘5’.

From there, I’ve tried both associating the scene with the buttons from the device itself, and from scene control, and nothing works.

Any advice? What logs can I look at in the Vera? I am fairly familiar with linux, etc…

See here for a full write up on how to use this scene controller:

http://forum.micasaverde.com/index.php/topic,22913.msg154671.html#msg154671

I read this tutorial, but it is prior to UI7. I had ALL the cooper buttons, including the ‘all off’ button working at home an a Vera 3, but with single lights on each scene. Perhaps its related to multiple lights, but I’ve tried test scenes with single switches within a scene and it still doesn’t work.

It sounds like what you did in step 2, is go into the device and into the scenes menu and answered the question how many buttons does the scene controller have and you entered 5.

Don’t do that, the scene controller won’t work if you do that.

You may need to unpair the device and start over.

Instead after you pair the device, do nothing more on the device menus. And go to the scene you want to use with button 1, and add a trigger using the scene controller and select, when a scene is active and then enter 1 for the which scene question.

When you click the button again (to turn off LED), that is scene 0, and unfortunately is the same for all buttons. You still use when a scene is active for this one but use 0.

So the tutorial I linked to above is still pretty much correct above even for UI7, you just need to resist answering the question, how mant buttons does the scene controller have, in the device.

OK, unpaired, repaired.

Did NOT go and enter ‘5’ as number of buttons. When I go to a scene and try to active a button, it says:

A scene is activated
Which scene numberNo buttons available on controller

So, that was a bust…

BUT, I put in ‘5’, Then I ran this command on the lights in the scenes I wanted to control:

http://192.168.0.5:3480/data_request?id=lu_variableset&DeviceNum=17&serviceId=urn:micasaverde-com:serviceId:ZWaveDevice1&Variable=IgnoreDirectScene&Value=1

where 192.168.0.5 is my IP, and the device ID is 17…

Comments?

I have this scene controller mostly working. Occasionally one light in the scene will remain on… And device status isn’t updated. Lights are off but the interface shows them as on.

Cool, so what did you end up doing? Just putting 5 in the “How may buttons does your controller have” question? Maybe your problem is that you can’t set a scene to button 0 which is the Scene off button number (same for each button).
I notice in the iphone Vera app you can create a scene and free type in the button number, that might let you work arround the fact that 0 wouldn’t normally be listed.

But only do that if you want all the buttons to have the same "off " action.

Setting the ‘IgnoreDirectScene’ variable. I found a post from 2011 that suggested that variable.

But I’m still bothered that the device status doesn’t update.

More info as to how the Cooper 5 button was working for me… I paired it, entered 5 for number of buttons, and assigned scenes. One press, scene came on, light by button got brighter, press again, scene went off, light got dim again. Press “all off” button, all scenes that are on go off. ONLY problem is that I’ve got 2 switches and 14 dimmers, and occasionally one light will stay on. Also, device status doesn’t update. Basically, controller is working exactly as advertised, except for the occasional light left on, and status.

Just want to add a “Me Too” to what kirbyb is reporting here. This controller mostly worked with UI5. Now it’s a disaster. Used to be: Push, scene goes on, push again, just that scene goes off. Now you either get the scene going on, and nothing on off, or it just doesn’t take at all, and the button does nothing.

Whatever is going on with this “Scene zero on deactivate” thing is not how it used to work, and not desirable.

Basically everything on the forums and wiki about this controller are unusably out of date.

OK, after reading this doc:

http://www.cooperindustries.com/content/dam/public/wiringdevices/products/documents/technical_specifications/advancedtechinfo_V2.pdf

I manually sent the device a group association with an empty node list, and then re-configured my scenes. This mostly worked (scenes that control dimmers worked. The one that controls a switch didn’t).

Subsequent changes to my scenes do not work, unless I manually set some group association in the device options section, and then un-set the group association, and then re-configure the triggers for my scenes. I think this is related to the “The second Association_Set command is for all devices with another level. The third Association_Set command is for all devices with yet another level. And so on.” mentioned in the Cooper Document. Perhaps this isn’t being taken into account when the Vera Lite sets associations by scene?