How to Fix Zooz S2 Inclusion Failing with Security Errors
- Old failed node not removed
- Controller security state mismatch
- Inclusion started too far from hub
Problem Description
When your Zooz Zooz S2 Inclusion 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
- Inclusion fails at final step
- Security key mismatch
- Falls back to non-secure join
Recognize these? Here's what usually causes it.
Common Causes
- Old failed node not removed
- Controller security state mismatch
- Inclusion started too far from hub
Most fixes happen in the first 3 steps.
Do not leave failed secure attempts in the mesh before retrying.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Clean failed joins
Delete failed or ghost node records before retrying S2 inclusion.
Start fresh secure join
Factory reset device and restart inclusion from controller.
Verify secure completion
Confirm device joined with expected security class and stable control.
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.
Document secure-inclusion outcomes to avoid repeated ghost-node issues.
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.
- Old failed node not removed
- Controller security state mismatch
- Inclusion started too far from hub
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.
