Why Some Gateways Need Updates to Support New Shelly Wave Devices
Overview
Shelly Wave devices use the Z-Wave protocol. In many cases, a Z-Wave gateway can read the device information directly from the device firmware. If the gateway platform is designed to integrate devices based on the data provided by the device, new Shelly Wave devices can be added without waiting for a gateway firmware update. However, not all gateways use this integration method.
How Z-Wave device integration should work
A Z-Wave device stores important information in its firmware.
This information can include:
Manufacturer ID
Product Type ID & Product ID
Firmware Version
Supported (CC) command classes (and CC versions)
Role Type
Feature Classes
Security Schemes
Association Groups
Configuration parameters
When a Z-Wave gateway is programmed correctly, it can read this information from the device and use it for integration. With this method, the gateway does not need a special update for every new device model. The gateway can use the data already available in the device. This is the recommended and more flexible way to integrate Z-Wave devices.
Why some gateways need updates
Some gateways do not fully use the device information that is available from the Z-Wave device. Instead, they use their own custom integration method. Because of this, the gateway may need a firmware update or platform update before a new device is shown and controlled correctly. In some cases, more than one update may be needed before all device functions work as expected. This can cause delays for users, even when the Shelly Wave device itself is working correctly.
What we tested
We tested Shelly Wave devices with gateways that support integration based on the device data. On these gateways, the Shelly Wave devices worked correctly after they were added. This confirms that the required device information is already available in the Shelly Wave device firmware.
We have done everything possible from our side to make the devices compatible and ready for correct Z-Wave integration.
Why the gateway developer may need to help
If a gateway uses a custom integration method, Shelly cannot directly change how that gateway detects or displays devices. In this case, the gateway developer must add or improve support for the new Shelly Wave device in their platform. For this reason, we kindly recommend contacting the gateway developer or gateway support team and asking them to include support for the new Shelly Wave devices. This helps all users who use the same gateway platform.
What you can do
If your Shelly Wave device is included but does not show all functions correctly, please check the following:
Make sure the gateway firmware is up to date.
Check if the gateway already supports the specific Shelly Wave device model.
Contact the gateway developer and ask if support for the device can be added.
Check if the gateway supports Z-Wave device data-based integration.
Test the device with a gateway that is known to support Shelly Wave devices, if possible.
Helpful links
You may also find these articles useful:
Summary
Shelly Wave devices already include the needed Z-Wave information in the device firmware. Gateways that use this information correctly can integrate the devices without waiting for a special update. Some gateways use custom integration methods, so they may need additional firmware or platform updates. If your gateway does not fully support a Shelly Wave device yet, please contact the gateway developer and ask them to add support for the device.