Events from WallMote Quad is not registered

koverskeid · May 4, 2019, 8:57pm

Dear Community,

I’ve been running into some problems with my WallMoteQUad (aeotec_ZW130). It was no fuzz to add it to “Things” and add the scenes to “Items”. However, when I push a button the only log entry I get is
“[vent.ItemStateChangedEvent] - ZWaveSerialController_StartFrames changed from 2438 to 2439” no matter which of the four buttons I press. This makes it a bit hard to create rules…

I’m also having trouble editing the configuration on the wallMote Quad. For example, I try to disable the touch sound, but it seems like the new settings aren’t uploaded to the wallMote Quad. I tried to push the action-button to send a wake up notification, but it just blinks orange for around 10 minutes. When I push the buttons, it still beeps and still, it seems like I’m not receiving any usefull information in openHAB.Here’s the log event that’s created when I save the changes:

[vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_1_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_2_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_4_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

I tried to remove the WallMote Quad several times. I also tried to remove and add the Z-Wave Serial Controller.

The WallMote Quad properties:

dbReference	535
defaultAssociations	1
manufacturerId	0086
manufacturerRef	0002:0082,0102:0082,0202:0082
modelId	ZW130
vendor	AEON Labs
zwave_beaming	true
zwave_class_basic	BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic	GENERIC_TYPE_WALL_CONTROLLER
zwave_class_specific	SPECIFIC_TYPE_BASIC_WALL_CONTROLLER
zwave_deviceid	130
zwave_devicetype	2
zwave_frequent	false
zwave_listening	false
zwave_manufacturer	134
zwave_neighbours
zwave_nodeid	8
zwave_routing	true
zwave_secure	true
zwave_version	1.8

Did I forget to do something important?

Best regards
Kristian the Rookie

P)latform information:
- Hardware: Raspberry Pi 3b+ with a razberry card and 32 GB memory card
- OS: OpenHABian v.1.4.1
- Java Runtime Environment: _OpenJDK Runtime Environment (Zulu8.36.0.152-CA-linux_aarch32hf) (build 1.8.0_202-b152)
  OpenJDK Client VM (Zulu8.36.0.152-CA-linux_aarch32hf) (build 25.202-b152, mixed mode, Evaluation)
- openHAB version: openhab2 2.4.0-1

mhilbush · May 5, 2019, 12:17am

@koverskeid You might want to tag this post with the zwave tag, as several people on the forum subscribe to that tag, hence there’s a greater chance one of them will see your post.

Also, there are several people on the forum using the Wallmote Quad (myself included), so we know it works.

This is a report from the controller, which indicates there’s activity on the zwave network. This is ok, but doesn’t necessarily indicate anything good or bad with respect to the Wallmote.

A couple things to help level-set…

Is the Wallmote the only device in your zwave network? If there are other devices, are they working properly?
What are you using to manage your zwave devices? Paper UI? If so, I’d suggest you install the HABmin UI. It’s better for managing zwave devices. You can install HABmin using Paper UI.
I’d suggest you upgrade to the latest version of the zwave binding. You can do that by following the directions in this post. If you’re unfamiliar with the Karaf console, you can read about it here.
Debugging zwave issue can be tricky. There’s some good information about debugging here. At some point, we might ask for a debug log. But that’s a bit premature right now.

koverskeid · May 5, 2019, 2:26pm

Hi Mark,

Thanks for the quick reply and good tips

I have several other devices in my network:
- Two HEATIT Z-TRM2fx that reports the temp and I can send commands to them
- One FT112 door/window sensor that sends me updates if the door is open or closed
- One DanalockV3 that worked fine yesterday, but after I reinstalled openhabian and updated the zwave binding, I can’t connect it
- One ZXT-120 AC IR Remote that worked fine yesterday, but now I can only include it, not send
  commands.
- Two Fibaro smoke sensors (FGSD-002-EN-A-v1.1) I can include, but no alarms are received (my
  ears are hurting after testing)
I tried to use HABmin, but weren’t that happy about it. See the next section
After I updated the zwave binding from 2.4 to 2.5, I noticed some improvements. While I could change the settings on the wallmont quad (sound and vibration) from Paper UI (I was so happy), this didn’t work from HABmin. The wallmont quad seemed to receive the updates because it stopped blinking organge after I woke it up, but the sound and vibration settings didn’t change when I did it from HABmin. Another improvement was that I received scene changes when I pushed the different buttons, but if I pushed the same button twice, nothing was logged.
I have enabled debugging in case we have reached the point were you will ask me for a debug log

I know a guy that has his smarthome set up, I will go to him to test if he can set up the wallmont quad properly at his place to check that it’s actually working.

I still haven’t figured out how to properly exclude things from OH and have a feeling maybe that’s why I can’t make the danalock and IR remote work properly. Is there any good procedure how to properly reset a thing to add it again as if it was brand new?

koverskeid · May 6, 2019, 6:26pm

Hi aigan,

So I checked the debug log. When the wallmount quad was included securely, every time I pressed a button, I could see in the log that it was complaining about no valid nonce.

