Fakro ZWS12 Z-Wave window actuator problem

MikeD · June 20, 2016, 6:05am

Hi Guys,

I am trying to get a Fakro ZWS12 window actuator to work, but have run into problems.

I am running the latest snapshot of openHAB and also HABmin 2 v 0.1.6.

I can see the device on both the Paper UI (including the control page) and also HABmin but I am unable to get it to work.

I suspect my problem has something to do with the Association Group as I am unable to save changes after I set it to openHAB Controller as per the screenshot below. It is only this setting that does not save in HABmin.

I also note that the ZWS12 is in the Z Wave database. Could there be a problem with one of the settings there?

Does anyone have any ideas what I can do next?

Cheers,
Mike

chris · June 20, 2016, 6:20am

The first thing to do would be to look at the logs. Put the logging into debug mode and then load it into the online log viewer at www.cd-jackson.com and see if it shows anything.

For the HABmin error, can you open the browser debug console and see if it shows any more information about the error. IF you go to the Network tab you should be able to see the information that is being sent and also the response. Often the responses aren’t very useful, but I’ll look at updating HABmin to display them.

MikeD · June 20, 2016, 7:36am

Hi Chris,

Following is an extract from the debug log. I tried to upload a TXT file but it would not upload. Does this help??

19:29:43.124 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 21
19:29:43.124 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 11 01 00 25 07 D6
19:29:43.124 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 17: Sending REQUEST Message = 01 08 00 13 11 01 00 25 07 D6
19:29:43.134 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
19:29:43.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:43.136 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
19:29:43.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
19:29:43.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
19:29:43.136 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: Sent Data successfully placed on stack.
19:29:43.195 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 07 00 00 06 EA
19:29:43.197 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:43.197 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 07 00 00 06 00 00 E4
19:29:43.197 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 07 00 00 06 00 00 E4
19:29:43.197 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=07 00 00 06
19:29:43.197 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: SendData Request. CallBack ID = 7, Status = Transmission complete and ACK received(0)
19:29:43.197 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 17: Node is ALIVE. Init stage is PING:{}.
19:29:43.197 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
19:29:43.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveNodeStatusEvent
19:29:43.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Setting ONLINE
19:29:43.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node Status event during initialisation - Node is ALIVE
19:29:43.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - PING: queue length(1), free to send(false)
19:29:43.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Initialisation retry timer started 80000
19:29:43.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - queued packet. Queue length is 1
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 22. Queue={}
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 17: Node Status event - Node is ALIVE
19:29:43.198 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=17, callback=7, payload=11 01 0
0
19:29:43.198 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=07 00
00 06
19:29:43.198 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=7, expected=SendData, cancelled=false        transaction complete!
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
19:29:43.198 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - PING: Transaction complete (SendData:Request) success(true)
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - checking initialisation queue. Queue size 1.
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - message removed from queue. Queue size 0.
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - PING: queue length(0), free to send(true)
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Initialisation retry timer started 80000
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: loop - PING try 5: stageAdvanced(false)
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - advancing to DETAILS
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
19:29:43.198 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveInitializationStateEvent
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: loop - DETAILS try 0: stageAdvanced(true)
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: Restored from file - skipping static initialisation
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - advancing to GET_CONFIGURATION
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
19:29:43.198 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveInitializationStateEvent
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: loop - GET_CONFIGURATION try 0: stageAdvanced(true)
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: GET_CONFIGURATION - CONFIGURATION class not supported
19:29:43.198 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - advancing to DYNAMIC_VALUES
19:29:43.198 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
19:29:43.198 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveInitializationStateEvent
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: loop - DYNAMIC_VALUES try 0: stageAdvanced(true)
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking SWITCH_BINARY
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - found    SWITCH_BINARY
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Found 1 instances of SWITCH_BINARY
19:29:43.199 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 17: Creating new message for application command SWITCH_BINARY_GET
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer - queued packet. Queue length is 1
19:29:43.199 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 23. Queue={}
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking VERSION
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking MANUFACTURER_SPECIFIC
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking SWITCH_MULTILEVEL
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - found    SWITCH_MULTILEVEL
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Found 1 instances of SWITCH_MULTILEVEL
19:29:43.199 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 17: Creating new message for command SWITCH_MULTILEVEL_GET
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking SECURITY
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking NO_OPERATION
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - checking BASIC
19:29:43.199 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 17: Node advancer: DYNAMIC_VALUES - queued 2 frames
19:29:43.199 [DEBUG] [curityCommandClassWithInitialization] - NODE 17: updating lastSentMessageTimestamp
19:29:43.199 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Response processed after 73ms/1950ms.
19:29:43.199 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 22
19:29:43.199 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 11 02 25 02 25 4C B8
19:29:43.199 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 17: Sending REQUEST Message = 01 09 00 13 11 02 25 02 25 4C B8
19:29:43.208 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
19:29:43.210 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:43.210 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
19:29:43.210 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
19:29:43.210 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
19:29:43.210 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: Sent Data successfully placed on stack.
19:29:43.270 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4C 00 00 07 A0
19:29:43.272 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:43.272 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4C 00 00 07 00 00 AE
19:29:43.272 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 4C 00 00 07 00 00 AE
19:29:43.272 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4C 00 00 07
19:29:43.272 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: SendData Request. CallBack ID = 76, Status = Transmission complete and ACK received(0)
19:29:43.272 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=17, callback=76, payload=11 02 2
5 02
19:29:43.272 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4C 00
00 07
19:29:43.272 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=76, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
19:29:48.201 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Timeout while sending message. Requeueing - 2 attempts left!
19:29:48.201 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 17: Got an error while sending data. Resending message.
19:29:48.201 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 23. Queue={}
19:29:48.201 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 22
19:29:48.201 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 11 02 25 02 25 4D B9
19:29:48.201 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 17: Sending REQUEST Message = 01 09 00 13 11 02 25 02 25 4D B9
19:29:48.211 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
19:29:48.213 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:48.213 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
19:29:48.213 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
19:29:48.213 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
19:29:48.213 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: Sent Data successfully placed on stack.
19:29:48.272 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4D 00 00 07 A1
19:29:48.274 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:48.274 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4D 00 00 07 00 00 AF
19:29:48.274 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 4D 00 00 07 00 00 AF
19:29:48.274 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4D 00 00 07
19:29:48.274 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: SendData Request. CallBack ID = 77, Status = Transmission complete and ACK received(0)
19:29:48.274 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=17, callback=77, payload=11 02 2
5 02
19:29:48.274 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4D 00
00 07
19:29:48.275 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=77, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
19:29:53.204 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 17: Timeout while sending message. Requeueing - 1 attempts left!
19:29:53.204 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 17: Got an error while sending data. Resending message.
19:29:53.204 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 23. Queue={}
19:29:53.204 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 22
19:29:53.204 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 11 02 25 02 25 4E BA
19:29:53.204 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 17: Sending REQUEST Message = 01 09 00 13 11 02 25 02 25 4E BA
19:29:53.214 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
19:29:53.215 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:53.215 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
19:29:53.215 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
19:29:53.215 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
19:29:53.216 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: Sent Data successfully placed on stack.
19:29:53.277 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 4E 00 00 06 A3
19:29:53.279 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
19:29:53.279 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 4E 00 00 06 00 00 AD
19:29:53.279 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 4E 00 00 06 00 00 AD
19:29:53.279 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4E 00 00 06
19:29:53.279 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 17: SendData Request. CallBack ID = 78, Status = Transmission complete and ACK received(0)
19:29:53.279 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=17, callback=78, payload=11 02 2
5 02
19:29:53.279 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=4E 00
00 06
19:29:53.279 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=78, expected=ApplicationCommandHandler, cancelled=false      MISMATCH

