Right. Then isn’t that the purpose of sending the NOP when using the Zensys tool? Won’t sending the NOP put the device in the failed list (assuming the device is really gone)?
Well spotted - this would prevent the node going onto the failed list if it wasn’t there already.
Yes, as above - that is one way to do it.
So, maybe it’s just the terminology that has me confused. If I select Set as failed from the menu in HABMin, the binding sends a RemoveFailedNodeID command?
Yes, as you pointed out, this is an error and I have just fixed this (not pushed to GH yet). It should send the “set as failed” command - it’s just calling the wrong command.
This might explain some issues, but many devices should end up on the failed list due to the binding sending the NOP to all devices on startup.
Ah, good! I was starting to wonder if I had had too many beers this afternoon. 
1 Like
Now I’m confused! You mean there is such a thing as “too many beers”?
Take a look at the following PR - comments welcome…
Not when you have 2 kegs on tap at home. 
I’ll take a look.
Ouch - enjoy tomorrow morning 
I added a comment to the PR.
I agree with your comment, and also your assumption is correct.
ZWave isn’t really the best thought through or documented system - probably a result of being a closed protocol.
1 Like
Hi all,
so is there a solution now? because I also have the same problem with this “gost” nodes.
In my case it is like 1 powered a node and found it trough Habmin, but then I didn’t added it as a thing.
I unpowered the device an deleted it from the inbox but if I do a search for new devices every time I get this device. But it is powered off. I also tried the way with setting as failed and remove from controller. Same behavior. I’m on the new snapshot 2.5.0.201905191822 from yesterday.
If you don’t have solution yet, I can also provide you a log if its helpful?!
Same problem here.
Stupid question - how to add the node to the dead list? The only options in Habmin which I have under advance list are:
- remove
- set as failed
- reinitialize
- heal
Cloud you guys be so kind and explain step by step how to do that?
Thank in advance
- Set as failed
- Wait 20-30 s.
- Remove from the controller
- Restart the Openhab server
- Find your device on the things list (it would have some kind of remark like “…Z-wave network…” < don’t remember exactly.
- Delete the thing.
- You made it
Unfortunately that does not work for me.
Did exactly the steps from above but still with DEBUG logging on for zwave I see activity that stuff is sent to the node which is obviously not responding. Also all things coming back into the Inbox.
openHAB 2.5.0~S1637-1 (Build #1637) on openhabian on Raspbian 9.
Since I’m using a Razberry module I cannot use any other tools to get rid of the stuff and those Fibaro wall-plugs lose their connection every few months 
As far as I understand, you can not remove a node by the use of habmin, if the device doesn´t communicate. You´ll have to use a special tool for this, which I have forgotten the name of. And then you´ll be removing the node directly from the z-wave controller.
To be frank, zensys is garbage. The link to the software leif has mentioned is far far better and actually works properly.
Repeating a Windows tool does not help in any way because my controller is a RPi module and NOT a USB device. Does anyone know of a tool which runs on an RPi with Linux to access the controller in such a way?
If you mean the RaZberry card (you need to tell!) then you can use Z-Way, downloadable on zwave.me.
2 Likes
z-way finally did it.
Thanks for the pointer.
And I told in my first post
Since I’m using a Razberry module I cannot use any other tools to get rid of the stuff
1 Like