FAQ: Z-Wave Inclusion Problems

Modified on Fri, 14 Aug at 10:53 AM

TABLE OF CONTENTS


Q: Why can't I add the Shelly Wave device to a controller?

There are several common reasons why a Z-Wave device cannot be added to a controller: 

  • The controller may not support the device’s Z-Wave frequency
  • The device is already paired with another controller and must be excluded first.
  • The controller is too far from the device during inclusion.
  • The device is not in inclusion/pairing mode.
  • Low battery power can prevent the device from joining the network.
  • Network interference or firmware issues may also cause pairing problems.

Try:

  • Excluding the device

  • Factory reset if necessary

  • Moving the device closer to the controller

  • Check the battery

  • Start the inclusion process again


You may read the following article for more information.



Q: Why does my device stay on "Initializing" - "adding"?

This usually means the device interview did not complete successfully. Common causes include weak signal, secure inclusion problems, or heavy Z-Wave traffic.

Try:

  • Moving the device closer to the controller

  • Re-interviewing the device

  • Including without security



Q: Why is inclusion taking a very long time?

Long inclusion times can happen because of:

  • Weak signal quality

  • Busy Z-Wave networks

  • Battery-powered devices

  • Secure inclusion negotiation

Longer inclusion time does not always mean the process failed.


Q: Why are parameters or settings missing after inclusion?

  1. Missing parameters are often caused by an incomplete interview process.
    Try:
    • Re-interviewing the node

    • Reinitializing the device

    • Including the device closer to the controller

  2. In some cases, the device is included successfully, but the gateway or controller does not fully support all device features.
    • Missing parameters
    • Missing Command Classes
    • Missing configuration options
    • Missing sensor values
    • Missing controls or functions

More information about gateway integration.


Q: Should I use secure inclusion?

Secure inclusion is recommended when required, but it may cause problems on weak or busy networks.

If inclusion fails:

  • Try non-secure inclusion first

  • Move closer to the controller

  • Reduce network traffic


Q: Why does SmartStart keep trying to include my device?

This may happen if:

  • Old DSK entries remain stored

  • SmartStart information is incorrect

  • Previous failed inclusions were not removed

Try removing unused SmartStart entries and retrying manual inclusion.


Q: Can a device already included in another network be added again?

No. A device must first be excluded from the previous network before joining a new one. 

Always perform:

  1. Exclusion

  2. Factory reset if necessary

  3. New inclusion attempt



Note:
The Shelly Wave devices Green signal LED blinking (Violet blinking with the Wave Plug US) signalize that the device is already included or that the Home and Node ID was added during the previous inclusion attempt.


More about LED signalization


Q: Why does my battery device fail inclusion more often?

Battery devices are more sensitive to:

  • Weak signal quality

  • Long routing paths

  • Secure inclusion overhead

Recommendations:

  • Wake up the device manually

  • Include close to the controller

  • Use powered repeaters nearby


Q: Why does the device not appear at all during inclusion?

Possible causes include:

  • Frequency mismatch

  • Device already included elsewhere (green signal led blinking)

  • Device not in inclusion mode

  • Controller compatibility problems

Verify the controller and device regions match.


Q: What is a re-interview?

A re-interview forces the controller to rediscover the device capabilities, parameters, and supported Command Classes.

This often fixes:

  • Missing parameters

  • Missing controls

  • Incomplete device setup


Q: Does Z-Wave Long Range (LR) work on all controllers?

No. If the controller does not support Z-Wave Long Range, the device must use standard mesh inclusion instead.