Why Can't My Hubitat Find Z-Wave Devices?
- Device too far from the hub during inclusion
- Device not factory reset or excluded first
- S2 DSK not entered in time
Problem Description
Your Hubitat will not discover or include a Z-Wave device, it stays in inclusion mode and never finds the device, or the join fails partway. On Hubitat this is usually distance from the hub at inclusion, a device that was not factory reset or excluded first, or a security negotiation that times out.
Why This Happens in Real Homes
Z-Wave discovery failures on Hubitat are almost always distance, a device not reset first, or an S2 timeout, not a broken hub radio. In real homes people try to include a switch across the house, or re-add a device that was never excluded.
Factory reset or exclude first, include within a few feet of the hub, and enter the DSK promptly; remove any ghost node before trying again.
Symptoms
- Hub sits in inclusion and never finds the device
- Join starts then fails or times out
- Device includes with no driver
- Only includes right next to the hub
- S2 security prompt times out
- Previously paired device will not re-include
- Inclusion leaves a ghost node
- Intermittent discovery
Recognize these? Here's what usually causes it.
Common Causes
- Device too far from the hub during inclusion
- Device not factory reset or excluded first
- S2 DSK not entered in time
- Weak mesh route at join
- Interference during inclusion
- A prior ghost node blocking the join
- Wrong inclusion mode (S2 vs unsecure)
- Battery device asleep during pairing
Most fixes happen in the first 3 steps.
Z-Wave repair tool helps fix ghost devices - Settings > Z-Wave Details.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Start Z-Wave inclusion on the hub
In the Hubitat web interface, go to Devices > Add Device > Z-Wave. Click Start Z-Wave Inclusion. The hub begins listening for Z-Wave devices. For Z-Wave Plus devices (most devices made after 2016), the hub uses SmartStart or standard inclusion. Keep the hub in inclusion mode while you trigger pairing on the device.
Trigger pairing on the Z-Wave device
Each Z-Wave device has a specific inclusion procedure — usually pressing a button once or holding it for 3 seconds. For light switches (GE/Jasco, Zooz, Inovelli): press the up paddle or config button once. For locks (Schlage, Yale, Kwikset): follow the lock-specific add procedure from the lock menu. For sensors (Zooz, Ecolink): press the internal button or insert the battery. Check the device manual for the exact inclusion trigger.
Pair within range then move the device
Z-Wave pairing happens at a lower power level than normal communication. Pair the device within 10 feet of the hub if possible. For wired devices like light switches that cannot be moved, use the Z-Wave Include at the hub and walk to the switch to trigger pairing. If the switch is far from the hub, make sure there are other Z-Wave devices between them to create a mesh path. After pairing, the device can communicate at full power through the mesh.
Fix devices that do not discover
If the device does not appear after triggering inclusion: first run Z-Wave Exclusion (Settings > Z-Wave Details > Exclusion) and trigger the device — this clears any previous network association. Then try inclusion again. If the device was previously paired to another hub (SmartThings, Wink, another Hubitat), it must be excluded or factory reset first. Also check the Z-Wave frequency — the Hubitat hub must match the device frequency (US uses 908.42 MHz, EU uses 868.42 MHz).
Assign the correct driver after pairing
When a Z-Wave device pairs, Hubitat assigns a driver based on the device fingerprint. If the device works but is missing features (no dimmer control, no energy monitoring), the hub may have assigned a generic driver. Go to the device page, click the Type dropdown, and select a more specific driver. For Zooz switches, use the Zooz-specific driver. For GE/Jasco, use the GE driver. For Inovelli, use the Inovelli driver. After changing the driver, click Save then Configure to initialize all device parameters.
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.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.
- Device too far from the hub during inclusion
- Device not factory reset or excluded first
- S2 DSK not entered in time
- Weak mesh route at join
- Interference during inclusion
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Hubitat Elevation owners.
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Hubitat provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Hubitat Elevation.
Source: hubitat.com
Need More Help? Hubitat Support
Note: The contact information below connects you directly to Hubitat's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
