Zwave. Node initialising: STATIC_VALUES. node.xml file

Hi,

I’ve some issues with my zwave Shutter Goap ZNMHCD (OH2, snapshot 2017-05-25).

  1. Habmin shows: Node initialising: STATIC_VALUES, Firmware version 0.0
  2. node.xml file dosen’t appear
  3. opemhab.log error every few minutes: 2017-05-31 17:54:46.909 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 19 08 59 06 01 06 20 01 26 01 >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 19 08 59 06 01 06 20 01 26 01 (11)
  4. Rollershutter works - sometimes experience lags but generally it works :slight_smile:

Thanks for any help.

I am using the same flush shutter from Qubino. Does Habmin ever returns to get_configuration and some other stuff and then return to normal? Because that should be the way it is. I am using 12 of those ZMNHCDs. And also node.xml should appear sooner or later. Could it be something wrong with the controller or its binding. I know that inclusion with those devices are a pain. Those are the things to try:
Remove the thing from habmin and make it discovered again. Habmin should find as “ZMNCHD Node xx”. If “Unknown device” wait some minutes and check again.
If that doesn’t solve, exclude the module from the controller first and then reinclude.

I was trying:

  • remove things and discovered it again.
  • Exclude and include again.
    It dosen’t help - no node.xml files. I have two Qubino Flush 2 relays and no problem with them.

With OH1 ZNMHCD works flaweless (node.xml appears, no lags).

Please provide a short debug log showing the error you mentioned above and also what node number this is…

Hi,

Nodes: 10,11,14,25,27,28,29,30,32,35,5,8,9

10 Mb (500Kb zip) file: https://www.dropbox.com/s/hk302bw3fkg2nsr/zwave.log.zip?dl=0
2 Mb (150Kb zip) shorter debug: https://www.dropbox.com/s/i7el9oyeo5qcib8/zwave_short.log.zip?dl=0
7Mb (350Kb zip) 10 minutes later https://www.dropbox.com/s/i7el9oyeo5qcib8/zwave_short.log.zip?dl=0

Thanks!

Ok, I’m a bit confused. What node gives this error? You’ve listed 15 nodes or so - are they all doing the same thing? Which log has the error (none of them look especially short :wink: ). It would be good if you can pull out the error?

All of them (13 nodes Roller shutter Qubino ZNMHCD) gives the same error + no node.xml file + No firmware version in Habmin + stuck at Node initialising: STATIC_VALUES in Habmin.

Smaller (10Kb zip) file with Error (near node 8): https://www.dropbox.com/s/6rtbbkugdk60xf2/zwave_file_with_error.zip?dl=0

Error loks that:
2017-06-01 19:08:51.333 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 08 59 06 01 06 20 01 26 01 >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 08 59 06 01 06 20 01 26 01 (11)

All of them (13 nodes Roller shutter Qubino ZNMHCD) gives the same error + no node.xml file + No firmware version in Habmin + stuck at Node initialising: STATIC_VALUES in Habmin.

Smaller (10Kb zip) file with Error (near node 8): https://www.dropbox.com/s/6rtbbkugdk60xf2/zwave_file_with_error.zip?dl=0

Additionally I’ve checked firmware version and protocol of my Qubino ZMNHCD (in OH1 node.xml).

<protocolVersion>3.95</protocolVersion>
<applicationVersion>4.0</applicationVersion>

mayby my version is older (18.09.2015) and I should add new record into database.

I was added into database second version of Qubino ZMNHCD: firmware version S1 (the oldest one).
Firmware <= 4.0. I can’t remove Parameter 0 from web interface - Please remove it.

Zwave database changes don’t help. No node.xml file and Habmin shows firmware version 0.0. But after first initialization and discovered ‘thing’ appeared firmware 4.0. After OH2 restart Habmin shows firmware 0.0.

What changes did you actually make to the database?

I found some errors in the new device you added so I’ve just fixed this, but what’s the difference between the two versions?

With according to this manual :http://www.cd-jackson.com/zwave_device_uploads/213/ZMNHCD-S1.pdf (This one is similar to my printed manual) and node.xml from OH1
I changed:
SPECIFIC_TYPE_CLASS_C_MOTOR_CONTROL to SPECIFIC_TYPE_CLASS_B_MOTOR_CONTROL
Protocol Version 4.005 to 3.95
Delete endpoints 2 and 1 (probably endpoints 1 should stay)
COMMAND CLASS version (to lower)
Remove Parameter 86 - but I see now that it is in this pdf but not in my printed manual.
Unique Reference (added S1)
Device overview (added S1)
That’s all.
Below screenshot from HABmin

