njogu
(Pierluigi Patuelli)
November 16, 2016, 9:35pm
1
521 21:19:03.957 [DEBUG] [.b.z.i.p.i.ZWaveNodeSerializer:138 ] - NODE 5: Serializing from file etc/zwave/node5.xml
522 21:19:03.966 [DEBUG] [.b.z.i.p.i.ZWaveNodeSerializer:141 ] - NODE 5: Error serializing from file: file does not exist.
How can I force openHab to create the XML file? What is wrong? Can I write by my hands the file?
Tks in advance
Njogu
ptmuldoon
(Paul Muldoon)
November 17, 2016, 12:07am
2
Pretty sure the XML file is not created until after the device completes initialization. Did you try removing the device in Habmin and then re-adding it?
Can you confirm the device is in the database?
rlkoshak
(Rich Koshak)
November 17, 2016, 2:49am
3
If it is a battery powered devices you will have to wake it up so the binding can interrogate it to find out what it is and generate the XML.
njogu
(Pierluigi Patuelli)
November 17, 2016, 10:41am
5
I tried everything … but the xml is not present … The sensor seems to work but not for all functionnalities. The sensor is a Philio PSM02-A multisensor. For standard functions like batteri, illumination, temperature it works; but for PIR or Contact doesn’t work becouse I nedd to configure some parametres and I can not … Any suggestion?
Below a peace of log file …
21:19:26.312 [DEBUG] [ApplicationCommandMessageClass:40 ] - NODE 5: Application Command Request (ALIVE:DETAILS)
21:19:26.328 [DEBUG] [ApplicationCommandMessageClass:58 ] - NODE 5: Incoming command class BATTERY
21:19:26.343 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:81 ] - NODE 5: Received Battery Request
21:19:26.355 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:96 ] - NODE 5: Battery report value = 100
21:19:26.379 [DEBUG] [b.z.i.protocol.ZWaveController:648 ] - Notifying event listeners: ZWaveCommandClassValueEvent
21:19:26.395 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ] - ZwaveIncomingEvent
21:19:26.414 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
21:19:26.444 [DEBUG] [ApplicationCommandMessageClass:89 ] - Transaction not completed: node address inconsistent.
21:19:26.544 [DEBUG] [eController$ZWaveReceiveThread:1530 ] - Receive Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 06 16 00 63
21:19:26.695 [DEBUG] [b.z.i.protocol.ZWaveController:1194 ] - Receive queue TAKE: Length=0
21:19:26.699 [DEBUG] [eController$ZWaveReceiveThread:1446 ] - Receive queue ADD: Length=0
21:19:26.768 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ] - Assembled message buffer = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 06 16 00 63
21:19:26.844 [DEBUG] [b.z.i.protocol.ZWaveController:1195 ] - Process Message = 01 0F 00 04 00 05 09 71 05 00 00 00 FF 06 16 00 63
21:19:26.932 [DEBUG] [b.z.i.protocol.ZWaveController:194 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 09 71 05 00 00 00 FF 06 16 00
21:19:26.956 [DEBUG] [ApplicationCommandMessageClass:40 ] - NODE 5: Application Command Request (ALIVE:DETAILS)
21:19:26.966 [DEBUG] [ApplicationCommandMessageClass:58 ] - NODE 5: Incoming command class ALARM
21:19:26.988 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:82 ] - NODE 5: Received Alarm Request
21:19:27.005 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:94 ] - NODE 5: Alarm report - Value = 0
21:19:27.020 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:113 ] - NODE 5: Alarm Type = General (0)
21:19:27.036 [DEBUG] [b.z.i.protocol.ZWaveController:648 ] - Notifying event listeners: ZWaveAlarmValueEvent
21:19:27.053 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ] - ZwaveIncomingEvent
21:19:27.067 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
21:19:27.089 [DEBUG] [ApplicationCommandMessageClass:89 ] - Transaction not completed: node address inconsistent.
21:19:27.129 [DEBUG] [eController$ZWaveReceiveThread:1530 ] - Receive Message = 01 0B 00 04 00 05 05 31 05 03 01 0E C8
21:19:27.275 [DEBUG] [b.z.i.protocol.ZWaveController:1194 ] - Receive queue TAKE: Length=0
21:19:27.281 [DEBUG] [eController$ZWaveReceiveThread:1446 ] - Receive queue ADD: Length=0
21:19:27.339 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ] - Assembled message buffer = 01 0B 00 04 00 05 05 31 05 03 01 0E C8
21:19:27.379 [DEBUG] [b.z.i.protocol.ZWaveController:1195 ] - Process Message = 01 0B 00 04 00 05 05 31 05 03 01 0E C8
21:19:27.442 [DEBUG] [b.z.i.protocol.ZWaveController:194 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 05 31 05 03 01 0E
21:19:27.473 [DEBUG] [ApplicationCommandMessageClass:40 ] - NODE 5: Application Command Request (ALIVE:DETAILS)
21:19:27.489 [DEBUG] [ApplicationCommandMessageClass:58 ] - NODE 5: Incoming command class SENSOR_MULTILEVEL
21:19:27.512 [DEBUG] [veMultiLevelSensorCommandClass:95 ] - NODE 5: Received Sensor Multi Level Request
21:19:27.531 [DEBUG] [veMultiLevelSensorCommandClass:130 ] - NODE 5: Sensor Multi Level REPORT received
21:19:27.542 [DEBUG] [veMultiLevelSensorCommandClass:140 ] - NODE 5: Sensor Type = Luminance(3), Scale = 0
21:19:27.560 [DEBUG] [veMultiLevelSensorCommandClass:149 ] - NODE 5: Sensor Value = 14
21:19:27.583 [DEBUG] [b.z.i.protocol.ZWaveController:648 ] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
21:19:27.601 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ] - ZwaveIncomingEvent
21:19:27.616 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 14
21:19:27.651 [DEBUG] [ApplicationCommandMessageClass:89 ] - Transaction not completed: node address inconsistent.
21:19:27.705 [DEBUG] [eController$ZWaveReceiveThread:1530 ] - Receive Message = 01 09 00 04 00 05 03 80 03 64 13
21:19:27.808 [DEBUG] [b.z.i.protocol.ZWaveController:1194 ] - Receive queue TAKE: Length=0
21:19:27.812 [DEBUG] [eController$ZWaveReceiveThread:1446 ] - Receive queue ADD: Length=0
21:19:27.892 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ] - Assembled message buffer = 01 09 00 04 00 05 03 80 03 64 13
21:19:28.009 [DEBUG] [b.z.i.protocol.ZWaveController:1195 ] - Process Message = 01 09 00 04 00 05 03 80 03 64 13
21:19:28.062 [DEBUG] [b.z.i.protocol.ZWaveController:194 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 05 03 80 03 64
21:19:28.143 [DEBUG] [ApplicationCommandMessageClass:40 ] - NODE 5: Application Command Request (ALIVE:DETAILS)
21:19:28.170 [DEBUG] [ApplicationCommandMessageClass:58 ] - NODE 5: Incoming command class BATTERY
21:19:28.202 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:81 ] - NODE 5: Received Battery Request
21:19:28.251 [DEBUG] [i.p.c.ZWaveBatteryCommandClass:96 ] - NODE 5: Battery report value = 100
21:19:28.270 [DEBUG] [b.z.i.protocol.ZWaveController:648 ] - Notifying event listeners: ZWaveCommandClassValueEvent
21:19:28.292 [DEBUG] [.z.internal.ZWaveActiveBinding:449 ] - ZwaveIncomingEvent
21:19:28.304 [DEBUG] [.z.internal.ZWaveActiveBinding:466 ] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
Thanks
ptmuldoon
(Paul Muldoon)
November 17, 2016, 3:59pm
6
Are you certain the Node5.xml file is missing? I’m only guessing but thinking there may be an issue with device not being in the database.
Did you check the database?
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list
I know I have 2 sensors as well that are not working correctly. And it was determined that the database needs to be corrected for them. And its possible you are having the same issue?
I believe Chris is super busy with various items, but database and other concerns. But hopefully if you can identify the item and with the debug log can determine the cause.
What does Habmin show for the device?
njogu
(Pierluigi Patuelli)
November 17, 2016, 5:11pm
7
The sensor is in the Database … When I open Habmin and I see the z-wave network, it is gray (the controller is green!) and I don’t see any properties …
Hi, I have seen similar problems. Especially when I brought a bunch (10) of door/window sensors. I started adding a 3 or 4 and it took ages to synchronize and create xml file. Afterwards I took them one by one and waited until the process has ended. That means I repeatedly woke up the device until the xml was created.
Please notice that a lot of steps should pass before xml is created. If you restart OpenHAB it just starts from scratch until it eventually succeeds in creating an xml
chris
(Chris Jackson)
November 17, 2016, 6:23pm
9
The lack of an XML is not related to the database - it means that the initialisation isn’t completed. So, the real question is why the initialisation isn’t completing, and for this you’d need to get a debug log from startup.
From the very small bit of log I see above, it’s possible that you haven’t yet woken the device up, and as pointed out above, this is necessary if the device is a battery device (which it appears to be as I see battery information being sent).
So, I would wake up the device and see if the device initialises.
njogu
(Pierluigi Patuelli)
November 18, 2016, 3:44pm
10
I tried … during wake up I have the below exception:
java.lang.RuntimeException: java.lang.ClassCastException: org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveWakeUpCommandClass cannot be cast to org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveConfigurationCommandClass
I’am using OpenHab 1.8.2 with Habmin 1.5 … are those versions correct? What binding JAR I have to use? The one that is in Habmin ore the one that come with addons?
Tks
chris
(Chris Jackson)
November 18, 2016, 4:37pm
11
I would in the first instance suggest using the latest binding (ie 1.9). If the problem continues, then please provide a debug log and I’ll take a look.
njogu
(Pierluigi Patuelli)
November 18, 2016, 4:41pm
12
Ok. 1.9 for both OpenHab and Habmin?
chris
(Chris Jackson)
November 18, 2016, 4:42pm
13
Just the binding needs to be updated - you don’t need to update the openhab runtime. HABmin is probably ok as it is (there’s no recent update).
njogu
(Pierluigi Patuelli)
November 18, 2016, 5:03pm
14
1.9.0.b2 binding it’s ok?
chris
(Chris Jackson)
November 18, 2016, 5:05pm
15
I would suggest to use the latest snapshot from here . If we need to fix any bugs, it will be with this version…
njogu
(Pierluigi Patuelli)
November 18, 2016, 5:34pm
16
I tried … something better but still not working …
As you can see I am not able to set Configuration Parametres … node5.xml is not yet created …
chris
(Chris Jackson)
November 18, 2016, 5:43pm
17
So as I suggested, if it still doesn’t work then please provide a debug log.
njogu
(Pierluigi Patuelli)
November 18, 2016, 6:09pm
18
openhab.xml (307.6 KB)
Et voilà! It’s a TXT file … not an XML
Tks in advance
chris
(Chris Jackson)
November 18, 2016, 6:46pm
19
The problem looks like it’s associated with security.
Maybe it’s worth adding a security key to see if that fixes it -:
zwave:networkKey=0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##, 0x##
njogu
(Pierluigi Patuelli)
November 19, 2016, 10:14am
20
it doesn’t work … Always the same problem … no xml file generated …
openhab.xml (176.1 KB)
chris
(Chris Jackson)
November 19, 2016, 10:35am
21
Try excluding the device and re-including it. It’s currently not responding to the NIF which might now be an issue with security.