@chris Quick question regarding association groups. Now that my switches are upgraded to the new firmware and the switches report back dim changes from the physical paddle. How do association groups work to sync two switches together.
Right now i have Switch ONE a member in Association Group 1 on Switch Two
and
Switch TWO a member in association Group 1 on Switch ONE.
Is there anything else i need to do to make this work?
Iâm not sure I follow this? The binding definately supports associations. If the device doesnât, or the database doesnât include this feature, then of course you canât configure it.
That should be everything if the device is sending the multi-level commands now. It should send the command to whatever devices you add to these groups.
Has anything changed in the device configuration? Eg does it now support more association groups, or some other way to configure what commands get sent? Often devices will provide different groups that send different messages, or a config parameter to do this - given this device used to send the scene command, and now sends multi-level-switch, I suspect something has changed? If so, we might need to change something in the database to update it for the new firmware which would require adding a different version.
I donât see any new features; still only âGroup 1â under the Association Groups tree.
Hereâs what i see in habmin:
Hereâs Debug Logs from two events:
Dimmed to 47% on the paddle:
13:52:16.952 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:16.964 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:16.975 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:16.986 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:16.997 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:17.027 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:17.250 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:17.265 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:17.278 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:17.293 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:17.309 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:17.329 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:17.484 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:17.493 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:17.502 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:17.511 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:17.520 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:17.541 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:17.675 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:17.685 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:17.696 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:17.703 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:17.713 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:17.725 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:17.867 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:17.878 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:17.887 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:17.896 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 1
13:52:17.905 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:17.943 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=1, scene=1}
13:52:18.101 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:18.111 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class SWITCH_MULTILEVEL (0x26)
13:52:18.121 [DEBUG] [veMultiLevelSwitchCommandClass:95 ] - NODE 10: Received Switch Multi Level Request
13:52:18.131 [DEBUG] [veMultiLevelSwitchCommandClass:115 ] - NODE 10: Switch Multi Level report, value = 47
13:52:18.141 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:18.165 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 47
Dimmed up to 68% on the paddle:
13:52:47.492 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:47.503 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:47.513 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:47.523 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:47.533 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:47.552 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:47.713 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:47.732 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:47.742 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:47.756 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:47.771 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:47.794 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:49.030 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:49.041 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:49.058 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:49.069 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:49.078 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:49.094 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:49.226 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:49.237 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:49.246 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:49.254 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 2
13:52:49.263 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:49.293 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=2, scene=1}
13:52:49.441 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:49.451 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class CENTRAL_SCENE (0x5b)
13:52:49.460 [DEBUG] [.ZWaveCentralSceneCommandClass:77 ] - NODE 10: Received central scene command (v1)
13:52:49.469 [DEBUG] [.ZWaveCentralSceneCommandClass:84 ] - NODE 10: Received scene 1 ; key 1
13:52:49.478 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:49.495 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = {key=1, scene=1}
13:52:49.650 [DEBUG] [ApplicationCommandMessageClass:41 ] - NODE 10: Application Command Request (ALIVE:DONE)
13:52:49.661 [DEBUG] [ApplicationCommandMessageClass:146 ] - NODE 10: Incoming command class SWITCH_MULTILEVEL (0x26)
13:52:49.671 [DEBUG] [veMultiLevelSwitchCommandClass:95 ] - NODE 10: Received Switch Multi Level Request
13:52:49.680 [DEBUG] [veMultiLevelSwitchCommandClass:115 ] - NODE 10: Switch Multi Level report, value = 68
13:52:49.691 [DEBUG] [b.z.i.protocol.ZWaveController:668 ] - NODE 10: Notifying event listeners: ZWaveCommandClassValueEvent
13:52:49.709 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 68
No - nothing will change here. The question is if anything changed in the firmware - if so, we need to get a new manual that describes any new features etc⊠Then we can update the database with this info, and then it will be available hereâŠ
Please when you post logs, can you format them with the </> button. By pasting them in as a quote I canât easily process them and they are hard to read.
The logs wonât show what (if anything) the device is sending to another device, since this has nothing to do with the controller - itâs a direct transaction. I would expect this to be documented in an updated manual.
My bad! I corrected all my posts above to use the </>.
Iâll email them and see if i can get an updated manual with the changes for this new firmware they will be releasing.
Sorry, I was definitely not terribly clear. First, I assumed that the database doesnât know about these particular modules because these messages show up in the log:
2016-12-11 00:00:34.223 [DEBUG] [.z.i.config.ZWaveConfiguration:288 ]- NODE 7: No database entry: Linear [ID:3331,Type:4457]
2016-12-11 00:00:34.225 [DEBUG] [.z.i.config.ZWaveConfiguration:288 ]- NODE 8: No database entry: Linear [ID:3331,Type:4457]
Based on that assumption, I guessed that the modules get a default level of support because either the binding knows what to do somehow based on responses from the modules, or because I assigned âSWITCH_MULTILEVELâ to them in the item definition. One way or the other, the get some basic level of functionality, even though theyâre not in the database.
What they donât seem to get, based on the fact that I canât seem to make associations, is support for associations. That may be because theyâre not in the database or because they donât support associations, and trying to figure out which it might be based on the Linear instructions is (ahem) difficult at best.
So I realize that the binding does support associationsâand I didnât mean to imply that it doesnâtâbut for some reason associations arenât supported for these modules, and it could be because theyâre not in the database or it could be because they donât support associations in the first place.
Howâs that for a long, drawn-out explanation? 
The modules get âfullâ support - the database isnât used other than for configuration in OH1. So, you can configure all the items etc, you just canât configure the device without the databaseâŠ
But yes, basically your understanding is correct I think.
If the device isnât in the database, then it wonât show any associations - or configuration - so you canât configure it. Iâd suggest to try and add them to the database (maybe they are already in the online database, which means they just need to be added to the OH1 repository).
Hi guys,
Iâve got a HS-WS100+ and am trying to set up the double/triple tap scene control within OpenHAB.
This is my configuration (which I saw from @billeccles in another thread):
Switch KitchenZ âKitchen Lightâ { zwave=â7:command=SWITCH_BINARYâ }
Number KitchenZ_1TU âKitchen Light_Scene 1TUâ { zwave=â7:command=CENTRAL_SCENE,scene=1,key=0â }
Number KitchenZ_2TU âKitchen Light_Scene 2TUâ { zwave=â7:command=CENTRAL_SCENE,scene=1,key=3â }
Number KitchenZ_3TU âKitchen Light_Scene 3TUâ { zwave=â7:command=CENTRAL_SCENE,scene=1,key=4â }
Number KitchenZ_1TD âKitchen Light_Scene 1TDâ { zwave=â7:command=CENTRAL_SCENE,scene=2,key=0â }
Number KitchenZ_2TD âKitchen Light_Scene 2TDâ { zwave=â7:command=CENTRAL_SCENE,scene=2,key=3â }
Number KitchenZ_3TD âKitchen Light_Scene 3TDâ { zwave=â7:command=CENTRAL_SCENE,scene=2,key=4â }
The SWITCH_BINARY works just fine, but none of the others do.
In my debug log, each of the Number items have these lines associated with them:
2016-12-20 14:26:15.377 [ERROR] [.i.ZWaveGenericBindingProvider] - KitchenZ_1TD: Invalid command class 'CENTRAL_SCENEâ
2016-12-20 14:26:15.569 [ERROR] [i.internal.GenericItemProvider] - Binding configuration of type âzwaveâ of item âKitchenZ_1TDâ could not be parsed correctly.
2016-12-20 14:26:15.622 [DEBUG] [rg.eclipse.jetty.server.Server] - RESPONSE /services/habmin/zwave/nodes/node7/ 200
Originally, I was using the zwave binding version 1.8.1, and noticed that in Habmin, the device was not properly identified. So I tried updating the binding to 1.8.3, and now none of the information will load in Habmin, but my existing zwave devices still work. Do I need to update my OpenHab runtime to 1.8.3 as well for the binding to display properly in habmin? And more importantly, how can I use the CENTRAL_SCENE command class on this switch?
Thanks
I suspect that you need to be using the 1.9 ZWave binding. You can just update the binding - the runtime can stay the same.
Updated the binding to 1.9, and now the device correctly shows in Habmin. However, Iâm getting a slightly different error message now:
2016-12-21 11:21:06.547 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No command class found for item = KitchenZ_1TU, command class name = central_scene, using 0 refresh interval.
The case wonât matter. Iâm not sure why you would get this error. The 1.9 source definitely has this class and Iâm pretty sure people are using itâŠ
Did you get the binding from cloudbees?
Yes, I downloaded from this link: https://openhab.ci.cloudbees.com/job/openHAB1-Addons/org.openhab.binding$org.openhab.binding.zwave/lastSuccessfulBuild/artifact/org.openhab.binding/org.openhab.binding.zwave/1.9.0-SNAPSHOT/org.openhab.binding.zwave-1.9.0-SNAPSHOT.jar
Delete the XML file for this device and restart OH. Itâs possible (likely!) that itâs not included as itâs cached the command classes and it wonât therefore see the new class.
Where can I find that XML file? /opt/openhab/âŠ
Edit: NVM, found it, in /opt/openhab/etc/zwave/
Chiming into revive an older thread here for some clarification.
Iâm currently on GE switches 12xxx series, that arenât not supporting instant status. I wanted to check here as I see a few folks who apparently are testing/using the HomeSeer HS-WS100+ and HS-WD100+ devices. Are these successfully reporting back via instant status? There seems to be some positive news relative to the newer firmware supporting report back of the SWITCH_MULTILEVEL via ASSOCIATIONS which I believe to understand as the requirement for instant status updates in OH.
My problem is that Iâd like my dimmers/switches to report their manual change at the switch instantly to OH. I thought Leviton was the only switch that could do this, but it seems the HS devices will support this - looking to just get some confirmation from other OH users before I order $1k+ of these devices.
@Python it seems you were the one blazing the trail here that I followed from another thread as well with updating using the demo HS3 software for the OTA update. Hopefully you can confirm/deny my assumption above.
Out of the box this does not work. You will need to update the firmware on the switches to 5.16. This firmware isnât released yet but support gave it to me. You can perform this update with HS3 demo software that is valid for 30days. Theres one bug in the software which is why they havent released it â once you perform an OTA update it loses itâs association with the controller and you need to include it again. But once itâs updated youâre good to go!
Once you have this firmware installed any change in dimmer value is reported back to OH. This includes virtually changing the dimmer value as well as using the physical up and down paddles. Anytime that switch changes OH knows the value instantly.
I HIGHLY recommend these switches to anyone with that update. Between instant status (after OTA update) and the double/tripple tap scene control gives you so many options! The only thing I wish they had was a way to change teh LED colors on the dimmer value indicator. Would work as a unreal notification for specific tasks iâm doing (eg. a timer running). Trying to figure out a better way to do that so i know when a timer is running to auto-turn off the lights.
Iâm going to be ordering more switches and plan on doing a full documented video of my setup which i think a lot of people would enjoy and give some insight into how you can integrate these switches.
Hereâs a quick demo i posted on FB demonstrating my setup. Still need to get 2 more switches to control the rest of my lighting so ignore the unmatched switches for now
https://www.facebook.com/coryschak/videos/10154862763393886/
In a quick nutshell this is utilizing the instant status reported back to OH to control a second switch in my detached garage which is my soffit lighting.
When double tapping the switch ON, it will sync dimmer value between both switches. If i change the dimness on this switch, its reported to the second switch in the garage and changes that value as well.
I have since integrated this switch a lot further which iâm waiting to show once i have the other switches installed.
My rule for dimmer switch in OH2:
//***********************************************************************************************************************************************
// DRIVEWAY SOFFIT DIMMER SCENE CONTROL *
//***********************************************************************************************************************************************
/* House Side Dimmer SCENE Control -- Scene Tap Selection Syncing */
rule "House Soffit Side Dimmer: Scene Tap Selection Syncing"
when
Item Light_House_Soffit_Scene received update
then
switch(Light_House_Soffit_Scene.state) {
/*ON*/
case 1.0 : { /* Single Tap ON */
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Single Press ON")
//CANCEL OFF TIMER CREATED FROM DOOR OPEN BY PRESSING UP ONCE
if (tHouseDoor !=null) {
tHouseDoor.cancel()
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Canceling tHouseDoor Timer. Single Press Up Received")
tHouseDoor= null
}
}
case 1.3 : { /* Double Tap ON */
logInfo("RULE.LIGHTING.Light_House_Soffit", "Double Press ON")
//DOUBLE TAP - SYNC TURN LIGHTS ON AND ENABLE DIMMER SYNC
if(Light_House_Soffit.state == 0){
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Turning Lights ON and Syncing Switches")
sendCommand(Light_House_Soffit, ON)
sendCommand(Light_Garage_Soffit, ON)
postUpdate(dimmerSync,2)
}
else {
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Syncing House Dim Value to Garage and Syncing")
percent = ((Light_House_Soffit.state as DecimalType)).intValue
sendCommand(Light_Garage_Soffit, percent)
postUpdate(dimmerSync,2)
}
//DOUBLE TAPPED WHEN DIMMER SYNC IS ENABLED
//BREAKS THE SYNC.
if(dimmerSync.state == 2){
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Dbl.TAP --> Disabling Dimmer SYNC")
postUpdate(dimmerSync,0)
}
}
case 1.4 : { /* Tripple Tap ON */
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Tripple Press ON")
postUpdate(dimmerSync,3)
sendCommand(Light_House_Soffit, 2)
sendCommand(Light_Garage_Soffit, 5)
}
/*OFF*/
case 2.0 : { /* Single Tap OFF */
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Single Press OFF")
}
case 2.3 : { /* Double Tap OFF */
logInfo("RULE.LIGHTING.Light_House_Soffit", "--> Double Press OFF")
postUpdate(dimmerSync,0)
sendCommand(Light_Garage_Soffit, OFF)
sendCommand(Light_House_Soffit, OFF)
}
case 2.4 : { /* Tripple Tap OFF */
logInfo("RULE.LIGHTING.Light_House_Soffit", "-->Tripple Press OFF")
postUpdate(dimmerSync,0)
}
}
end
@Python - THANK YOU! this is a phenomenal response and exactly what I was looking to hear. I had suspicions, and my ZWave knowledge isnât strong enough to feel fully confident. Unfortunately my order of GE switches screwed me, now Iâm just trying to find the cheapest place to buy 29 of these switches (WS/WD/WA models varying counts). Itâs a heavy cost, so searching for any discount avenue. So far, looks like smarthome.com with their 20% off is the best - but unfortunately they donât have them all in stock and wonât necessarily for awhile. 
Called and found out their current backorder was ordered in Dec from HS, and is just now set to arrive next week.
Trying to order from HS now directly with their packs that save some money here and there, just trying to scour the internet for a direct HS 10% coupon or something. My bigger rush is to replace the GE switches now, as Iâm going to try and make a claim with my CC company for âReturn Protectionâ - basically offers to refund you for things you purchase that you may not be happy with after ordering but within 90 days of purchase. 2/8 is the end of that 90 day window 
- any suggestions greatly appreciated.
Enough of my money ranting - onto the functionality. Iâm excited to hear this all works as expected and with the 2x/3x tapping as well. I never had a switch capable of that, but definitely have some uses for those. Things like using a 2x for turning off all the downstairs lights when going to bed, or just turning off all the kitchen lights (about 4 different loads). And for some simple scene activation on switch/dimmer (movie time, bedtime, etc).
Are you able to share that video a different way? Seems FB wonât let me see the video you shared? Perhaps not made public (I donât blame you!)? I would love to see what youâve crafted.
I will upload the video to Youtube, Itâs probably because i posted it to a private group called âSmartthings Users Groupâ as someone was asking questions about this switch as well.
I have a site for you (looks lat 90âs lol!) but itâs legit. A person in the same FB group above bought about 20 switches from him and got a discount. I canât afford doing all my switches at once but send this guy a message on facebook and he will give you a discount, He offered 8% on 10+ switches. I bet you can wheel him closer to 10% with that many switches!
FB page: https://www.facebook.com/haworldonline/
I too been searching everywhere and the prices are super regulated the only way i found this site is from the other person ordering from him.
Well crap i didnât fully read the 20% off at smarthome.com⊠I now know where iâm buying more switches 
I wonder when they will be getting stockâŠ