So I removed it and included it insecurely. Now I get a lot of lines in the debug log every time I press a button, but nothing when I turn off debug. The debug log is inlcuded under.

2019-05-06 20:19:51.740 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 04 15 05 5B 03 68 00 01 BF 00 6C

2019-05-06 20:19:51.775 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00

2019-05-06 20:19:51.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00

2019-05-06 20:19:51.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-05-06 20:19:51.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Application Command Request (ALIVE:STATIC_VALUES)

2019-05-06 20:19:51.789 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0

2019-05-06 20:19:51.791 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: SECURITY not supported

2019-05-06 20:19:51.795 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 21: Received COMMAND_CLASS_CENTRAL_SCENE V2 CENTRAL_SCENE_NOTIFICATION

2019-05-06 20:19:51.798 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 21: Received scene 1 at key 0 [Single Press]

2019-05-06 20:19:51.802 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2019-05-06 20:19:51.804 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CENTRAL_SCENE, value=1.0

2019-05-06 20:19:51.809 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating channel state zwave:device:a7a53341:node21:scene_number to 1.0 [DecimalType]

2019-05-06 20:19:51.812 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Commands processed 1.

2019-05-06 20:19:51.817 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@19cf5cd.

2019-05-06 20:19:51.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-05-06 20:19:51.825 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-05-06 20:19:51.827 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-05-06 20:19:51.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

mhilbush · May 6, 2019, 11:17pm

That’s normal. With DEBUG turned off, there won’t be much in the log.

Always best to use code fences when posting debug logs. Much easier to read.

2019-05-06 20:19:51.740 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 04 15 05 5B 03 68 00 01 BF 00 6C
2019-05-06 20:19:51.775 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00
2019-05-06 20:19:51.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=21, callback=4, payload=04 15 05 5B 03 68 00 01 BF 00
2019-05-06 20:19:51.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-05-06 20:19:51.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Application Command Request (ALIVE:STATIC_VALUES)
2019-05-06 20:19:51.789 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0
2019-05-06 20:19:51.791 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 21: SECURITY not supported
2019-05-06 20:19:51.795 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 21: Received COMMAND_CLASS_CENTRAL_SCENE V2 CENTRAL_SCENE_NOTIFICATION
2019-05-06 20:19:51.798 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 21: Received scene 1 at key 0 [Single Press]
2019-05-06 20:19:51.802 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-05-06 20:19:51.804 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CENTRAL_SCENE, value=1.0
2019-05-06 20:19:51.809 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Updating channel state zwave:device:a7a53341:node21:scene_number to 1.0 [DecimalType]
2019-05-06 20:19:51.812 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Commands processed 1.
2019-05-06 20:19:51.817 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 21: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@19cf5cd.
2019-05-06 20:19:51.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-05-06 20:19:51.825 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-05-06 20:19:51.827 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-05-06 20:19:51.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

This looks fine. If you have an item linked to the scene_number channel, you should be able to deal with it in a rule like this.

rule "wallmote rule"
when
    Item Wallmote_Scene received update
then
    var double sceneNumber = (Wallmote1_Scene.state as Number).doubleValue

    switch (sceneNumber) {
        case 1.0 : {            // Button 1 short press
            // Do something
        }
        case 1.1 : {           // Button 1 long press
            // Do something
        }
        case 1.2 : {            // Button 1 hold
            // Do something
        }
        // Repeat for buttons 2, 3, & 4
    }
end

koverskeid · May 10, 2019, 10:31pm

Hi Mark,

Once again, thank you very much for your tips and tricks

I got the wallmote quad to work when I added the wallmote withouth encryption. Even made som nice rules that controlled my danalock.

However, when I’m adding it with encryption, it’s not recognized by my controller. I tried to add it in both HABmin and paperUI, but it doesn’t matter. I’m considering giving in and use it withouth encryption, but I want to try everything first because I intend to control a lock with it.

I guess a central clue is the error message “SECURITY_ERR No valid NONCE! null”

mhilbush · May 11, 2019, 12:16am

@koverskeid If you can provide a debug log starting from the point when you perform the secure inclusion, I’m sure @chris would be willing to take a look at what’s happening.

chris · May 11, 2019, 6:52am

Sure - just mention me when posting it and I’ll take a look.

chris · May 11, 2019, 11:20am

The best approach is to provide it as a linked file.

koverskeid · May 11, 2019, 11:28am

Thanks for the tip @chris, here are the log files from the discovery and inclusion process. When I added the wallmote quad (node 2), I woke it up at the same time.

openhab discovery.txt (91.4 KB)
openhab including.txt (4.7 KB)

chris · May 11, 2019, 12:23pm

It seems that the secure inclusion worked?

I appreciate it’s a little hard to see this image, but the secure key exchange seems to complete successfully. There are no errors that I can see in the inclusion log.

There is something strange in that it seems to try the key exchange again, but the device then sleeps so it doesn’t succeed anyway.

koverskeid · May 11, 2019, 4:29pm

I’m very sorry @chris, but I didn’t notice that it was not included securely. Here is the log from me searching and including the wallmote quad securely as node 4. However, it doesn’t recognize it…

search and include securely.txt (28.9 KB)