How to Fix Zooz Device Excluded but Ghost Node Remains
- Incomplete exclusion handshake
- controller cannot mark dead node
- stale route cache
Problem Description
After excluding a Zooz Z-Wave device, a ghost node remains in your hub's Z-Wave network — it shows as dead, unknown, or offline and cannot be controlled or removed through normal exclusion. Ghost nodes waste Z-Wave network resources and can slow down mesh routing by causing repeated failed communication attempts to a device that no longer exists.
Why This Happens in Real Homes
A ghost node is left behind when an exclusion or device removal did not finish cleanly, so the controller still lists a dead node it cannot reach. In real Z-Wave networks this follows a failed exclusion or a device that died mid-network. Use the hub's remove-failed-node tool or a Z-Wave repair to purge it, then heal the network so routes stop trying the dead node.
Symptoms
- Phantom node in topology
- route instability after exclusion
- inclusion errors on new device
Recognize these? Here's what usually causes it.
Common Causes
- Incomplete exclusion handshake
- controller cannot mark dead node
- stale route cache
Most fixes happen in the first 3 steps.
Do not start new inclusion attempts before ghost-node cleanup is complete.
Tools & Requirements
Step-by-Step Solution
Identify the ghost node in your Z-Wave network
A ghost node appears when a device is physically removed or excluded but its node ID remains in the hub's Z-Wave network table. In Home Assistant Z-Wave JS: go to Settings > Devices > Z-Wave JS > the node shows as 'Dead' or 'Unknown' with no manufacturer info. In Hubitat: the device page shows 'UNKNOWN' for device type. In SmartThings: the device appears as offline with no controls. The ghost node wastes Z-Wave network resources and can slow down the entire mesh by causing repeated failed routing attempts.
Try removing the ghost node through the hub UI
In Z-Wave JS (Home Assistant): click the dead node > click Remove Failed Node. The hub sends a 'Remove Failed Node' command to the Z-Wave controller. This works if the controller has already marked the node as failed. If the button is grayed out or returns an error: the controller does not consider the node failed yet. In Hubitat: go to Settings > Z-Wave Details, find the ghost node, and click Remove. If Remove fails: click Repair on the ghost node first (it will fail), wait 30 seconds, then try Remove again — the failed repair marks it as failed.
Force-remove using the Z-Wave controller directly
If the hub UI cannot remove the ghost: access the Z-Wave controller directly. For Z-Wave JS: open the Z-Wave JS UI (usually port 8091), go to Control Panel > Nodes, select the ghost node, and click 'Remove Failed Node'. For a Zooz ZST39 or ZST10 controller stick: this is the same process. If using the Silicon Labs UZB-7 stick: you can use the PC Controller software from Silabs to directly issue the Remove Failed Node command. This bypasses the hub's abstraction layer and talks directly to the Z-Wave chip.
Power cycle the Z-Wave controller stick
If Remove Failed Node still fails: power cycle the Z-Wave controller. Shut down Home Assistant/Hubitat completely. Unplug the Z-Wave USB stick (ZST39, ZST10, UZB-7). Wait 30 seconds. Plug it back in. Start the hub software. The controller re-initializes its node table — ghost nodes that were in an inconsistent state may now be removable. Try Remove Failed Node again after the controller fully initializes (wait 2-3 minutes after startup for the Z-Wave network to settle).
Re-include the physical device to clear the ghost
If the original Zooz device still exists (just excluded improperly): factory reset it (hold the paddle/button for 20+ seconds until the LED blinks), then re-include it with the same hub. During inclusion: the controller may recognize the old node ID and overwrite the ghost entry. If it assigns a new node ID instead: you now have both a ghost and a new node. Remove the ghost using the steps above (it should be removable now that a new inclusion succeeded), then reconfigure automations to use the new node ID.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Ghost-node hygiene prevents long-tail mesh instability.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Incomplete exclusion handshake
- controller cannot mark dead node
- stale route cache
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Zooz provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Zooz Ghost Node Cleanup.
Source: help.zwaveproducts.com
Need More Help? Zooz Support
Note: The contact information below connects you directly to Zooz's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Zooz Ghost Node Cleanup.
Zooz 800 Series Z-Wave Long Range S2 Motion Sensor ZSE18 ...
Zooz 800 Series Z-Wave Long Range Open|Close XS Sensor ZS...
Zooz 800 Series Z-Wave Long Range Temperature | Humidity ...
As an Amazon Associate we earn from qualifying purchases.