Mike

MikeD · June 20, 2016, 7:41am

Not sure if this helps, but this is a new error message on my system that has only appeared tonight while I am working with the ZWS12:

MikeD · June 20, 2016, 7:52am

Following is the error I see in the Browser Console after pressing the save button in HABmin.

PUT XHR http://192.168.1.240:8080/rest/things/zwave:device:1541dc5a0e6:node17/config [HTTP/1.1 500 Internal Server Error 4ms]

chris · June 20, 2016, 9:44am

I don’t think this is anything to do with ZWave. It mentions graphics adapters.

I’ll take a look at the log tonight.

MikeD · June 20, 2016, 9:54am

Thanks Chris.

For what it is worth, one thing I noticed today was that when I first added the ZWS12 I was running HABmin 0.1.5. When I went to set the Association Groups, no options came up in the option box. i then updated to 0.1.6 and got options and the current save problem.

Now I am not sure that I have ever set up a z wave device on 0.1.5, I think I did all of my original setup on 0.1.4

Cheers,
Mike

chris · June 20, 2016, 9:57am

I changed the widget recently to allow me to add tagging, and the updated widget might have broken association setting - someone has reported this but I’ve not had the chance to confirm or check it.

MikeD · June 20, 2016, 10:01am

Let me know if you want me to do any other specific tests, I have about 6 different z wave devices on the system for testing purposes while I develop the HA system for our new house.

