How to Fix Zooz Switch Not Including With S2 Security
- Device not excluded before re-inclusion
- Weak mesh route during secure join
- S2 key prompt not completed in time
Problem Description
Your Zooz switch fails inclusion when S2 security negotiation starts. The hub may time out or show partial inclusion. This is usually caused by stale pairing state, weak mesh route at inclusion time, hub-side S2 prompt timing, or outdated firmware on switch or controller.
Symptoms
- Inclusion starts then fails at security step
- Hub shows ghost device after pairing attempt
- Switch appears but does not respond
- Inclusion only works close to hub
- S2 dialog times out during setup
- Exclusion reports success but inclusion still fails
Recognize these? Here's what usually causes it.
Common Causes
- Device not excluded before re-inclusion
- Weak mesh route during secure join
- S2 key prompt not completed in time
- Hub firmware S2 handling bug
- Switch firmware outdated
- RF interference near switch location
Most fixes happen in the first 3 steps.
Do not leave ghost nodes in your hub after failed secure inclusion. Ghosts degrade routing and cause future join failures.
Tools & Requirements
Step-by-Step Solution
Force clean exclusion first
Run Z-Wave exclusion from your hub and trigger the Zooz inclusion/exclusion action on the switch. Even brand-new devices can carry stale pairing state. Inclusion failures often disappear once exclusion completes and the switch starts from a truly unpaired condition.
Include with strong RF path
Perform first inclusion with the switch close to the hub or using a temporary powered setup point. Secure S2 negotiation is more sensitive to weak mesh conditions than basic joins. Once included reliably, move the switch back and heal the network.
Handle S2 prompt correctly
When the hub prompts for security keys or DSK confirmation, complete it immediately. Delays or accidental cancellation can create half-included nodes. If the attempt fails, remove any ghost entry in the hub before trying again to avoid repeated failed negotiations.
Update firmware on both sides
Check hub and Zooz device firmware for current stable releases. S2 inclusion behavior has improved over many platform updates, and mismatched old firmware often causes avoidable negotiation errors. Update first, then retry inclusion from a clean state.
Heal mesh and validate control
After successful inclusion, run Z-Wave repair/heal where supported and test on/off and scene events from normal mounting location. Confirm no delayed or missed commands. If reliability drops only after relocating the switch, add/optimize nearby repeaters.
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.
Keep one known-good powered repeater near high-problem inclusion areas to improve secure join reliability for future devices.
Range tests in open air are useless for predicting real-world Z-Wave performance — a single concrete wall or appliance can cut effective range by more than half.
- Device not excluded before re-inclusion
- Weak mesh route during secure join
- S2 key prompt not completed in time
- Hub firmware S2 handling bug
- Switch firmware outdated
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Zooz Z-Wave Smart Switch owners.
As an Amazon Associate we earn from qualifying purchases.
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.
