Zwave Repair Fails on Node not in Device List

I have repeated z-wave repair failures on a node with nothing showing up in the device list.

I am continuing to have strange intermittent dropout behavior that started a couple weeks ago that i cannot explain. I am wondering if it is related to this "ghost node".

Anyone seen this before?

I might not be understanding: how are you running a repair on a node that doesn't appear in the Settings > Z-Wave Details list? "Ghost nodes" have been reported to cause problems for some users, so removing it would be a good idea if you think you have one. Just not sure what else might be going on here (screenshots might be good).

Z-wave repair tries to repair "node 50" and fails because node is unreachable.

I have no such node in my device list. I'm not sure how to remove it, if it phsyically is no in my device list.

Additionally, I will have repair failures on nodes that respond despite being "unreachable."

Ah, a network-wide repair, then, I assume (not recommended in most cases but still shouldn't cause this problem). Two guesses I have: either you're looking at decimal instead of hex node IDs, or maybe you have Z-Wave database corruption (which I've seen manifested by weird logs about node IDs, though I don't recall this particular one). Not sure there is much that can be done about the latter, though recent updates should make it less likely going forward...

1 Like

It might be a good idea to post a screen cap of your Z-Wave details page. This would eliminate misunderstandings.

3 Likes

@bertabcd1234, I'm assuming corruption, but not sure how to fix it.

@dennypage

Ill uploaad screenshots to my github account as I suck at posting still.

I did a network-wide repair because i keep having very strange behavior. I am having corruption issues on my GoControl thermostat when I try to change it via zwave interface that requires removing batteries and 24v line to force reset it. I'm having Homsee HSFL100+ issues where sometimes they just flat out won't work unless I reboot the hub or walk infront of motion to get it to activate then force switch it. (personally think these things are junk but thats another story). Having switches just randomly stop working and failing to do anything but down stream nodes still work... I'm also having severe lagging on some nodes.... i mean 10 seconds sometimes and up to 30+ with repetaed failures. Once the node responds it's instant switches unless it sits for a couple minutes.

Ok....

I know what node it is looking for that is not there. It was a kiwkset 910 that is long gone as it just plain wouldn't work. Isee it sitting in my Z-Wave Details page labeled as secure keypad and under device heading it is saying "discover" with a radio button.

Welllll..... it get's better. I see this in a few device id's in the Z-wave details..... that does not show up on the device list. All linked to the same keypad it looks like.

I was able to "discover" the device with failure, it then listed pending under the status and let me force remove it. Finger's crossed, this helps.