How to Fix Zooz Device Excluded but Ghost Node Remains
- Incomplete exclusion handshake
- controller cannot mark dead node
- stale route cache
Problem Description
When your Zooz Zooz Ghost Node Cleanup isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
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
Confirm removed device is offline
Ensure original node cannot respond during failed-node removal.
Run controller failed-node removal
Use platform tools to force ghost cleanup.
Repair local mesh routes
Stabilize affected neighbor paths after node deletion.
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).
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.
