Can't add Z-wave devices anymore

🛎️ Get Help
1

Hello! Hoping someone can help me out!

I have a C-8 Pro Platform version 2.4.3.176.
It's connected by Ethernet with a static IP.
It's powered by the supplied power block.

When I bought the device about a month ago I was able to add a garage door opener, a couple of Kwikset door locks and GE Z-wave switches. I did run into issues adding one of my Kwikset door locks and one of the Linear garage door openers. They would begin to pair but then timeout. I figured something was wrong with the devices so I bought a new z-wave garage door opener and a new Kwikset door lock. Same issues. I can't include or exclude anything.

I checked to make sure my antennas are straight up and down. I've shutdown the device and unplugged it multiple times for 30 minutes, I've rebuilt the network and nothing changes.

I read about ghost nodes and I seem to have a few. In the Z-wave details I've clicked refresh a bunch of times and don't get the option to remove them.

The logs show this: [sys:1] warn Z-Wave Network responded with Busy message.

I bought a Z-wave stick and followed the instructions to use Simplicity Studio to remove the ghost nodes and I'm having the same issue, the hub won't add any Z-wave devices so I can't get my Z-wave stick on the network to remove the ghost nodes.

I'm at a complete loss.

Screenshot 2026-01-18 at 11.23.17 AM
Screenshot 2026-01-18 at 11.23.17 AM1920×987 124 KB

2

Looks like you indeed have many ghosts, so that is likely part of the issue. I would suggest switching to Z-Wave JS if you haven’t already - it will make it easier to remove the ghosts directly from the hub. Once with JS, click « Refresh » again until a « Remove » option appears.

3

I had to do the same last night. I have been replacing my Red Z-Wave's with Blue mmWave's and found even after excluding I had two ghosts that couldn't be deleted. I switched to the Zwave.js and they both deleted fine.

1 Like
4

That did the trick! Thank you!

2 Likes
5

One further point.
I have found that sometimes the device to be paired and the Hub must be in close proximity. I think it happens when there is a lot of data to be exchanged between the device and the Hub (e.g. a smart lock, or a zwave stick).
It appears as if it's "bootstrapping", but the pairing never finishes and often a ghost node is created.

1 Like