Ok, thanks.

Do you have the manual for this version that you can upload to the reference section on the database page?

Have you also checked that all the parameters are correct? I found one error that would cause a problem with initilising the device.

Thanks. I scanned and uploaded my version of manual: http://www.cd-jackson.com/zwave_device_uploads/614/ZMNHCD-VER-S1-19-08-2015.pdf
I’m also checked parameters and change only alloowable value and descriptions.
Parameter 80 dosen’t exists in my manual but in OH 1 it was working fine (I tested it on one shutter).
I changed endpoint 0: Specific Class SPECIFIC_TYPE_CLASS_B__MOTOR_CONTROL. I’m not sure what is difference between CLASS B and C. I’m a little confused with Basic and NIF Should be ticked or not?

Thanks.

Most of this stuff isn’t really used, so it doesn’t matter too much. NIF just means the class is reported by the device in the Node Information Frame, and Basic tells us what to do if the device sends a basic command class.

Basic might be useful, but we can worry about that later - first thing is to get it working :wink:

I’ve got to go out soon so probably won’t get to update this until tomorrow (sorry).

If it doesn’t work still, then we’ll need to get a detailed debug log showing the initialisation to work out why it’s getting stuck… My expectation is that we probably haven’t fixed it here, but let’s see…

OK. I’ll wait for update. Now I attached current short log with errors for NODE 5. Next one after update :slight_smile:
https://www.dropbox.com/s/owajc8od5yfls73/short_log_NODE_5_20170610.log?dl=1

It looks that Parameter 80 is not valid:

2017-06-10 23:07:03.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_40_1 - id = '40'
2017-06-10 23:07:03.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_40_1 - size = '1'
2017-06-10 23:07:03.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Sub-parameter config_40_1 is 00000000
2017-06-10 23:07:03.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Pre-processing  00000000>>FFFFFFFF
2017-06-10 23:07:03.657 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Post-processing 00000000>>FFFFFFFF
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Sub-parameter setting config_40_1 is 00000000 [0]
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_80_1
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_80_1 len=3
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_80_1 - id = '80'
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing action_failed
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@32713af6
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing powerlevel_level
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing action_remove
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing binding_pollperiod
2017-06-10 23:07:03.658 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_0_0
2017-06-10 23:07:03.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_0_0 len=3
2017-06-10 23:07:03.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing config_0_0 - id = '0'
2017-06-10 23:07:03.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Processing

Thanks - this is useful and should help. Let me take a look but I can reproduce the issue with this log.

Unfortunately the problem seems to be with the data the device is sending :frowning: .

01 0E 00 04 00 05 08 59 06 01 *06* 20 01 26 01 A6

In the above packet, the 06 is the length of the data to follow. Forgetting the A6 (which is the Checksum) the data is only 4 bytes long, but the packet says it’s 6 bytes and this causes the problem as the binding is trying to read 6 bytes.

Unfortunately this is going to take a little time to would out how best to accommodate this problem.

Thanks!
It’s really strange. It looks like device bug.
But I’ve analyzed file and every time when device is sending 06 20 it’s sending also 06 01 (two bytes eralier). Maybe in this device information about bytes to sent is sending two bytes eralier. After node id is 08 and it also looks like pattern with information about bytes to sent.
01 0E 00 04 00 05 ***08*** 59 ***06*** 01 ***06*** 20 01 26 01 A6
I can provide bigger log.

Every node sends similar payload.

2017-06-05 21:26:30.188 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:26:35.191 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:26:40.192 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:26:45.184 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:26:50.186 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:26:55.191 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:00.193 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:05.194 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:10.196 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:15.197 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:20.199 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 23 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:25.200 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:30.202 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:35.204 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:40.205 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:47.112 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:52.115 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)
2017-06-05 21:27:57.115 [ERROR] [ssage.ApplicationCommandMessageClass] - Error processing frame: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  >> Attempt to read message payload out of bounds: Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 08 59 06 01 06 20 01 26 01  (11)

The 06 01 sent earlier is normal - the 06 is the command, and the 01 means association group 1. I think this is definitely a device bug when reviewing this against the protocol documentation.

Are these all the same device? If so, then I would expect this - if it’s a device bug, then every device would send the same erroneous information.

I can look to work around this, but I can’t do it at the moment.