Remove a ghost Z-Wave Node from HABmin

[dan12345 (Dan)]

I’ve run the Aeotec zwave tools successfully on a vmware virtual windows box on my mac, if that’s any help. That removes dead notes easily.

[markus7017 (Markus Michels)]

I have VM ware, but no suitable Windows Image, so…

But in any case it shows that it is possible, so @chris might find a trick to fix that issue.

[dan12345 (Dan)]

yes - backing up and killing dead nodes directly from openhab would be fantastic…

[sihui]

@dan12345

would be fantastic…

You may accelerate it:

Introducing BountySource for funded development

All, While in the early days of openHAB every user was also a developer, the number of non-tech users steadily grew over time. This led us to the situation, where the number of ideas and feature requests clearly outweighs the capacity of the openHAB developer community. Having more ideas than it is possible to implement brings up the question of prioritisation. For users that are developers, this is rather easy as they decide for themselves what is most important for them and then come up with…

[hl_at (Herbert)]

@ellisbjohns

For those of you trying to remove a node using zensys tool here are the steps required:

1. Highlight the node you believe has failed from the top left frame’s node list/table
2. Toggle the “Quene Overrided” checkbox for this selected node (a check should appear)
3. Send a NOP (i.e. no operation) command by selecting the exclamation mark from the tools menu
4. Check to see if the node is failed by selecting the “is node failed” icon from the tools menu. If it has failed, you should see a message stating it has failed in the lower right frame (i.e. log actions tab)
5. Select the “remove failed” icon from the tools menu
   Note: If uncertain which icon from the tools menu corresponds to a particular action, hoover your mouse over each to receive a “tool tip” message specifying the corresponding action.

Dear Ellis!

Thanks for the “manual” - do you know what step 1 does/means technically seen?

Regards,
Herbert

[ellisbjohns (Ellis Johns)]

@hl_at.
Truthfully, I’m not exactly sure as I wrote these instructions about a year ago. One thing I have noticed is that openhab’s zwave binding doesn’t always reflect the true state of the node when compared with the z-stick controller’s node state (i.e. eprom). This often leads to inconsistencies that have to be addressed using a third party tool which directly changes the z-sticks internal node status (e.g. Zensys). The combo of Zensys and Chris Jackson’s binding have allowed me to accomplish a ton of zwave reconfigurations over the past year, but either tool alone has not been sufficient. Step #1 likely allows you to delete a node which the z-wave binding believes to be dead/failed but the node still has an active entry in the zstick’s eprom (i.e. it was never truly deleted by the bindings api calls to the zstick). Hope this helps.

[chris (Chris Jackson)]

@ellisbjohns

One thing I have noticed is that openhab’s zwave binding doesn’t always reflect the true state of the node when compared with the z-stick controller’s node state (i.e. eprom)

I think this is very unlikely. The binding reads the list of nodes directly from the controller (ie eprom) so it will be consistent.

I think what you are talking about is removal of devices that appear in the OH list, but can’t be removed - I think this is a bit different…

[ellisbjohns (Ellis Johns)]

@chris

I think what you are talking about is removal of devices that appear in the OH list, but can’t be removed - I think this is a bit different…

Yeah…What Chris said

[shorty707]

@ellisbjohns

party tool which directly changes the z-sticks internal node status (e.g. Zensys).

hey @ellisbjohns
I havent tried the zensys tool yet (link not working atm).
Do you know if this tool has a option to change the state from FAILED to OK ?
I have some nodes that acutally work but the controller lists them as failed and therfore openhab reads them as offline

cheers

[chris (Chris Jackson)]

@shorty707

Do you know if this tool has a option to change the state from FAILED to OK ?

No - this isn’t possible. Only the controller can do this.

[TheNetStriker (David Masshardt)]

I think I finally found a way to also delete nodes that are not marked as dead by the controller. I also used the Zensys tool, but instead of using the “Remove Failed” function I used the “Replace Failed” function. (to the left of the remove function)

Simply click on the node you like to remove, start the function and put any Z-Wave device in inclusion mode. (I used a switch I don’t use at the moment) After a few seconds the progressbar disappears and the node is put to the end of the list. Now the node is replaced with my switch and I can simply put the controller and the switch into remove mode and the node is gone!

I tried this with 3 nodes that I had for a long time on my controller and it worked on all of them.

@chris Maybe you could implement this replace function into your addon so we don’t always have to unplug the Z-Stick?

[anfaenger (rud)]

