I have 6 x WallMote Quads and the only non-default settings that I needed to change for sliding events was “Button 1/2/3/4 Multilevel”. These should be set to “Controller”, as was mentioned earlier.
The “Notification Report” settings does not need to change from its default, “Central scene”.
Because these are battery-based devices, it can take a few attempts to get the configuration to store. I found it useful to toggle the “Touch Sound” setting to be certain the revised configuration was stored.
The channel for swipe events adopts the form zwave:device:abcdef:node123:switch_startstop1.
Have you had any success with resolving this problem. I have just unboxed my Wallmote and I have set up all channels to relevant Items. Unfortunately, the only item receiving updates is the central scene_number all the rest hold a value of NULL.
I have been trying to force an update of the device and use the haptic setting to confirm. I can successfully switch on and off the haptic but no luck with receiving updates from channels.
@Ben
What kind of firmware do your devices have? I have 2.3 and it is not working for me.
I am waking up the device through the action button (3 sec pres multiple time) and I have reinitialized the device so I am confident the has the correct configuration.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Scene-zwave:device:controller:node48:scene_number' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Batterie-zwave:device:controller:node48:battery-level' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Swipe1-zwave:device:controller:node48:switch_startstop1' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Swipe2-zwave:device:controller:node48:switch_startstop2' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Swipe3-zwave:device:controller:node48:switch_startstop3' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Swipe4-zwave:device:controller:node48:switch_startstop4' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Scene1-zwave:device:controller:node48:scene_number1' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Scene2-zwave:device:controller:node48:scene_number2' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Scene3-zwave:device:controller:node48:scene_number3' has been added.
[.ItemChannelLinkAddedEvent] - Link 'WallMote_Scene4-zwave:device:controller:node48:scene_number4' has been added.
Here are some of the properties reported for my WallMotes:
Property
Value
dbReference
535
defaultAssociations
1
manufacturerId
0086
manufacturerRef
0002:0082,0102:0082,0202:0082
modelId
ZW130
vendor
AEON Labs
zwave_deviceid
130
zwave_secure
false
zwave_version
2.3
I suggest trying the log viewing suggestion from @Bruce_Osborne to verify Z-Wave events are actually being sent by the WallMote to your controller when you tap a button.
The commands are not being sent as the binding is expecting. The channels are configured to use the multi-channel encapsulation, which allows the binding to know what switch has been changed. This log shows the commands from the root endpoint and there is no channel associated with that command.
It seems unlikely. Multichannel encapsulation is needed to differentiate the different switches on the device. Probably this is a configuration issue, or something was wrong when the device was initialisation and the incorrect associations were used.
The device will only send multichannel encapsulated commands if configured in a certain way. I’d probably suggest to reset the device and reconfigure it. If you supply a debug log I’ll take a look.
(note that I’m really just responding to this one message - I’ve not read through all 30 or so messages in the thread).
I factory reseted the device 2 times, tried secure inclusion which failed (I remember it’s not supported for these devices), reseted two times again, included 2 times, set the config exactly as before and voila - it works.
That’s really some flaky behaviour!
Glad you got it to work. I still have a minor issue with half of my WallMotes, although didn’t think fixing it was worth the time.
Specifically three units report properties that indicate they’re Z-Wave Plus devices:
Property
Value
zwave_plus_devicetype
NODE_TYPE_ZWAVEPLUS_NODE
zwave_plus_roletype
ROLE_TYPE_SLAVE_PORTABLE
zwave_routing
true
zwave_secure
false
zwave_version
2.3
Whereas the remaining three never report those additional Z-Wave Plus properties:
Property
Value
zwave_routing
true
zwave_secure
false
zwave_version
2.3
The ones with the extra properties allow a “Wake Up Interval” to be configured and correctly report their battery state. The remaining three do not.
I’ve used “Heal the device” and put them in wake up mode beside the Z-Stick quite a few times over the months. But I haven’t investigated it more fully given they otherwise work and it’s only the battery reports missing. If you don’t receive battery reports at least you might have some properties to check.
Hi, I just installed a WallMote Quad and have the same problem. Nothing but the Scene Number is updated. It is only updated when each of the four buttons are pressed. Sliding doesn’t result in any change in OpenHAB.
I’m on openHAB 3.1.1/Release Build. ZWave binding is 3.1.1 as well:
Set the config as described and swipe only in the quadrant (start and stop must start in the same quadrant).
Since you get the scene numbers the device is working.
