Ghost node and secondary controller

Get Help
1

Hubitat C-8, platform 2.5.0.136.

I have a ghost node 0x2F / 47 showing NO DEVICE / FAILED / SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL.

Hubitat Refresh makes Remove appear/Pending, but Remove consistently fails with: “Failed node 2F remove status: 0 SDK failure node is no longer in failed node list.” Likely sibling nodes 0x30-0x33 were powered down, hub was shut down/power-cycled, same result. Z-Wave Mesh Details shows RoutingFor Count 0.

I tried adding a Zooz ZST39LR 800 USB stick through Silicon Labs PC Controller 5.56.1 as a secondary controller, but Hubitat inclusion does not detect it; PC Controller Classic Learn Mode / NWI Learn Mode ends with “Learn mode Removed completed” and the stick remains RealPrimary with only node 1.

Looking for guidance on removing node 47 or getting the secondary controller included.

Update: solved.
I was finally able to add the Z-Wave USB dongle as a secondary controller and remove the ghost.

The issue was PC Controller's Transmit Settings. The transmit mode/region in PC Controller did not match the Hubitat C-8's Z-Wave region. Once I changed the transmit setting to match the hub, the dongle joined and the network replicated normally.

After matching the transmit mode, the secondary controller joined. I selected the ghost node in PC Controller, used Is Failed, which correctly marked it failed, then Remove Failed. The ghost immediately disappeared from Hubitat.

So if PC Controller absolutely refuses to join a Hubitat C-8 as a secondary controller, check the Transmit Settings/region in PC Controller and make sure they match the hub before spending hours troubleshooting everything else.

2

Have you tried shutting down the hub and unplugging it for a minute or so (this is the only way to reboot the Z-Wave radio)? If not, give that a go and re-try the “Remove”.

3

Yes I did; no change.

4

You could try, and no one wants to hear this, waiting. Before I go to using my Zstick, I’ll usually wait a few days. In about 50% of cases the hub sorts things out and remove works. Make sure the device you are trying to remove is powered down, as it could be a device already connected via another node number. But yes there is an issue with ghost nodes and them being difficult to remove, using only the hubitat. Good new is that it’s not too frequent