How Do I Remove a Z-Wave Ghost Node from Hubitat?
- Pairing that failed partway (secure join dropped)
- Device removed without a clean exclusion
- Controller could not mark the node dead
Problem Description
Your Hubitat Z-Wave network shows a ghost node, a device entry that is dead, unknown, or has no driver, usually left behind by a pairing that failed partway or a device removed without a clean exclusion. Ghost nodes waste network slots and can degrade routing for healthy devices until they are removed.
Why This Happens in Real Homes
Ghost nodes come from pairings that did not finish cleanly, and they quietly hurt routing until removed. In real Hubitat networks powering off the original device first makes removal succeed, because the controller can then mark the node dead.
Use Z-Wave Details, Refresh then Remove with the device unpowered, and run a repair afterward; re-pair the device close to the hub for a clean join.
Symptoms
- A Z-Wave device entry shows no driver or as dead
- A node appears that you cannot control
- Routing or speed degraded for nearby devices
- Left behind after a failed pairing
- Cannot remove it through normal exclusion
- Shows as unknown in the Z-Wave details
- Z-Wave repairs stall on it
- Network feels less reliable since it appeared
Recognize these? Here's what usually causes it.
Common Causes
- Pairing that failed partway (secure join dropped)
- Device removed without a clean exclusion
- Controller could not mark the node dead
- Weak route at inclusion time
- Device powered off during pairing
- Stale route cache referencing the node
- Interference during the join
- Battery device that never fully joined
Most fixes happen in the first 3 steps.
Do not factory reset your hub unless absolutely necessary as this removes all paired devices, automations, and settings. You will need to re-pair every single device from scratch which can take hours for a large setup. Always try a simple restart first.
Tools & Requirements
Step-by-Step Solution
Identify ghost nodes in the Z-Wave details page
Go to Settings > Z-Wave Details in the Hubitat web interface. This page lists every Z-Wave device on your network with its node ID, device name, route, and status. Ghost nodes appear as entries with no device name or a generic name like Device, with blank or incomplete route information, and no clusters listed. They are leftover entries from devices that were factory reset without being excluded, devices that failed during pairing, or devices that were physically removed without being properly removed from the hub.
Why ghost nodes cause problems
Ghost nodes degrade your entire Z-Wave mesh. The hub and neighboring devices continuously try to communicate with the ghost, sending route discovery requests and waiting for responses that never come. This creates delays for all Z-Wave commands — you will notice lights responding slowly, locks taking 3-5 seconds to react, and sensors reporting late. A single ghost node can slow your entire Z-Wave network. Multiple ghosts can make the system nearly unusable.
Remove ghost nodes using the Z-Wave details page
On the Z-Wave Details page, find the ghost node and click Refresh. Wait 30-60 seconds. The Refresh forces the hub to query the node — since the ghost does not respond, the hub marks it as failed. After the Refresh completes (check the Logs page for confirmation), a Remove button appears next to the node. Click Remove. The hub sends a Z-Wave Remove Failed Node command, clearing the ghost from the network. Repeat for each ghost.
Fix ghost nodes that will not remove
Sometimes clicking Remove fails with an error because the hub does not consider the node truly failed. Try this sequence: click Refresh, wait 60 seconds, click Refresh again, wait 60 seconds, then click Remove. If that does not work, shut down the hub (Settings > Shut Down), unplug the power for 30 seconds, plug it back in, and immediately try the Remove sequence again. For the most stubborn ghosts, try at a time when other Z-Wave devices are quiet (late at night) to reduce network congestion during the removal attempt.
Prevent ghost nodes in the future
Always exclude a device before removing it physically. Go to Settings > Z-Wave Details > Z-Wave Exclude, then trigger the exclusion on the device (usually a button press sequence). This properly removes the device from the network table. If a pairing attempt fails midway, immediately run an exclusion to clean up the partial entry before trying to pair again. When replacing a device, exclude the old one first, then include the new one.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the hub reconnects then drops every few minutes, check for an IP conflict — two devices sharing the same DHCP address fight each other continuously.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- Pairing that failed partway (secure join dropped)
- Device removed without a clean exclusion
- Controller could not mark the node dead
- Weak route at inclusion time
- Device powered off during pairing
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Hubitat Elevation owners.
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Hubitat provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Hubitat Elevation.
Source: hubitat.com
Need More Help? Hubitat Support
Note: The contact information below connects you directly to Hubitat's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
