Homeseer Zwave Door/Window Sensor Broken Post 2.4 Upgrade

jmbenner · December 20, 2018, 11:15pm

After successfully upgrading to Openhab 2.4 I follow the provided instructions specific to zwave and deleted all ‘things’ and readded from PaperUI. All devices working fine except for my battery powered Homeseer HS-HD100+ window/door sensors. These were working fine in previous stable version and seem to still be listed in the zwave device list database accurately. HS-HD100+

From PaperUI, the devices are found but never identified properly. Have tried exluding and re-adding devices using non-secure inclusion with Aeotec Z-stick controller. (as previously in 2.3)

Log - DEBUG level detail for one specific device:
2018-12-20 17:39:44.715 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! Manufacturer data not known.
2018-12-20 17:55:52.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Application Command Request (ALIVE:REQUEST_NIF)
2018-12-20 17:55:52.550 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-12-20 17:55:52.550 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Command class COMMAND_CLASS_ALARM not found, trying to add it.
2018-12-20 17:55:52.550 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Creating new instance of command class COMMAND_CLASS_ALARM
2018-12-20 17:55:52.551 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Command class COMMAND_CLASS_ALARM, endpoint 0 created
2018-12-20 17:55:52.551 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Adding command class COMMAND_CLASS_ALARM to endpoint 0
2018-12-20 17:55:52.551 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: SECURITY not supported
2018-12-20 17:55:52.551 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2018-12-20 17:55:52.552 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2018-12-20 17:55:52.552 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = BURGLAR (0)
2018-12-20 17:55:52.552 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-12-20 17:55:52.552 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-12-20 17:55:52.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Commands processed 1.
2018-12-20 17:55:52.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@657c957c.
2018-12-20 17:55:52.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@657c957c.
2018-12-20 17:55:53.454 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Application Command Request (ALIVE:REQUEST_NIF)
2018-12-20 17:55:53.454 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2018-12-20 17:55:53.454 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Command class COMMAND_CLASS_BATTERY not found, trying to add it.
2018-12-20 17:55:53.455 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Creating new instance of command class COMMAND_CLASS_BATTERY
2018-12-20 17:55:53.455 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Command class COMMAND_CLASS_BATTERY, endpoint 0 created
2018-12-20 17:55:53.455 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Adding command class COMMAND_CLASS_BATTERY to endpoint 0
2018-12-20 17:55:53.455 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: SECURITY not supported
2018-12-20 17:55:53.456 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Received COMMAND_CLASS_BATTERY V0 BATTERY_REPORT
2018-12-20 17:55:53.456 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 38: Battery report value = 63
2018-12-20 17:55:53.456 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-12-20 17:55:53.456 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BATTERY, value = 63
2018-12-20 17:55:53.457 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Commands processed 1.
2018-12-20 17:55:53.457 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3f7d1640.
2018-12-20 17:55:53.457 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3f7d1640.
2018-12-20 17:55:53.645 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Application Command Request (ALIVE:REQUEST_NIF)
2018-12-20 17:55:53.645 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-12-20 17:55:53.646 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: SECURITY not supported
2018-12-20 17:55:53.646 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2018-12-20 17:55:53.646 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: NOTIFICATION report - 0 = 0, event=3, status=255, plen=0
2018-12-20 17:55:53.646 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = BURGLAR (0)
2018-12-20 17:55:53.646 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-12-20 17:55:53.647 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-12-20 17:55:53.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Commands processed 1.
2018-12-20 17:55:53.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@53cb0ca0.
2018-12-20 17:55:53.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@53cb0ca0.

I have captured all the detail I can think to provide. Please let me know if anything else would be needed to assist and thanks in advance for any help.

rlkoshak · December 20, 2018, 11:21pm

Since they are battery powered you need to wake them up one or more times after you have included it to the Controller and accepted the Thing from the Inbox. Often the wakeup procedure is different from the inclusion/exclusion procedure.

jmbenner · December 20, 2018, 11:25pm

Thanks for the quick response. I have definitely tried waking the devices multiple times and seen no change over the last 3 days.

Press the Z-Wave button inside the sensor body to wake device

Each time this would trigger similar output from above DEBUG logs

Also tried removing and reinserting batteries but no luck.

2018-12-20 18:47:08.086 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Application Command Request (ALIVE:REQUEST_NIF)
2018-12-20 18:47:08.087 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2018-12-20 18:47:08.087 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 38: SECURITY not supported
2018-12-20 18:47:08.087 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 38: Received COMMAND_CLASS_BATTERY V0 BATTERY_REPORT
2018-12-20 18:47:08.087 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 38: Battery report value = 67
2018-12-20 18:47:08.088 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-12-20 18:47:08.088 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BATTERY, value = 67
2018-12-20 18:47:08.088 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Commands processed 1.
2018-12-20 18:47:08.088 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 38: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3852afc5.

