Z-Wave repair found failed node but everything appears to be ok

Ran a Z-Wave repair and got about 15 failed nodes. Most are because I force removed a device after the normal method did not work. Was able to take care of most of them but several failed nodes remain.

One node in particular is confusing

It is noted as Node 15 in the Z-Wave node list, which is a Zooz ZEN15 and is listed as Kitchen Refrigerator.

I can turn the Zooz on and off through the app, and the refrigerator follows suit.

Energy, power, and voltage are being reported correctly.

Is this something to be concerned about? What little I know about Z-Wave is a failed node should be removed.

Edit -

I have 4 of the ZEN15 and all of them are failed nodes. Every one of them appears to be working correctly. The devices are recognized as Zooz Power Switch

Failed nodes when doing a full zwave repair (which normally isn’t necessary or recommended) may or may not indicate a problem or than a communication latency (which I would expect when doing a full repair). If the devices work from the device page then they should be good.

1 Like

I'm not sure what the original intent of this function was but I have learned it often creates ghosts since apparently it removes the device from the HE database but not from the ZWave radio database. I was using it more or less freely but noticed that my mesh hygiene has improved since I stopped.

I'd follow @thebearmay's advice and see what your zwave details look like after a day or two, especially if everything appears to be working.

Do you have any ghosts in there or just failed devices?

So “if it works, don’t fix it” will apply here. I am aware the repair is nuclear. I will monitor the mesh

As for nodes that have nothing discovered, should I leave those alone as well?

Also, can’t seem to find a way to delete these if I need to.

Yeah those look a lot like ghosts... if they are, you will need to get rid of them. There are lots of threads here about removing zwave ghosts but basically the idea is to make sure the device itself is not powered, and then the hub will figure out they have failed and give you the option to remove them. You can sometimes accelerate this process by repeated clicks on "refresh" or "repair" (when it appears) but the critical part is the devices themselves must not be powered, or must be out of range of the hub. Otherwise the hub can't tell they're no good and will not remove them. There is an alternative if HE fails to fail them, so to speak, but it involves a zwave stick and some software from silicon labs.

1 Like

I have a ghost that is currently powered and after a refresh does give me the option to remove which of course does not. I have also tried banging on the refresh and remove countless times without success.

Just confirming you're saying the device is powered on? Or powered off? I think it needs to be powered off if it is going to be removed. Or out of range of the hub, which is usually trickier.

The device is powered on. I was responding to your post that the device had to be powered off to get the remove option. I have powered it off to try to remove in the past and it is located within 5 feet of the hub.

Oh ok. The device needs to either be powered off or out of range / unreachable in order to be successfully removed by the hub. However those conditions may still not lead to a successful removal. Make sense?

How do I know which device this is a ghost of?

That can be a tad difficult to determine. Often a ghost is created as a result of an unsuccessful inclusion. In that case the next zwave node (presumaby 7) MIGHT be the corporeal node. If node 7 is a multilevel powere switch of some sort I'd say your chances are good.

1 Like