Z Wave Binding Phantom Things

Hi folks,

I’m not sure if this is the right place for my topic, but as this last already with the “old” z wave Binding I don’t see this in the News channel.

Sometimes a device is not included correct. Openhab has it in the inbox and it can be added, but the device is still uninitialized. If I try to remove it from the controler I get in Habmin an “unkown error”. I can delete the Thing, but on a new start of an inclusion all these devices are “found” again.

I found a hint to add the device as thing, select the thing and to remove it from the controller in the extended settings, but that doesn’t work. As my z wave controller is a Raspberry GPIO module I can’t connect that to a Windows PC and remove it with another tool, as mentioned elsewhere.

It’s getting more and more difficult when adding new devices as until now I’ve 9 of these zombies. Any ideas except to start from scratch, which is not feasible with ca. 20 working z wave devices in my installation?

Start z wave inclusion:

2019-01-21 23:08:01.363 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.373 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node33' to inbox.
2019-01-21 23:08:01.415 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 35: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.425 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node35' to inbox.
2019-01-21 23:08:01.495 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.502 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node12' to inbox.
2019-01-21 23:08:01.517 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.522 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node14' to inbox.
2019-01-21 23:08:01.529 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.535 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node15' to inbox.
2019-01-21 23:08:01.571 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.577 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node26' to inbox.
2019-01-21 23:08:01.583 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 27: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.590 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node27' to inbox.
2019-01-21 23:08:01.595 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.602 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node28' to inbox.
2019-01-21 23:08:01.608 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-01-21 23:08:01.615 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:Razberry2:node29' to inbox.

Add Node 12:

2019-01-21 23:17:53.093 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:Razberry2:node12' has been removed.
2019-01-21 23:17:53.153 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node12' changed from UNINITIALIZED to INITIALIZING
2019-01-21 23:17:53.288 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node12' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-01-21 23:17:53.298 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node12' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-01-21 23:17:53.364 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node12' has been updated.
2019-01-21 23:17:53.426 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node12' has been updated.
2019-01-21 23:17:53.489 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:Razberry2:node12' has been updated.

Node 12 “Set Device as Failed”:

2019-01-21 23:05:39.241 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 12: Remove failed node not placed on stack due to error 0x18.

Remove Node 12 from Controller:

2019-01-21 23:26:45.750 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 12: Remove failed node failed as node not found

And finally the output from Delete thing for Node 12:

2019-01-21 23:28:47.138 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node12' changed from ONLINE to UNINITIALIZED
2019-01-21 23:28:47.301 [hingStatusInfoChangedEvent] - 'zwave:device:Razberry2:node12' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

Platform information:
Release = Raspbian GNU/Linux 9 (stretch)
Kernel = Linux 4.14.79-v7+
Platform = Raspberry Pi 3 Model B Plus Rev 1.3
z-wave controller Razberry2
openHAB 2.4.0-1 (Release Build)
227 x Active x 80 x 2.4.0 x ZWave Binding

I found that using the Zensys tool is the best way to remove “ghost” nodes from the controller. Google for “Zensys tools download” and you’ll find a download link. It only runs on Windows.

Hi Mark,

but how can it act with the module on the razbery?

I’m sorry. I thought you had a USB stick. I now see that it’s a Razberry2. I’m not sure what to suggest in that case.