@sercasyr

I have two nodes for the same device. One works fine. The other is a ghost node.

Me too. Meanwhile I have eleven of them.

@hubertus_hettenkofe1

Put the stick to a windows pc. There you can use the tools ZTools or ZenSYS-Tools to delete the device.

My z-Wave-Controller is a raZberry-Board on Raspberry Pi3. So no usb-stick that I can put somewhere.
Is there such a tool available that can be installed on a RPi3?

@xsnrg

I try to just ignore them

To me it feels like those failed or dead devices slow down my system because the controller constantly tries to connect to them. That’s the reason I would like to get rid of them.
@chris Is that right? If not, I also would ignore them.

By the way: I use PaperUI to include and rename z-wave-devices. And HABmin to configure the z-wave-devices.
@chris Would you recommend, NOT to use PaperUI? Should I do everything with HABmin instead? Could this in general prevent some problems?

Thanks a lot!

[sihui]

@anfaenger

That’s the reason I would like to get rid of them.

Did you already try the “usual” way?
Go to HABmin, select your node, Tools … Show advanced settings. Then click “Set device as failed”, wait a minute, then “Remove device from controller”.
After that it may still be there but after an openHAB restart it should be gone.

[chris (Chris Jackson)]

As @sihui said - this should implement the functionality to remove devices…

[anfaenger (rud)]

Yes. Sorry that I didn’t describe more detailed what I’ve tried so far.

This are some of the nodes I would like to get rid of.
All this devices have worked fine but at some point didn’t anymore. After many tries, I got them reincluded and they are working fine now with a new node-number. But the old node numbers are still listed, like you can see below:

When I’m trying what you suggest, I get those errors.

Doesn’t matter if the device is communicating with the controller or not. And doesn’t matter if I try “Set device as failed” or “Remove device from controller”.

I did spend a lot of time searching the forum, reading many posts and trying to solve this. And at some point I gave up. Maybe because of my missing skills.

So, at the moment I don’t want to burden you with that. I would like to know if this nodes don’t effect my z-wave-net. Then I would just ignore them. But I don’t believe so. .

[sihui]

Do those get rediscovered when you just delete the “things”?

[Kim_Andersen]

@anfaenger

Doesn’t matter if the device is communicating with the controller or not. And doesn’t matter if I try “Set device as failed” or “Remove device from controller”.

I did spend a lot of time searching the forum, reading many posts and trying to solve this. And at some point I gave up. Maybe because of my missing skills.

I had the same experiences. Couldn´t remove a node from Habmin, got the same communication error.

[chris (Chris Jackson)]

I don’t speak German (sorry) so can you tell me what this means, or provide a debug log please?

[anfaenger (rud)]

After a reboot something has changed and I don’t get this error again.
Don’t know why just now. I need to reboot almost every day and that didn’t change this error in the past. Sorry, if this is a mistake on my side and @chris sorry because of the german screenshot. “Fehler beim Senden der Aktion” means “Error while sending the action”.

@sihui

Do those get rediscovered when you just delete the “things”?

All Nodes, which had been online before deleting them (16, 18, 23…) are rediscovered when I delete them:

I also tried “Set device as failed” or “Remove device from controller” without success.

But I have had one success:
All Nodes, which had been offline before deleting them (44, 45… not communicating with controller) are not rediscovered when I delete them.
Making a little progress is feeling good!

Maybe because I deleted and discovered with HABmin for the first time now? Before I used to use PaperUI to do this. Can that make a difference?
Or maybe because something chandged since the last reboot?

openhab.log:

2018-06-05 18:52:21.704 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node12' to inbox.
2018-06-05 18:52:21.720 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 16: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:21.727 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node16' to inbox.
2018-06-05 18:52:21.758 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:21.765 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node18' to inbox.
2018-06-05 18:52:21.773 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:21.789 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:21.847 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node23' to inbox.
2018-06-05 18:52:21.924 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node31' to inbox.
2018-06-05 18:52:21.964 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 35: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:21.973 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node35' to inbox.
2018-06-05 18:52:22.014 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 36: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:22.027 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node36' to inbox.
2018-06-05 18:52:22.074 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node41' to inbox.
2018-06-05 18:52:22.092 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 45: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:22.101 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node45' to inbox.
2018-06-05 18:52:22.112 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 46: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-06-05 18:52:22.121 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:22b201ea:node46' to inbox.

[sihui]

@anfaenger

I need to reboot almost every day

Why that???