If I press the Delete Node button, I can see in the zwave.log that the operation fails because the node is not found. Iām not entirely sure how this works, but I can imagine that the ZWave-stick has remembered the old device-pairing and has added it as a new node after the repeated inclusion-proces. But then the Delete Node operation should take care of that problem? Or is the error raised by OpenHAB which tries to delete a non-existing node, fails and then leaves the node in the cache, somewhere?
No luck, so far. Iāve added some rules like those shown above, but I could only trigger them via the OpenHAB UI and not by pressing the wallswitch. First Iāll ask my supplier for help in this matter and post any (hopefully positive) results to this forum. I will also try HABmin 1 and other tools to see if Iām able to get more feedback on the switch configuration. Iām unsure if HABmin 2 shows the correct configuration from the switch, the webinterface is behaving a little weird sometimes.
Oh, I have never used direct associtions with my nodes, so I guess Iām not the correct person to comment in this case.
I know I have seen āUnsupported command class (0x5b)ā messages before when fiddeling around, but I donāt see it now with my current configuration (as posted earlier)
I just tried to delete a dead node using HABmin 1 and when I clicked on āDelete Nodeā this was logged:
NODE 19: Remove failed node failed with error 0xfe.
When I tried to to click on āDelete Nodeā again, this was logged:
NODE 19: Remove failed node failed as node not found!
Still, the node showed up in HABmin, even after I reloaded the page and restarted the browser. I then restarted the whole openHAB and now finally the dead node is also gone from HABmin.
I can understand why OpenHAB lists 0x5b as a commandclass that is not implemented. According to the pepper1 zwavedb it is tied to the Central Scene command (which is not supported by the ZWave binding). It is the factory default setting for the WALLC-S to send this command whenever a button is clicked.
http://www.pepper1.net/zwavedb/device/554
The odd thing is that Iāve changed the WALLC-S configuration through the HABMin2 userinterface and assigned Scene Activation and Basic to the four button groups. Iāve also made sure that the WALLC-S was
able to get the new settings by activating the Wakeup Note. I can see a lot of logging comming from the WALLC-S, but nothing indicates that the configuration is updated succesfully. So, I wasnāt sure that
the update succeeded or not, seeing the Invalid Command class messages in the log makes me believe that it didnāt.
I will try a different tool to setup the configuration of the WALLC-S (eg. Open ZWAVE control panel) and see if Iām able to change the button associations. What tool do you use to configure your ZWave network? I see that you mention HABMin 1 above. Is there anything better?
Perfect. I just installed HABMin 1 and through the ZWave configuration panel I was able to correctly configure the WALLC-S switch. Button 1 to send a Activate Scene command, which I can see is received by OpenHAB. Button 2 to send a Switch On/Off command directly to the TKBHOME wallswitch. Both work beautifully, now.
Next thing is to discover how I to create rules, etc. in OpenHABā¦ 
Great! Good job 
Saw this a bit late but maybe this helps I use this switch to control my hue lights thru openhab:
zwave.items
Number LinksAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=11,state=0" }
Number LinksUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=12,state=1" }
Number LinksDBAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=31,state=0" }
Number LinksDBUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=32,state=1" }
Number RechtsAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=21,state=1" }
Number RechtsUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=22,state=1" }
Number RechtsDBAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=41,state=1" }
Number RechtsDBUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=42,state=1" }
Number LinksLAAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=13,state=1" }
Number LinksLAUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=14,state=1" }
Number RechtsLAAan "" { zwave="9:0:command=SCENE_ACTIVATION,scene=25,state=1" }
Number RechtsLAUit "" { zwave="9:0:command=SCENE_ACTIVATION,scene=26,state=1" }
And my zwave.rules:
import org.openhab.core.library.types.*
import org.openhab.model.script.actions.*
rule "Eten Knop Aan"
when
Item LinksAan received update 1
then
sendCommand(TafelScene, 1)
end
rule "Eten Knop Lang Aan"
when
Item LinksLAAan received update 1
then
sendCommand(TafelScene, 2)
end
rule "Eten Knop Lang Uit"
when
Item LinksLAUit received update 1
then
sendCommand(TafelScene, 0)
sendCommand(KamerScene, 0)
end
rule "Eten Knop Uit"
when
Item LinksUit received update 1
then
sendCommand(TafelScene, 0)
end
rule "Herfst Knop Aan"
when
Item LinksDBAan received update 1
then
sendCommand(KamerScene, 1)
end
rule "Herfst Knop Uit"
when
Item LinksDBUit received update 1
then
sendCommand(KamerScene, 0)
end
rule "Overloop Knop Aan"
when
Item RechtsAan received update 1
then
sendCommand(OverloopS, ON)
end
rule "Overloop Knop Uit"
when
Item RechtsUit received update 1
then
sendCommand(OverloopS, OFF)
end
And I know, this is not āthe zwave wayā to do it, but I do have a nice and configurable switch using OpenHabā¦
Good to see your examples. I derived a similar setup. Also maybe not the āzwave wayā to do it, but now I have the 4 buttons configured to do the following:
- 2x switch on/off lights connected via a TBK Wallplug
- 1x switch on/off lights connected via a TBK Wallplug dimmer
- same switch long-press dims the lights up and down (direction reversed every time) until button released
- 1x scene switch, steps through a list of preset lighting configurations (stepper is reset after 5 seconds)
- same switch turns off all the lights when double clicked
- with long-press starts slow cinema fade out to dark
ā¦all that with a single wallswitch!
Now Iām thinking about adding awareness using my Fibaro multisensor watching the scene. Lights should go into energy conservation mode when no motion is detected for 30 minutes and go back to the old setting whenever someone enters. Also, lights should go on when twilight is kicking in and off when ambient lighting has gone up.
I see that you control hue led lighting. If you have zwave actuators, they could be configured in association mode. The problem that I now have is that lights cannot be controlled whenever Iām working on the OpenHAB installation.
Biggest problem I have is the family acceptance factor. "Click left to switch on, Click left switch off is easy enough. But āDouble click the upper left to switch the room to a yellow sceneā is almost too much and double long click (which the WALLC-S does support) I have not even started usingā¦ 
oh and I added this:
zwave.items
Number TafelBatt "" { zwave="9:0:command=BATTERY" }
default.sitemap
Text item=TafelBatt label="Batterij [%d]"
Iāve now expanded my setup to include about 30 devices consisting of buttons, motion sensors, dimmers and relays. To increase the FAF (family acceptance factor) Iāve configured buttons to control dimmers and relays by association, so that when my OpenHAB server is not available for any reason weāre still able to turn on and off (most of) the lights. However, this also leads to some issues, for which Iāve yet to find a solution.
What I see is that whenever a button controls a dimmer directly, the status of the dimmer in OpenHAB is not updated automatically. This might be because of a possible patent infringement, the ZWave standard is not allowed to retransmit status updates of a device controlled by association. The workaround is to have the controlling device (eg. a WALLC-S button) being associated with the controller node. This leads to the dimmer being controlled directly and an event being generated in OpenHAB. However I wil need a rule to fetch the current status of the dimmer and update OpenHAB to refelect the new status. Is there any way to do that? I tried lamp.state but that only returns the state as OpenHAB sees it and is often incorrect.
There is also another issue directly related to the WALLC-S button, which contains 4 buttons actually. Iāve setup a Contact item in OpenHAB that will receive the button events. But since a buttonpress needs to send a BASIC DIM/ON/OFF command to directly to the dimmer, the same event is received in OpenHAB. The dimmers differentiate by the way they are associated, but OpenHAB will receive the same event regardless of which button is pressed. Is there a way to differentiate between different buttons? Using SCENE commands it is possible to filter events based on the scene parameter in the ZWave-binding. But since the button directly controls the dimmer and I cannot make the dimmer respond to SCENE commands, Iām a bit stuck here. The only workaround is to refresh the status of all associated devices, but that seems a bit overkill to me.
To answer my own question Iāve noticed the refresh_interval parameter which you can add to your zwave binding. I think that would partially solve the state problem I have now. But Iāll test this tonight and post any results Iāll find. More info and inspiration can be found in this post: Working with zwave nodes that donāt have association groups
The refresh_parameter seems to do its work. The OpenHAB state of the device is updated fine, although with a little (configurable) lag. What worries me though is the increasing number of messages on the ZWave network. Iām starting to see some lag now and then, especially with ZWave commands sent from rules. From the ZWave (debug) log I see events appearing almost every few seconds. What would be the maximum number of messages per second in a typical ZWave network before things are really slowing down? Right now I have about 35 devices, 6 of which are battery operated and do not send any unsolicited messages. My guess is that the number of devices will be doubled when Iāve reached my desired setup. Will it still perform?
Iām not sure what the max amount of messages are or if that is even a hard number. I suspect that it depends not only on how many devices you have but how active they are. That is a stone cold shot in the dark so take it lightly. After playing around with the refresh settings I can tell you that there appears to also be limitations in the devices(Nodes) and not just a binding/controller thing. At the most frequent polling intervals I set while playing around one of my thermostats was the first device to stop responding and I was only polling it once per minute(but I was polling other devices more frequently). Makes sense since every device receives and repeats the message and this thermostat happens to be 10 feet from the A/V closet so itās definitely getting and repeating every message.
As far as polling, my default intervals for switches and outlets is 1 minute because they can change at anytime. Devices like thermostats are 1 minute for operating state (heating, off) and 15 minutes for everything else. If the temperature in the house changes more frequently than 15 min iād spend less effort on zwave and more on insulation . I donāt have zwave motion and contact sensors as I use my alarm panel for that but I would imagine that they actively communicate status changes and therefore wouldnāt require polling so I would set those to 5 - 10 minutes if I were using them. I am by no means a zwave expert but this is what works for me and what I think makes sense.
Hello, can someone help me with the configuration change of the Zwave-me Wall controler. I bought one this week and I managed to include it. I see it in the Habmin (see picture) but Iām not able to change the Configuration Parameters.
I reed the post but no success so far.
Iām pretty stuck on this. Very new to zwave and openhab, so itās quite tricky to get the concepts right, but anyway. Iām facing the NODE 2: Unsupported command class SECURITY (0x98) issue with my WALLC-S. Using RaZberry Gen5, RPi2, openhab 1.8, habmin 1 and Z-way for including units.
In habmin it seems I cannot do much. I can see the status of my devices but I cannot seem to change anything. Exclusion doesnāt work (log says Invalid message class RemoveNodeFromNetwork (0x4B) for sendData). Inclusion does not work (Invalid message class AddNodeToNetwork (0x4A) for sendData).
How do you get those Configuration Parameters for the WALLC-S? I donāt have any such.
I think I need someone to hold my hand here. I have no idea how to proceed.
Iāve found them very fiddly devices and completely inconsistent across units. Some work straightaway. Others required exclusion/inclusion. Others (like yours) would never exclude and I returned them.
I still believe itās me doing it wrong. I managed to exclude/reinclude the unit a few times, and I might have found a way to do it right. In Z-Way, there is an option to include a unit securely or insecurely. What it actually means, I donāt know, but by default the secure option is selected. I tried including it with the insecure option, and it actually stopped sending the secure message afterwards. I have two of these units and I will try doing the same with the second one to confirm or decline the correlation.
I have yet to figure out how to use the unit, but I feel like Iām passed the showstopper. Now it sends another message openhab cannot understand, 0x5b, but I donāt think that is as fatal. At least it doesnāt leave the buttons stuck for half a minute.
Actually I like the Z-Way interface much better than habmin. Currently my habmin is broken anyway, so I donāt have much of a choice here. I read somewhere that you can use openhab without the zwave binding but instead with a wrapper to Z-Way. Iāll probably try that out pretty soon unless everything magically resolve.
Iām interesting in your item and rule definition, can you post them?
I have no idea about dimming with this device via a rule, because the wall switch sends no continuos command if pressed.
I just updated to Openhab 2.2.0 and had to re-include my WALLC-S switch.
When I now want to re-include the switch, it is not recognized as a WALLC-S switch, but as a āZME_KFOB-S Secure 4 Button Key Chain Controllerā.
I checked the specs of the 4 Button Key Chain Controller and as it looks from the specs similar to the WALLC-S, I included it.However, the buttons pressed at the WALLC-S are not transmitted correctly and thus, do not show up in the log. I checked the configuration and figured out that in the Association Groups, I was not able to select Node 1 (the zwave controller) but could, besides all other zwave devices, just select openHAB controller. Is this correct?
Why is the WALLC-S not recognized as a WALLC-S anymore? How can I get the switchup and running again?
Thanks for your help
I am using a Raspberry PI3