MikeD · June 20, 2016, 10:09am

I think you are correct here, as I was using a remote desktop session from my development box to the server so that could cut & paste data easily.

FYI, my server is running Win 7 64 bit and the Aeon Z Stick is running on a RPI2 running the Virtualhere USB sharing application.

MikeD · June 21, 2016, 6:04am

@Chris I tired removing an association group from another z wave device then saving and following that adding one and saving again and it worked OK. So it really looks like the issue is specific to the ZWS12 device.

chris · June 21, 2016, 6:24am

I will print the error returned from ESH to the red error box and we can see if that helps. Unfortunately these errors tend to be mostly useless so I don’t have high hopes…

I’ll try and do that tonight, although I have a late flight to catch so won’t have much time this evening…

MikeD · June 21, 2016, 8:46am

After some more testing outside of openHAB I now have the Z Stick controlling the actuator using the Z-Wave PC Controller. The command classes look very different to what is in the database for the ZWS12.

What can I do to resolve this? I am not sure I have enough experience to edit the database myself yet…

Note: this is after excluding and then re-including the device using the PC Controller. Note: I am still unable to save the Association Group in HABmin2 after the above.

Cheers,
MIke

chris · June 21, 2016, 8:57am

Can you be specific? If I look at what you show in the image above, it looks the same as the database from what I can see.

NO_OPERATION
BASIC
SWITCH_BINARY
SWITCH_MULTILEVEL
SWITCH_ALL
CONFIGURATION
MANUFACTURER_SPECIFIC
POWERLEVEL
PROTECTION
ASSOCIATION
VERSION

Or am I missing something?

MikeD · June 21, 2016, 9:06am

Sorry if I am confusing things. I have been trying many different options to try an solve this issue.

It could be on my side as earlier there seemed to be only 2 classes available and I unfortunately did not note them. The SWITCH_ALL class was not available last night when I tried the same exercise using the PC Controller.

I think I was looking at the XML file not the Database.

I have some more tests to do and will report back again later. At least I seem to be moving forwards as I now know the actuator works when I send a command to it. Now to just get OH2 to send the commands and I am not sure how to fix the save “Association Group” Issue. Can I directly edit the XML file to fix this?

chris · June 21, 2016, 9:09am

IF the XML file is different, then this would be strange and we should look at that as it means the device is not being discovered correctly.

No - editing the XML won’t make any difference to the device configuration.

MikeD · June 21, 2016, 9:37am

It looks like the xml file is missing a number of the classes.

I have put a copy at the following link if you have time to have a look before your flight

chris · June 21, 2016, 10:08am

What version of the ZWave binding are you using exactly?

I don’t think the missing classes will matter, but it’s interesting as to why they are missing. It might be that the device isn’t reporting them in the NIF - if you can get a startup debug log it would be useful (delete the XML first before restarting).

MikeD · June 21, 2016, 10:33am

I downloaded the latest openHAB 2 offline snapshot about 24 hours ago.

I have stopped working on the system for tonight as it is getting late. I will do as you suggest and get a startup debug log tomorrow evening.

Thanks,
Mike

MikeD · June 21, 2016, 10:36am

@Chris - is there a easy way I can identify the binding version in the offline snapshot? i.e. Where do I look as it is not in the addons folder anymore.