Hello,
I installed OH2 on my synology with habmin2. All is working,
For Zwave 8 items are recognized (7 as unknow device, 1 correctly recognized).
I have to wait since all things are paired correctly? Can I check something?
Thanks Chris
If they are battery devices, they might take some time to be found correctly. Mains devices should be reasonably quick.
Do the devices show up with a type/id, or just as unknown? Do they have XML files generated for them?
If you’re using HABmin, what shows up in the attributes for the manufacturer/type/id?
Chris
Thak you Chris,
I don t know where to look… it seem that I can t click …
how I know if my package zwave is up-to-date? I installed from the menu extension.
I found. In the previous page i clicked advanced option and the address of items are ffff ffff:ffff
UPDATE
Chris, as new user I can post only 3 posts and only 1 image for post. The XML is created only for the recognized devices
Ok - at least for the device you should here, this needs to wake up so that the discovery can complete as it is a battery device (listening flag is x). This might take some time, or you can normally force the wakeup by pressing a button on the device.
The XML files are in /userdata/zwave - it would be interesting to see if they exist for any devices.
Chris,
Thanks for your work, I sent you a large logfile. Let me know if there is any other info you need. I’ve been letting it run and it seems to be working a bit, adding items to the inbox. I chose one in the same room as the ZStick to add and got this output in the debug log:
12:09:10.700 [INFO ] [smarthome.event.InboxRemovedEvent ] - Discovery Result with UID 'zwave:device:c3e91c3f:node7' has been removed.
12:09:10.710 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing 'zwave:device:c3e91c3f:node7' has been added.
12:09:10.714 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler.
12:09:10.715 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from UNINITIALIZED to INITIALIZING
12:09:10.721 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=zwave:device, thing.id=zwave:device:c3e91c3f:node7, service.id=372, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.729 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=373, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller initialised.
12:09:10.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller status changed.
12:09:10.748 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from INITIALIZING to OFFLINE
12:09:10.749 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller is ONLINE. Starting device initialisation.
12:09:10.751 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller status changed.
12:09:10.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller is ONLINE. Starting device initialisation.
12:09:10.755 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured during notification of thing 'zwave:device:c3e91c3f:node7' about bridge initialization at 'null': null
java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:500)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeHandlerInitialized(ZWaveThingHandler.java:395)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.eclipse.smarthome.core.thing.internal.ThingManager$8.run(ThingManager.java:750)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
12:09:10.756 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to ONLINE
12:09:10.757 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from OFFLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
12:09:10.766 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Handler disposed. Unregistering listener.
12:09:10.767 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'zwave:device:c3e91c3f:node7': java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_65]
at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_65]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:179)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:72)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:56)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7.run(ThingManager.java:684)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:500)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:140)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7$1.call(ThingManager.java:687)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7$1.call(ThingManager.java:1)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:170)[98:org.eclipse.smarthome.core:0.8.0.b5]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
... 3 more
12:09:10.769 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=zwave:device, thing.id=zwave:device:c3e91c3f:node7, service.id=372, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.776 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from ONLINE to UNINITIALIZED (HANDLER_INITIALIZING_ERROR)
12:09:10.782 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=373, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.885 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR) to INITIALIZING
12:09:10.887 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler.
12:09:10.888 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=zwave:ge_zw4005_00_000, thing.id=zwave:device:c3e91c3f:node7, service.id=374, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.891 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller initialised.
12:09:10.891 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller status changed.
12:09:10.892 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller status changed.
12:09:10.892 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller is ONLINE. Starting device initialisation.
12:09:10.892 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Controller is ONLINE. Starting device initialisation.
12:09:10.893 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from INITIALIZING to OFFLINE
12:09:10.896 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured during notification of thing 'zwave:device:c3e91c3f:node7' about bridge initialization at 'org.openhab.binding.zwave.handler.ZWaveThingHandler@b0c0f4': null
java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:500)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeHandlerInitialized(ZWaveThingHandler.java:395)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.eclipse.smarthome.core.thing.internal.ThingManager$8.run(ThingManager.java:750)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
12:09:10.899 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from OFFLINE to ONLINE
12:09:10.905 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'zwave:device:c3e91c3f:node7': java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_65]
at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_65]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:179)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:72)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:56)[98:org.eclipse.smarthome.core:0.8.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7.run(ThingManager.java:684)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:500)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:140)[192:org.openhab.binding.zwave:2.0.0.b3]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7$1.call(ThingManager.java:687)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager$7$1.call(ThingManager.java:1)[104:org.eclipse.smarthome.core.thing:0.8.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:170)[98:org.eclipse.smarthome.core:0.8.0.b5]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
... 3 more
12:09:10.906 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c3e91c3f:node7' changed from ONLINE to UNINITIALIZED (HANDLER_INITIALIZING_ERROR)
12:09:10.909 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=375, service.bundleid=192, service.scope=singleton} - org.openhab.binding.zwave
12:09:10.916 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:c3e91c3f:node7' has been updated.
12:09:10.992 [INFO ] [smarthome.event.ItemAddedEvent ] - Item 'zwave_device_c3e91c3f_node7_switch_binary' has been added.
12:09:10.993 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'zwave_device_c3e91c3f_node7_switch_binary-zwave:device:c3e91c3f:node7:switch_binary' has been added.
I’ll give it a few hours and see what happens.It might find all 50 nodes.
restarted OH2 and the ThingManager exception went away. I guess it crashed
I looked over the log - there’s an issue with initialising some of the devices which I’ll add a fix for (hopefully!) today. The other issue noticeable in the log is the log isn’t initialising which is something I’m still working on (ie the security classes).
Of your many nodes, many hadn’t woken up in the time the log was acquired, so hopefully more are working now?
Chris,
Yes. I left it running for a few hours yesterday and it picked up all of
the light switches and a couple of three battery devices. I was able to
turn on and off the switches through oh2 and see some contact sensors
working.
I woke up a couple other battery devices but it seems like they have to
wake up at the time the binding is querying then because they weren’t added.
The binding didn’t create any XML files for the switches, just the battery
devices.
I copied the security key from oh1s zwave binding but I figured the door
lock would still need to be re paired, which is OK.
Thanks for your help,
Mike
I recently had to delete and recreate the Z Wave Serial Controller thing. Unfortunately it seems I didn’t use the same name, which wouldn’t be that big of a deal if it weren’t for the fact that it didn’t do a very good job cleaning up after itself. A lot of auto-created items were left behind, and some of my manually created items are still bound to the now non-existent channels because I’m seeing a LOT of entires like this in my log:
12:20:18.072 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'Light_TV' to handler for channel 'zwave:device:controller:node4:switch_binary', because no thing with the UID 'zwave:device:controller:node4' could be found.
Is there any way to delete these bindings?
No. See here -:
Note that items won’t be deleted since they are not part of the thing, but the links should be…
@chris I noticed that you added in an automatic refresh poll for multilevel switches in order to handle the case where their value doesn’t update right away (as is the case with GE dimmers). Is there any way to adjust the delay for this poll? I noticed that at least with my switches, it’s still too quick. Ideally if turning it on/off to 100%/0%, it would end up with those values when it fires.
@chris Next question. I recently updated my setup, and noticed that the rules for zwave doorbell sensor stopped working (DB100Z). I turned on debug mode for the zwave binding and it looks like everything is coming it. Here’s what I think is happening though: The device uses the ALARM class and sends an ‘OFF’ command. The only time it technically changes is the first time after the Item is initialized (it goes from NULL to OFF). Subsequent presses send the same state (OFF), so in the end, the Item does change (it also doesn’t fire ‘received update’).
Here’s the log output:
20:12:55.481 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class ALARM
20:12:55.483 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Received Alarm Request V3
20:12:55.485 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Process Alarm Report, V3, length 13
20:12:55.486 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm report - 8 = 0, sensor=0, event=0, status=255
20:12:55.489 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm Type = Power Management (8)
20:12:55.490 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
20:12:55.492 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got an event from Z-Wave network: ZWaveAlarmValueEvent
20:12:55.493 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
20:12:55.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating channel state zwave:device:home:node14:alarm_general to OFF [OnOffType]
20:12:55.500 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Transaction not completed: node address inconsistent. lastSent=11, incoming=255
20:13:11.259 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
20:13:11.268 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:13:11.274 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
20:13:11.280 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
20:13:11.285 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 0A 71 05 00 00 00 FF 08 01 00 00
20:13:11.287 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:DONE)
20:13:11.289 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Starting initialisation from DONE
Hi,
Anyone can give some light with one of my devices (FGBS001 - Binary switch) where the initialization status seems to stall to ONLINE: STATIC_VALUES. The device seems to work although not perfectly which is something I’m investigating.
'zwave:device:c58043b5:node3' changed from ONLINE: VERSION to ONLINE: ENDPOINTS
2016-06-01 12:56:29.464 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c58043b5:node3' changed from ONLINE: ENDPOINTS to ONLINE: UPDATE_DATABASE
2016-06-01 12:56:29.480 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:c58043b5:node3' changed from ONLINE: UPDATE_DATABASE to ONLINE: STATIC_VALUES
After some time I get the following :
2016-06-01 13:32:08.656 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 3: Got an error while sending data. Resending message.
2016-06-01 13:40:40.462 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer: Retries exceeded at STATIC_VALUES
Thank you in advance
@chris is there any way we can amend the database/XML or the resulting channel definitions to set things such as motion sensors as read only?
You need to make the modification to the online database - I then export the files into the JAR.
You can provide a PR if you think some of the channel definitions aren’t correct. For sure some of them are probably not right, and I can’t test them all here, so your feedback is definately welcome. If you don’t want to do a PR, then I can update the channels if you give me a list of the things you think should be changed…
Probably this is using the new notification version of the ALARM class. Hopefully this will be included soon.
Strange - it should. It’s hard to tell from the log since it doesn’t seem to complete the processing of the second message - is that everything that was logged - if so, I don’t know what happened as the mesage doesn’t seem to be processed at all…
I’d need to see a debug log. If you can email me a full log during startup it would be good…
Interesting…it was working before though without issues. Here’s a larger chunk of the log…it looks to be the same block as above, but repeated (each time I tried pressing the doorbell):
2016-05-31 19:57:46.245 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-05-31 19:57:46.256 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 0A 03 20 01 FF 25
2016-05-31 19:57:46.258 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 0A 03 20 01 FF 25
2016-05-31 19:57:46.260 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 03 20 01 FF
2016-05-31 19:57:46.262 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
2016-05-31 19:57:46.264 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
2016-05-31 19:57:46.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@19d18c3 already registered
2016-05-31 19:57:46.269 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class BASIC
2016-05-31 19:57:46.273 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 10: Received Basic Request
2016-05-31 19:57:46.277 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 10: Basic Set sent to the controller will be processed as Basic Report
2016-05-31 19:57:46.280 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 10: Basic report, value = 0xFF
2016-05-31 19:57:46.284 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-05-31 19:57:46.287 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-05-31 19:57:46.290 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2016-05-31 19:57:46.294 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Transaction not completed: node address inconsistent. lastSent=14, incoming=255
2016-05-31 19:57:46.327 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0A 03 30 03 FF 37
2016-05-31 19:57:46.331 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-05-31 19:57:46.334 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 0A 03 30 03 FF 37
2016-05-31 19:57:46.338 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 0A 03 30 03 FF 37
2016-05-31 19:57:46.341 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 03 30 03 FF
2016-05-31 19:57:46.345 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
2016-05-31 19:57:46.348 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
2016-05-31 19:57:46.351 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@19d18c3 already registered
2016-05-31 19:57:46.353 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class SENSOR_BINARY
2016-05-31 19:57:46.356 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 10: Received SENSOR_BINARY command V1
2016-05-31 19:57:46.359 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 10: Sensor Binary report, type=Unknown, value=255
2016-05-31 19:57:46.361 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2016-05-31 19:57:46.364 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2016-05-31 19:57:46.366 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2016-05-31 19:57:46.370 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:home:node10:sensor_binary to ON [OnOffType]
2016-05-31 19:57:46.375 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Transaction not completed: node address inconsistent. lastSent=14, incoming=255
2016-05-31 19:57:46.382 [INFO ] [marthome.event.ItemStateChangedEvent] - Sensor_Front_Door changed from OFF to ON
2016-05-31 19:57:46.397 [ERROR] [.script.engine.ScriptExecutionThread] - Error during the execution of rule 'Front Door Opened': org.eclipse.smarthome.core.library.types.DateTimeType
2016-05-31 19:57:51.583 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
2016-05-31 19:57:51.590 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-05-31 19:57:51.593 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
2016-05-31 19:57:51.595 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 01 00 00 6D
2016-05-31 19:57:51.597 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 0A 71 05 00 00 00 FF 08 01 00 00
2016-05-31 19:57:51.599 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:DONE)
2016-05-31 19:57:51.600 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Starting initialisation from DONE
2016-05-31 19:57:51.602 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@187a047 already registered
2016-05-31 19:57:51.603 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class ALARM
2016-05-31 19:57:51.605 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Received Alarm Request V3
2016-05-31 19:57:51.606 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Process Alarm Report, V3, length 13
2016-05-31 19:57:51.608 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm report - 8 = 0, sensor=0, event=1, status=255
2016-05-31 19:57:51.609 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm Type = Power Management (8)
2016-05-31 19:57:51.611 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-05-31 19:57:51.612 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-05-31 19:57:51.613 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-05-31 19:57:51.616 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Updating channel state zwave:device:home:node14:alarm_general to OFF [OnOffType]
2016-05-31 19:57:51.620 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=14, callback=82, payload=0E 02 84 08
2016-05-31 19:57:51.622 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 0A 71 05 00 00 00 FF 08 01 00 00
2016-05-31 19:57:51.624 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=82, expected=SendData, cancelled=false MISMATCH
2016-05-31 19:57:52.602 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 00 00 00 6C
2016-05-31 19:57:52.606 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-05-31 19:57:52.608 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 00 00 00 6C
2016-05-31 19:57:52.610 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0E 0A 71 05 00 00 00 FF 08 00 00 00 6C
2016-05-31 19:57:52.619 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 0A 71 05 00 00 00 FF 08 00 00 00
2016-05-31 19:57:52.623 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:DONE)
2016-05-31 19:57:52.627 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Starting initialisation from DONE
2016-05-31 19:57:52.628 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@187a047 already registered
Before what 
.[quote=“feens, post:1326, topic:7522”]
it looks to be the same block as above, but repeated
[/quote]
The two messages from node 14 which I assume you mean are different and they use the new notification class.