Testing Z-Wave binding on openHAB-2

Ok - try using Scene Activation then, and see if that helps… We can change the database to use central_scene instead, but if you can change it, it might work now…

tried already both

both logs are posted above ?

Yes, sorry. When I looked earlier I didn’t spot them both - it looks like you reformatted the logs…

Anyway, I suspect the issue is the same one fixed over the weekend, but it was only fixed on central_scene - not scene_activation. In the version I’ll push tonight, it is also fixed on scene_activation, so I think it might work tomorrow.

I’m a little stuck just at the beginning: I just plugged into my Raspi2 a ZME_UZB1 stick. Now if the zwave.cfg is not used anymore, how do I configure the serial port?

Don’t understand how you add the stick as a zwave controller. Adding a thing with the Zwave2-binding does not list my stick at all.
Any hint for a newbie?

Read the first post above - it should say. Once you’ve added the Serial Controller, go to the configuration, and you should find the port settings.

In HABmin, click the + button at the top of the Thing Configuration window. Select the Z-Wave binding, and then select Z-Wave Serial Controller.

Ah, ok, that helped, thanks! I was missing setting the serial port for the EXTRA_JAVA_OPTS as described in this post

One thing I noticed about this flow when setting things (via HABMin) up that is a bit awkward/confusing: when you first select it, the options for serial port aren’t there…you click save, and it fails, and then you need to go and edit it to change the serial port.

Do you mean delete all items and discover them again? or also disassociate them from the stick and associate them again with the stick?

I just removed al items in habmin (including the serial controller), but no new items are in the inbox, also not after discovery.

2016-03-15 11:16:23.373 [DEBUG] [age.SerialApiGetInitDataMessageClass] - Got MessageSerialApiGetInitData response.
2016-03-15 11:16:23.375 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2016-03-15 11:16:23.376 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 3: Node found
2016-03-15 11:16:23.377 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 4: Node found
2016-03-15 11:16:23.378 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 6: Node found
2016-03-15 11:16:23.380 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 7: Node found
2016-03-15 11:16:23.381 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 8: Node found
2016-03-15 11:16:23.382 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 9: Node found
2016-03-15 11:16:23.383 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 10: Node found
2016-03-15 11:16:23.384 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 11: Node found
2016-03-15 11:16:23.385 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 12: Node found
2016-03-15 11:16:23.386 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 15: Node found
2016-03-15 11:16:23.387 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 16: Node found
2016-03-15 11:16:23.388 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 29: Node found
2016-03-15 11:16:23.389 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2016-03-15 11:16:23.390 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2016-03-15 11:16:23.391 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2016-03-15 11:16:23.392 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 13
2016-03-15 11:16:23.393 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2016-03-15 11:16:23.395 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent message Message: class=SerialApiGetInitData[0x02], type=Request[0x00], priority=High, dest=255, payload=
2016-03-15 11:16:23.397 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv message Message: class=SerialApiGetInitData[0x02], type=Response[0x01], priority=High, dest=255, payload=05 00 1D ED CF 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 
2016-03-15 11:16:23.398 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SerialApiGetInitData, callback id=0, expected=SerialApiGetInitData, cancelled=false        transaction complete!
2016-03-15 11:16:23.399 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-03-15 11:16:23.400 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 146ms/146ms.
2016-03-15 11:16:23.400 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNetworkStateEvent
2016-03-15 11:16:23.401 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-03-15 11:16:23.402 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 03 00 05 F9 
2016-03-15 11:16:23.404 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 05 F9 
2016-03-15 11:16:23.407 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 05 08 F7 
2016-03-15 11:16:23.409 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-03-15 11:16:23.410 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 05 08 F7 
2016-03-15 11:16:23.411 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 05 08 F7 
2016-03-15 11:16:23.412 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=GetControllerCapabilities[0x05], type=Response[0x01], priority=High, dest=255, payload=08 
2016-03-15 11:16:23.413 [DEBUG] [etControllerCapabilitiesMessageClass] - Controller is secondary = false
2016-03-15 11:16:23.414 [DEBUG] [etControllerCapabilitiesMessageClass] - Controller is on other network = false
2016-03-15 11:16:23.415 [DEBUG] [etControllerCapabilitiesMessageClass] - Node ID Server is present = false
2016-03-15 11:16:23.416 [DEBUG] [etControllerCapabilitiesMessageClass] - Controller is real primary = true
2016-03-15 11:16:23.416 [DEBUG] [etControllerCapabilitiesMessageClass] - Controller is SUC = false

Same here after a fresh installation with the latest build #191 with only Z-Wave binding in my addons.cfg.

1:46:22.719 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 10: Not initialized yet, ignoring message.
11:46:32.132 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0D 0A 8F 01 01 06 31 05 01 0A 00 47 1D 
11:46:32.133 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
11:46:32.133 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0D 0A 8F 01 01 06 31 05 01 0A 00 47 1D 
11:46:32.134 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0D 0A 8F 01 01 06 31 05 01 0A 00 47 1D 
11:46:32.134 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, payload=00 0D 0A 8F 01 01 06 31 05 01 0A 00 47 
11:46:32.134 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 13: Not initialized yet, ignoring message.
11:46:32.754 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0A 06 31 05 03 0A 00 35 F3 
11:46:32.755 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
11:46:32.755 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 0A 06 31 05 03 0A 00 35 F3 
11:46:32.756 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 0A 06 31 05 03 0A 00 35 F3 
11:46:32.756 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, payload=00 0A 06 31 05 03 0A 00 35

I didn’t merge this last night due to some problems with the merge - it’s currently in the list for today, but I’m trying to test it here and am also seeing the same issue you are saying.

Can you check something - when you do a discovery, are you immediately seeing a “Ending INCLUSION mode” message?

Yes:
11:52:03.644 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.

I run also in problems with editing items with the latest HABmin version 2.0.0.201603121150, the dropdown fields for assigning groups don’t work.

Same here

Yes, actually its the first message you get after pressing Z-Wave binding discovery

2016-03-15 12:59:01.700 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.

Sorry - I found the (stupid) problem! I left a check in there which I was using for debugging and that prevents discovery from working properly :flushed:.

No worries :grin: if you commit I can test again if you like

Will do shortly - I want to run a final test here before I commit anything more… I normally put any new binding into my production system before I release to try and avoid this sort of screw-up, but because OH2 wasn’t updated with the required additions until this mornings build I didn’t/couldn’t…

I’ll ping you when it’s there (maybe an hour or so…).

I’ll test it also again then :smiley: Could you please check why selecting groups in latest HABmin-Version don’t works?

I wasn’t planning on making a binary available, but I can do…

I’ve fixed this and will push an update soon(ish)…

No problem - i continue on testing Z-Wave after the next nightly building. Meanwhile i continue testing other amazing OH2-stuff like the HomeKit and the HarmonyHub :smiling_imp: You and the other maintainer makes me very happy in combining my SmratHome devices :smile: