Why Is Zooz Switch Not Excluding From Hub?
- Hub exclusion mode timing issue
- Device command sequence incorrect
- Network congestion
Problem Description
When your Zooz Zooz Exclusion Failures 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
- Exclude fails repeatedly
- Device remains in node list
- Inclusion blocked after failed exclude
Recognize these? Here's what usually causes it.
Common Causes
- Hub exclusion mode timing issue
- Device command sequence incorrect
- Network congestion
Most fixes happen in the first 3 steps.
Do not leave failed node entries after repeated exclusion attempts.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Start clean exclusion mode
Put hub in exclusion and trigger device sequence exactly per model.
Move closer to hub
Perform exclusion at strong RF range to improve reliability.
Clean failed nodes
Remove stale failed entries before new inclusion.
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.
Exclusion before inclusion avoids many S2 pairing failures.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- Hub exclusion mode timing issue
- Device command sequence incorrect
- Network congestion
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.
