Z-Wave Inclusion Timeouts: Secure vs Non-Secure and S2 Tips
Struggling with Z-Wave inclusion timeouts? This guide covers secure vs non-secure inclusion, S2 security tips, and troubleshooting steps to get your devices paired reliably.
Search results
Z-Wave inclusion timeouts are a common frustration for Home Assistant users. This guide explains the causes of timeouts, the difference between secure and non-secure inclusion, and provides practical tips for getting your devices paired reliably, especially with S2 security.
Quick Recommendations
- Bring the device close to the controller for inclusion.
- Use a USB extension cable for your Z-Wave stick.
- Increase the inclusion timeout in Z-Wave JS UI.
- Always exclude first, even for new devices.
Common Causes of Inclusion Timeouts
| Cause | Why it Happens | Solution |
|---|---|---|
| S2 Security Negotiation Failure | The controller and device fail to agree on security keys in time. | Increase timeout, bring device closer. |
| Distance/Range Issues | Inclusion often fails over the mesh; direct communication is needed. | Move device within a few feet of the controller. |
| USB Interference | The Z-Wave stick is too close to the host machine (e.g., Raspberry Pi). | Use a 3ft USB extension cable. |
| Firmware Bugs | Some 700/800 series controllers have known stability issues. | Update controller and device firmware. |
| Timing | Default timeouts are short, requiring frantic button presses. | Increase the inclusion timeout in Z-Wave JS UI. |
Secure (S2) vs. Non-Secure Inclusion
- S2 Security: The modern standard for Z‑Wave, offering strong encryption. It’s essential for security devices like locks and garage door openers. Inclusion requires entering a 5-digit Device Specific Key (DSK) or scanning a QR code.
- Non-Secure Inclusion: If S2 fails, the device may fall back to non-secure mode. For non-critical devices like light switches, this is often acceptable and can be more reliable.
Tips for Successful Inclusion
Proximity is Key: Always perform inclusion with the device physically close to the Z‑Wave controller. You can move it to its final location after it’s securely included.
Use a USB Extension Cable: A 3‑foot USB extension cable is a must‑have to move your Z‑Wave stick away from the host computer and reduce interference.
Increase the Timeout: In the Z‑Wave JS UI, go to
SETTINGS > Z‑WAVEand increase theInclusion/Exclusion timeoutto60or120seconds. This gives you more time for the S2 key exchange.Exclude First: Always perform an exclusion before inclusion, even for a brand new device. This acts as a soft reset and clears any old network information.
SmartStart (QR Code): If your device supports SmartStart, scan the QR code. Do not power on the device until prompted by the inclusion process.
Battery Power: For battery‑powered devices, always include them using battery power. Including them on USB power can cause them to be incorrectly identified as repeaters, leading to rapid battery drain.
Best Practices for a Healthy Z-Wave Network
- Controller Choice: Use a modern 800 series controller like the Zooz ZST39 LR or Home Assistant Connect ZWA-2 with the latest firmware.
- Z-Wave JS UI: Use the Z-Wave JS UI add-on for advanced features like NVM backup/restore, network mapping, and easy access to settings.
- Backup Your Keys: Always back up your S0 and S2 security keys. Without them, you’ll have to re-include all your devices if your controller fails.
Troubleshooting Failed Inclusions
- Check the Logs: Look for errors in the Z-Wave JS UI logs.
- Factory Reset: If exclusion doesn’t work, factory reset the device.
- Re-Interview Node: If a device includes but shows as ‘unknown’, try re-interviewing it from the Z-Wave JS UI.
By following these tips, you can significantly reduce Z-Wave inclusion timeouts and build a more reliable and secure smart home network.
Resources
Last modified December 16, 2025: Z-Wave Inclusion Timeouts: Secure vs Non-Secure and S2 Tips (cb5cc81)