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
S2 security inclusion for a Zooz Z-Wave device fails with a security negotiation error, timeout, or falls back to no security. S2 Authenticated inclusion requires a factory-reset device, the correct 5-digit DSK code, a compatible Z-Wave controller, and current hub/device firmware.
Why This Happens in Real Homes
S2 secure inclusion needs a factory-reset device, the correct DSK, and a strong route, so a security error is usually a stale prior pairing or including too far from the hub. In real networks a half-removed old node blocks the join. Factory-reset the device, remove any failed node, and include it within a few feet of the hub.
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
Factory reset the Zooz device before inclusion
S2 inclusion requires a clean security state. If the device was previously paired to another hub or had a failed inclusion attempt: leftover security keys cause inclusion failures. Factory reset the Zooz switch: for ZEN7x series, press and hold the upper paddle for 20+ seconds until the LED flashes rapidly. For the ZEN34 remote: press and hold any button for 20 seconds. After the reset: the LED confirms with a pattern (varies by model). The device is now ready for fresh S2 inclusion with no residual security state.
Enter the 5-digit DSK code during inclusion
S2 Authenticated inclusion requires a 5-digit PIN derived from the device's DSK (Device Specific Key). The full DSK is printed on the switch's label (inside the faceplate) or on the packaging. Your hub will prompt for the first 5 digits of the DSK during inclusion. In Home Assistant Z-Wave JS: a dialog box appears — enter the 5 digits. In Hubitat: the inclusion page shows a PIN field. If you skip the DSK entry: inclusion falls back to S2 Unauthenticated or no security (S0/none). Entering the wrong PIN causes the inclusion to fail with a security error.

Needed for this step
Zooz 800 Series Z-Wave Long Range DC Signal Sen...
This helps complete the fix you are currently reading.
$44.95Exclude the device before re-including
If inclusion fails partway through: the hub may have a partial entry for the device that blocks a fresh inclusion. Run exclusion first: put the hub in exclusion mode, then tap the Zooz switch paddle once (for ZEN7x) or the button (for ZEN34). The hub should confirm exclusion. If exclusion says 'unknown device excluded': that is fine — it cleared any partial state. Now start fresh: put the hub in inclusion mode with S2 security, then tap the switch paddle to begin inclusion. Enter the DSK when prompted.
Check hub Z-Wave controller compatibility
S2 security requires a Z-Wave controller that supports the S2 protocol. Older Z-Wave controllers (pre-700 series) may not support S2 properly. Check your controller: Zooz ZST39 (800 series) and ZST10 (700 series) fully support S2. Silicon Labs UZB-7 supports S2. Aeotec Z-Stick Gen5 (500 series) has limited S2 support and may fail. In Z-Wave JS: the controller's chip type is shown in Settings > Z-Wave. If your controller does not support S2: you can still include the device without security (or with S0), but S2 features (Central Scene encryption, secure parameter access) will not work.
Update hub firmware and Z-Wave driver
S2 inclusion bugs have been fixed in recent Z-Wave JS updates. In Home Assistant: update the Z-Wave JS add-on to the latest version (Settings > Add-ons > Z-Wave JS > Update). In Hubitat: update to the latest platform firmware (Settings > Firmware Update). Zooz also releases firmware updates that improve S2 compatibility — check getzooz.com/firmware for your model. After updating both the hub software and device firmware: factory reset the Zooz device and attempt S2 inclusion again with the DSK ready.
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).
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 S2 Inclusion.
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 S2 Inclusion.

Amazon Smart Plug, Works with Alexa, Simple Setup, Endles...

Sengled Smart Light Bulbs, Color Changing Alexa/Bluetooth...

Sengled Alexa Light Bulb, S1 Auto Pairing with Alexa Devi...
As an Amazon Associate we earn from qualifying purchases.




