Overview

Some users may experience issues while adding Z-Wave devices to their controller/gateway, including:

• Inclusion failing completely

• Inclusion hanging during the process

• Devices appearing partially included

• Missing parameters or Command Classes

• Extremely slow inclusion

• Interview process never completing

This article explains the most common causes of inclusion problems and provides recommended troubleshooting steps based on real-world support cases.

Common Symptoms

Typical Inclusion Problems

Users may experience one or more of the following:

• Device stays on “Initializing”

• Inclusion never completes

• Interview process hangs

• Device appears without parameters

• Device includes but does not function correctly

• Secure inclusion fails

• Device reports incomplete information

• Missing configuration settings

• Missing Command Classes

• Inclusion takes several minutes

• Device repeatedly retries inclusion

Most Common Causes

1. Weak Signal During Inclusion

The most common cause of failed or incomplete inclusion is weak signal quality during the initial interview process.

During inclusion, the controller and the device exchange:

• Security information

• Supported Command Classes

• Parameters

• Association data

• Routing information

If packets are lost during this process:

• The interview may fail

• Features may be missing

• Parameters may not appear

• Inclusion may hang indefinitely

Recommended Solution

Always include devices:

• Very close to the controller

• Preferably within a few feet/meters

• Away from metal obstacles

Help: Troubleshooting week signal.

2. Busy Z-Wave Network

A heavily loaded Z-Wave network can delay or interrupt inclusion.

Z-Wave devices share the same RF network and excessive traffic may:

• Delay secure key exchange

• Interrupt interviews

• Cause timeouts

• Increase retries

Recommended Solution

Try inclusion:

• During low traffic periods

• At night if possible

• When automations are less active

3. Secure Inclusion Problems (S0 / S2)

Secure inclusion adds additional communication overhead and may fail on some setups.

This is especially common with:

• Weak signals

• Older controllers

• Busy networks

• Battery devices

• Certain controller firmware versions

Symptoms

• Inclusion hangs

• Device partially includes

• Missing parameters

• Device appears dead after inclusion

Recommended Solution

Try including the device:

• Without security

• Using normal mesh inclusion

• Close to the controller

In many cases, non-secure inclusion resolves the issue immediately.

4. SmartStart Problems

SmartStart inclusion can sometimes fail if:

• Unknown DSK entries exist

• Previous failed inclusions remain stored

• Another device is sending SmartStart requests

• The wrong DSK is registered

Symptoms

• Endless inclusion attempts

• Unexpected SmartStart popups

• Inclusion loops

• Device never completes setup

Recommended Solution

1. Temporarily disable SmartStart

2. Remove unknown DSK entries

3. Retry normal inclusion manually

Help: Verify the DSK.

5. Incomplete Device Interview

Sometimes the device includes successfully but the initial interview does not complete properly.

This may result in:

• Missing parameters

• Missing Command Classes

• Missing controls

• Incorrect device behavior

Common Controllers Where This Was Observed

• Homee

• SmartThings

• Alarm.com

• Some Z-Wave JS setups

Recommended Solution

Perform a:

• Re-interview

• Reinitialize

• Node refresh

This forces the controller to repeat the initial capability discovery.

6. Frequency Mismatch

Z-Wave devices must match the controller region.

Examples:

• US device ↔ US controller

• EU device ↔ EU controller

If regions differ:

• Inclusion will fail completely

Symptoms

• No inclusion response

• Device never appears

• No communication at all

Recommended Solution

Verify:

• Device region

• Controller region

• Product label

7. Controller Compatibility Issues

Some controllers may have limitations or compatibility issues with certain Z-Wave features.

Examples observed:

• Ring controller routing limitations

• ZWA-2 battery device issues

• SmartThings slower inclusion behavior

• Homee parameter visibility limitations

Important Note

Most inclusion issues are not hardware failures but interoperability or interview problems.

8. Long Range (LR) vs Mesh Confusion

Some users attempt to include LR-capable devices using unsupported modes.

Important

If your controller does not support:

• Z-Wave Long Range (LR)

then the device must be included using:

• Standard Mesh inclusion

Symptoms

• Inclusion hangs

• Device not detected properly

• LR inclusion failure

9. Devices Already Included

A device already included in another network cannot join a new network.

Recommended Solution

Always:

1. Exclude the device first

2. Factory reset if needed

3. Retry inclusion

Even brand-new devices may require exclusion if they were included during factory testing.

Help: Device have already assigned the Home ID

Recommended Inclusion Best Practices

Recommended Procedure

Step 1 – Reset/Exclude Device

Always start with:

• Exclusion

• Factory reset if necessary

Step 2 – Move Close to Controller

Include devices:

• Next to the controller

• With minimal obstacles

Step 3 – Avoid Secure Inclusion Initially

If problems occur:

• Try non-secure inclusion first

Step 4 – Reduce Network Traffic

Perform inclusion:

• During quiet network periods

• With fewer active automations

Step 5 – Complete the Interview

After inclusion:

• Wait for full interview completion

• Do not unplug the device immediately

Step 6 – Re-Interview if Needed

If parameters/features are missing:

• Perform re-interview

• Reinitialize the node

Special Notes for Battery Devices

Battery-powered devices are more sensitive to:

• Weak signal

• Routing quality

• Secure inclusion overhead

Recommendations

• Wake up the device manually during inclusion

• Use nearby powered repeaters

• Avoid long routing paths

Why Inclusion Sometimes Takes a Long Time

Z-Wave inclusion speed depends on:

• Signal quality

• Security level

• Network traffic

• Number of supported Command Classes

• Controller performance

Some controllers naturally take longer:

• SmartThings may take up to a minute

• Battery devices may require retries

• Secure inclusion adds additional negotiation steps

Longer inclusion time does not always indicate failure.

Common Troubleshooting Workflow

Standard Troubleshooting Procedure

1. Exclude device

2. Factory reset

3. Move close to controller

4. Retry inclusion without security

5. Wait for interview completion

6. Perform re-interview if needed

7. Check controller logs

8. Verify matching Z-Wave regions

When to Contact Support

Please contact support if:

• Inclusion always fails

• Device never appears

• Device interview never completes

• Parameters remain missing after re-interview

• Device cannot enter inclusion mode

Please provide:

• Controller model

• Controller firmware version

• Device firmware version

• Inclusion method used

• Whether secure inclusion was enabled

• LED behavior during inclusion

• Logs/screenshots if available

Summary

Most Z-Wave inclusion issues are caused by:

• Weak signal during inclusion

• Secure inclusion problems

• Busy Z-Wave networks

• Incomplete interviews

• SmartStart conflicts

• Frequency mismatches

The majority of issues can be resolved by:

• Including close to the controller

• Avoiding secure inclusion during troubleshooting

• Re-interviewing the device

• Performing inclusion during low network traffic

• Verifying controller compatibility