GeKo · December 21, 2018, 4:52pm

Hi James,
I am pretty new to the whole stuff, so I dont know wether it makes sense or not. I had problems with my window sensors as well, so I was putting them into heal mode (using HABmin), pressed the button one time, and then three times (same procedure as if putting them into inclusion mode). After doing this, the devices showed up correctly in HABmin, but they didnt work. But I was then able to Reinitialise them using HABmin. Did the same again (1 click, then 3 clicks). And since then, they are working. Why? I have no clue

chris · December 21, 2018, 5:02pm

From this log, the device did not wake up, so the binding will not (ie can not) communicate with it. the Wakeup message is not the same as a report, as seen in this log.

jmbenner · December 21, 2018, 6:03pm

Removed and re-added item several more times. Followed instructions to wake item several times but still no luck. Logs showing complete but item still ‘unknown’:

2018-12-21 12:13:44.370 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Controller is ONLINE. Starting device initialisation.
2018-12-21 12:13:44.392 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Initialising Thing Node...
2018-12-21 12:13:44.392 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Device initialisation complete.

Rolled back to Openhab 2.3.0-1 and devices immediately identified and working.

Other battery operated zwave devices were functioning being identified and initializing without issue. Not sure what the problem is but will be holding off on the upgrade to 2.4 for now.

chris · December 21, 2018, 6:05pm

Please provide a debug log - at the moment it looks like you are not waking up the device, and if so, this is not a binding issue.

This is probably because you still have the persistence file - otherwise you would have the same problem with 2.3.

(ps. Please format logs using code fences, or the </> button so they are more readable)

jmbenner · December 28, 2018, 11:46pm

@chris - A few days later and taking another crack at this. Took brand new zwave sensor (same exact Homeseer device) out of package, did a fresh inclusion, woke up device about a hundred times within three feet of controller while watching logs. Woke up device using exact directions from device description (pressing wake button inside battery casing), removed and readded batteries, triggered open/close sensor - all numerous times over 15-20 minutes. I am not seeing any change in status - Device still ‘Unknown’ but clearly see in logs - ‘NODE 43: Device initialisation complete.’

This has been very frustrating as I added 3-4 of these devices in Openhab almost a year ago at least with no issues and hardly any effort. Thanks again in advance for any assistance.node43.txt (463.6 KB)

2018-12-28 17:55:35.762 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:44e58a3e:node43' has been added.
2018-12-28 17:55:47.229 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:44e58a3e:node43' has been removed.
2018-12-28 17:55:47.232 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from UNINITIALIZED to INITIALIZING
2018-12-28 17:55:47.232 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-12-28 17:55:47.232 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-12-28 17:55:47.243 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 17:55:47.262 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 17:55:47.272 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 17:57:08.184 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 17:57:38.878 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2018-12-28 17:57:40.976 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2018-12-28 18:02:06.549 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:03:13.187 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2018-12-28 18:03:20.828 [hingStatusInfoChangedEvent] - 'zwave:device:44e58a3e:node43' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2018-12-28 18:03:20.835 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:03:34.277 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:03:34.284 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:07:39.821 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:08:30.629 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:09:27.451 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:10:05.585 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:12:00.938 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:12:16.459 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:12:20.305 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:12:48.894 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 18:13:22.425 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:44e58a3e:node43' has been updated.
2018-12-28 17:55:07.864 [DEBUG] [age.SerialApiGetInitDataMessageClass] - NODE 43: Node found
2018-12-28 17:55:07.883 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 43: Init node thread start
2018-12-28 17:55:07.973 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 43: Serializing from file /var/lib/openhab2/zwave/network_e70a370d__node_43.xml
2018-12-28 17:55:07.973 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 43: Error serializing from file: file does not exist.
2018-12-28 17:55:08.006 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Starting initialisation from EMPTYNODE
2018-12-28 17:55:08.019 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 43: Init node thread finished
2018-12-28 17:55:08.019 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Node advancer - advancing to IDENTIFY_NODE
2018-12-28 17:55:08.020 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Node advancer: Initialisation starting
2018-12-28 17:55:08.072 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: ProtocolInfo
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Listening = false
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Routing   = true
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Beaming   = true
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Version   = 4
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: FLIRS     = false
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Security  = false
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Max Baud  = 40000
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Basic    = BASIC_TYPE_ROUTING_SLAVE
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Generic  = GENERIC_TYPE_SENSOR_NOTIFICATION
2018-12-28 17:55:08.073 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 43: Specific = SPECIFIC_TYPE_NOTIFICATION_SENSOR
2018-12-28 17:55:08.073 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Creating new instance of command class COMMAND_CLASS_NO_OPERATION
2018-12-28 17:55:08.073 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Command class COMMAND_CLASS_NO_OPERATION, endpoint 0 created
2018-12-28 17:55:08.073 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Version = 1, version set. Enabling extra functionality.
2018-12-28 17:55:08.073 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Adding command class COMMAND_CLASS_NO_OPERATION to the list of supported command classes.
2018-12-28 17:55:08.073 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Creating new instance of command class COMMAND_CLASS_BASIC
2018-12-28 17:55:08.073 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Command class COMMAND_CLASS_BASIC, endpoint 0 created
2018-12-28 17:55:08.074 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Adding command class COMMAND_CLASS_BASIC to the list of supported command classes.
2018-12-28 17:55:08.080 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Node Init response (0) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@637f0c20
2018-12-28 17:55:08.080 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Node Init transaction completed with response COMPLETE
2018-12-28 17:55:08.080 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Node advancer - advancing to REQUEST_NIF
2018-12-28 17:55:08.081 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@267d8e2b
2018-12-28 17:55:08.081 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Bump transaction 20 priority from Controller to Immediate
2018-12-28 17:55:08.081 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Adding to device queue
2018-12-28 17:55:08.081 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Added 20 to queue - size 5
2018-12-28 17:55:35.760 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 43: Device discovery completed
2018-12-28 17:55:35.761 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 43: Device discovery could not resolve to a thingType! Manufacturer data not known.
2018-12-28 17:55:35.761 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:44e58a3e:node43' to inbox.
2018-12-28 17:55:47.231 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:44e58a3e:node43.
2018-12-28 17:55:47.232 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: MANUFACTURER not set
2018-12-28 17:55:47.232 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Controller status changed to ONLINE.
2018-12-28 17:55:47.232 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Controller is ONLINE. Starting device initialisation.
2018-12-28 17:55:47.243 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating node properties.
2018-12-28 17:55:47.262 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating node properties. MAN=2147483647
2018-12-28 17:55:47.262 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Properties synchronised
2018-12-28 17:55:47.272 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Initialising Thing Node...
2018-12-28 17:55:47.272 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Polling intialised at 1800 seconds - start in 1395000 milliseconds.
2018-12-28 17:55:47.272 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Device initialisation complete.
2018-12-28 17:56:04.421 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 43: Device discovered

