The Z-Wave module allows you to manage Z-Wave networks either directly using the Z-Wave API, or through the abstraction layer provided by Device Access (DA). The module comes in two varieties:
Z/IP Gateway-based - the Z-Wave Plus V2 version of the module introduced in Bosch IoT Gateway Software 10.0 It includes features such as the Z-Wave’s S2 Security and Z-Wave SmartStartbased on the Z-Wave over IP (Z/IP) specification which describes the standard for transporting Z-Wave messages over IP networks.
Serial API-based - the Z-Wave Plus stack implementation is based on Serial API chip communication defined by the physical layer. This version of the module is now deprecated.
Feature Set
The Z-Wave module provides:
Polling mechanism, message routing and statistics
Support for many new Z-Wave command classes
Integrated with the Peripheral module for easier setup
Backup and restore of device data
Support for Z-Wave and Z-Wave Plus certified devices
Flexibility - 3rd-parties can develop their custom device extensions that can match the target device via a wide range of criteria, e.g. vendor, type, model, application and firmware versions, command classes, etc.
Out-of-the-box experience
Z-Wave Plus V2 Features (Z/IP Gateway-based)
Z-Wave SmartStart - device recognition and inclusion can now be automatic through the gateway, or through a quick scan of a QR code, for efficient and consistent installation success with zero errors.
Z-Wave’s S2 Security - with S2, Z-Wave completely eliminates the vulnerability of the network during device inclusion by way of PIN codes and an industry-standard secure key exchange.
Deprecation Alert Starting with version 10.0 of Bosch IoT Gateway Software, theserial-based Z-Wave Plus stack gets deprecated.
Migrating from a Serial API to a Z/IP Gateway-based solution is impacted by the chip's firmware version, static or bridge firmware type, network security level, etc. Any migrations should be undertaken on a case by case basis, or consider upgrading your solution entirely to the Z/IP Gateway-based version to take advantage of all new features.
Supported Devices
Certified Devices - the Z-Wave module provides support for all Z-Wave-certified devices, with a subset of features as described in the feature set above.
Tested Devices - a number of devices is fully tested with the latest release of the Bosch IoT Gateway software stack.
For a most up-to-date list of actual tested and certified devices, visit Supported Devices.
Known Issues and Limitations
Device representation in HDM has the following known issues:
If only one type is supported by MulitLevel CC and Thermostat Setpoint CC – the according DC instance will be represented in a child HomeDevice instance. In comparison to previous versions of 4.2.x and 4.4.x, where if only one type is supported – the according DC is registered in the root HomeDevice instance and child instances are created only if the supported types are more than one.
If the device supports Alarm CC Version 1 – the according DC is registered in the root HomeDevice instance. In comparison to previous versions of 4.2.x and 4.4.x, where the according DC instance will be represented in a child HomeDevice instance with a Z-Wave-specific property zwave.cc.spec.type set to a system value of 0.
For all other cases – the HDM device representation is fully backward compatible.
It is possible an application data exchange attempts to be made by the controller after a Wake Up No More Information is sent to a device.
Restoring a 7.5.x Z-Wave backup has a potential problem when performed over 9.x.x due to a problem with legacy HomeDeviceSpis UIDs support.
While using the ZIP Gateway based driver, DA and HDM devices stay online even if they are not accessible in the network anymore.
Module Dependencies
The module has dependencies on the following:
OSGi Framework: The OSGi Runtime is required for the module to operate.
Device Access: Optional, but required to abstract the Z-Wave device protocol from your runtime.
Regulations and Certification
Any product or solution based on the Z-Wave technology must undergo a Z-Wave Plus or Z-Wave Plus V2 certification at a test house approved by the Z-Wave Alliance. Please find the official statement from Silicon Labs here https://www.silabs.com/wireless/z-wave/certification. This is equally applicable to typical smart home gateways (e.g. running the Z-Wave module or other similar middleware), as it is to end devices and Z-Wave hardware.
Any customer intending to use the Z-Wave stack implementation of Bosch IoT Gateway Software must respectively undergo a separate certification and must contact us as soon as possible, as the procedure is specific and requires additional technical attention in order to be successful. Although it supports the main features of the standard, our Plus V2 implementation currently does not cover all certification requirements. They are being developed and are scheduled for the upcoming maintenance releases.
Z-Wave certification encompasses a wide range of requirements starting from low-level Z-Wave network behavior of the system, up to the middleware functionality, and ultimately the user interface. There is no restriction about the visuals, as long as the minimum information and operations are presented in the UI, so that a customer can buy any certified Z-Wave device, pair it and use it with your system.
Separate certifications are required for systems using different frequencies, meaning that EU and US based Z-Wave solutions need explicit dedicated certification, even though the UI and the and middleware might be the same.
For more information about the Z-Wave certification process please contact the Bosch.IO Support team or the Z-Wave Alliance directly.
Licensing Information
Check the Z-Wave section in the Third-Party Licenses.
* Z-Wave and Z-Wave Plus are registered trademarks of Silicon Laboratories and its subsidiaries in the United States and other countries.
