Struggling with ZW100 Multisensor 6

I installed a ZW100 and for a day or so it seemed to be working.

Now it seems to be stuck. It’s reported as online. But the motion detection is stuck “on”, the temp is stuck at 22.6 and the luminance is at 73.

Even though I added it, it still keeps picking up a second ZW100 in the inbox. At first I tried removing it. But I just added it and it seems to be an identical device but one is saying it’s node 6 and the other node 7.

I’ve enabled ZWave debugging. This is the most recent chunk from the logs:

2020-05-15 19:40:55.453 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller status changed to ONLINE.

2020-05-15 19:40:55.455 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller is ONLINE. Starting device initialisation.

2020-05-15 19:40:55.465 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Channel zwave:device:b29f3c74:node6:sensor_temperature linked - polling started.

2020-05-15 19:40:55.466 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Channel zwave:device:b29f3c74:node6:alarm_motion linked - polling started.

2020-05-15 19:40:55.521 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties.

2020-05-15 19:40:55.532 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=134

2020-05-15 19:40:55.533 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=134. SET. Was 134

2020-05-15 19:40:55.534 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Properties synchronised

2020-05-15 19:40:55.556 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[node_1]]: Adding Controller (node_1)

2020-05-15 19:40:55.558 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration synchronised

2020-05-15 19:40:55.572 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node...

2020-05-15 19:40:55.574 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:sensor_temperature for QuantityType

2020-05-15 19:40:55.575 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:sensor_temperature for QuantityType

2020-05-15 19:40:55.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:sensor_ultraviolet for DecimalType

2020-05-15 19:40:55.579 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:sensor_ultraviolet for DecimalType

2020-05-15 19:40:55.581 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:sensor_luminance for DecimalType

2020-05-15 19:40:55.583 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:sensor_luminance for DecimalType

2020-05-15 19:40:55.584 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:sensor_relhumidity for DecimalType

2020-05-15 19:40:55.586 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:sensor_relhumidity for DecimalType

2020-05-15 19:40:55.587 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:alarm_motion for OnOffType

2020-05-15 19:40:55.589 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:alarm_motion for OnOffType

2020-05-15 19:40:55.591 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:alarm_tamper for OnOffType

2020-05-15 19:40:55.592 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:alarm_tamper for OnOffType

2020-05-15 19:40:55.594 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:b29f3c74:node6:battery-level for PercentType

2020-05-15 19:40:55.595 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:b29f3c74:node6:battery-level for PercentType

2020-05-15 19:40:55.597 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling initialised at 1800 seconds - start in 624600 milliseconds.

2020-05-15 19:40:55.598 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Device initialisation complete.

2020-05-15 19:51:20.225 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling...

2020-05-15 19:51:20.227 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling deferred until initialisation complete

I’m not sure what this is telling me apart from the last bit seems to contradict itself.

I just removed it and did a discovery. This is what I get:

Node 4 keeps coming up as well. I have no idea what that is. In the logs it just says:

2020-05-15 19:53:25.783 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery completed

2020-05-15 19:53:25.798 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! Manufacturer data not known.

Node 4 is possibly a ghost node that the controller thinks is still part of the network. It is best to mark it as failed & then remove it from the controller. I usually use HABmin for this.

2020-05-15 21:26:15.384 [ERROR] [essage.ReplaceFailedNodeMessageClass] - NODE 4: Replace failed node failed as node is functioning!

2020-05-15 21:26:15.410 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveNetworkEvent

2020-05-15 21:26:15.688 [ERROR] [essage.ReplaceFailedNodeMessageClass] - NODE 4: Replace failed node failed as node is functioning!

2020-05-15 21:26:15.690 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveNetworkEvent

2020-05-15 21:26:15.974 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 4: Is currently marked as healthy by the controller

2020-05-15 21:26:16.011 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 4: Remove failed node failed as node not found

2020-05-15 21:26:16.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveNetworkEvent

2020-05-15 21:26:43.636 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Handler disposed. Unregistering listener.

2020-05-15 21:26:43.697 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 4: Serialise aborted as static stages not complete

Oh, and node 4 has the same address as nodes 6 and 7 - ending in 3c74

What “address” are you talking about? There is no “address” in ZWave other than the node ID.

Sorry, thought it was like the MAC address:

zwave:device:b29f3c74:node4
zwave:device:b29f3c74:node6
zwave:device:b29f3c74:node7

These all get detected when I do a Zwave discovery

No - that is the controller ID - ie the HomeID or network ID.

These are just 3 different nodes returned from the controller.

So does that mean they’re 3 different devices? In my case, sensors because I haven’t got anything else Zwave. I have 3 sensors, 2 of which I’ve tried to get discovered fully on OH and one that I haven’t touched. And not sure why they’re being picked up if I haven’t put them into discovery mode, or is that not how Zwave works?

No - it’s impossible to know. They are just 3 different nodes from the controller, but it could still be the same device included multiple times. If you have reset the node without excluding a device, then this can happen since the controller still thinks the original device is included, and it then adds it again.

Well, in terms of 6 and 7, it’s definitely a duplicate as I only have one ZW100 but, as you can see from the screenshot further up, it gets picked up twice.

Yep - this is not uncommon with ZWave if you reset a device without excluding it first.

1 Like