chris · December 29, 2018, 10:18am

There is no sign of the device waking up in this log at least. This is quite a short log and there’s not really much I can comment on from it.

jmbenner · December 29, 2018, 12:15pm

@chris Sorry it was not specified above - attached is full log entry from the above described sequence of events for this node: node43.txt (463.6 KB)

If more is required, can I have some guidelines?
i.e. simply a full unfiltered log copied down from server (events.log || openhab.log), etc.

chris · December 29, 2018, 12:18pm

Please provide the full log - by filtering it, you remove all the responses from the device, so I can only see the data being sent by the binding in this log.

chris · December 29, 2018, 12:18pm

Other than the filtering, this log looks like it will have good information - I can guess what is happening, but want to confirm with the full log.

jmbenner · December 29, 2018, 12:44pm

Thanks for the quick response @chris

Had to host the file as it is too large for upload here apparently: Dropbox

chris · December 29, 2018, 12:50pm

Thanks - this is useful. I’ll need to take a look at the root cause which is related to the fact that the binding things the device is awake, but there was a delay, and in reality, it has gone back to sleep.

chris · December 29, 2018, 3:27pm

I’ve made a change that will hopefully help this issue -:

Unfortunately something is broken in the CI system at the moment so all ZWave builds are failing due to a dependency issue somewhere in the OH build. Until this is fixed, I can’t merge .

jmbenner · December 31, 2018, 3:45pm

Once the OH dependency issue is resolved and you are able to merge these changes, would this fix be available from the nightly build only?

chris · December 31, 2018, 4:09pm

Yes, it’s only available in the snapshot. It’s impossible to rebuild a previously released version. It should also be available in the milestone versions while get released once a month.

MFornander · March 26, 2019, 10:25am

Spent another few hours on OH2 tonight but I seem to grind into device issues. I can’t add these HomeSeer Door Sensors. I’ve tried back and forth OH2.4-M1 and OH2-latests snapshot. My old Hank Sensors that look the same work just fine but these new HS-DS100+ sensors seem to get stuck. They do show up correctly in Habmin but there is no Z-Wave activity is seen in the log when clicking tamper switch or on open/close.

The seem to be stuck on the VERSION stage. I’ve tried for hours now with various combos of add/remove, reset (hold device button for 20 sec), wake (triple click after included) but no luck.

The log below is after the sensor is added and after several triple click to try to wake it up past the “version stage”… Heal will not work because:

NODE 93: Can not start heal as initialisation is not complete (VERSION).

This is on 2.5.0-SNAPSHOT Build #1561

On a brighter note, my Z-COMBO Smoke detectors are now included fine in the latest snapshot whereas I lost an evening battling with them a month ago

node93.log (209.8 KB)