Here is a link to the DH for the cooper aspire scene controller device handler. I have done limited testing with my two controllers. If you have one of these controllers please give it a try. The file can be found on git hub at the repository below.
The path below is the git hub location for 1.9.
It sounds like you have it set right. The configuration process is slow and will take several minutes. It’s best just to watch in the logs and don’t touch any buttons. Push the configure scenes button again and wait for it to complete before testing.
The scene controller DH can provide the following functions via smartThings:
It will provide 5 buttons with button pressed events that can be used to trigger events in ST. This functionality works with the Smart Lighting app.
It provides five attributes for indicators showing their current state (on off). Applications can be triggered via a button press and then use the indicator attributes to determine/check the current on off state. This will work well with CoRe and other apps that allow access to device handler attributes.
It provides commands to toggle or set the indicators. These work with CoRe and other apps that have access to commands. There are 5 toggle commands that change the state of the associated indicator. The IndicatorSet command requires two parameters: Indicator number (1-5) and on or off (1 or 0).
It can be configured to control zwave devices directly via association. The user must enter node ids and desired levels/states in the preferences per instructions.
It can be configured to control zwave devices directly via scene commands. For this to work the target devices must support the Scene Activation 0x2B command and they must be configured with the scene Scene Actuator Conf 0x2C command separately. Check your device Raw Description for 2B and 2C. A custom device handler is need to set these devices up (see below for an example).
Devices actuated via 4 and 5 above will continue to function without the smartThings hub online. (This is useful for applications where things are dedicated. I have a controller at the nexus of the kitchen, living and dining rooms right where the builder should have put a bank of switches but didn’t. I would not want this to stop working if ST or the internet stopped working).
I’ve tested this device handler with some Linear Dimmers (scene controlled) and some GE, and zwave4less switches via association. I’ve done some testing of the interaction with smartThings. I see three modes of use available to the user:
A. Use the default config settings and use smartThings app like CoRe to activate any other SmartThings devices.
B. Use a scene/association configuration and let the controller send commands to devices.
C. Use a combination of A and B and let SmartThings extend the controllers capabilities to non-zwave devices.
I’ve forked the device handler by snailium for the gocontrol-linear-2gig-dimmer-switch and added scene configuration capabilities. There seems to be some bugginess with updating the tiles but the configuration works. I’ve boxed the code I added with comments so if you want to copy it to mod another DH you can. Below is a link to the github fork.
Please take a whack at using this and let me know how it works. I am new to programming this stuff and I know the code needs some cleaning up and likely bugs fixed so any help is appreciated. There are a few limitations:
- The 6th button on the controller is an all off button. It is intentionally not supported as a separate button in the DH. However, it works as intended by the device designers. It signals an off command for all other buttons that are on. The indicators and button presses for the other five will report to ST their status properly.
- The device uses button hold to dim or brighten scene controlled zwave devices. There is no support for ST in the DH for button holds as I could not find a way to determine which button was held. Perhaps future support.
- A better implementation would be a 5 switch parent/child DH. The was beyond my skill set for programming currently. Perhaps it can be implemented in the future.
- There is no support for remotely activating a button. I could not find a way get the device to respond on any such commands. The indicators can be turned off and on. The button will respond appropriately when pressed following a remote change of the indicator. Pressing a button after turning the indicator off will turn on the “scene”. Pressing a button after turning the indicator on will turn off the “scene”. While setting the indicators does not control devices it will be useful for setting the desired button state. If your group of devices are turned off via ST by other means then turn the indicator off and the RFWC will be ready to activate those lights again.