Silicon Laboratories Z-Wave 800 Series User manual

QSG185: Z-Wave 800 Dev Kit
Thunderboard Quick Start Guide with
Unify
The Z-Wave 800 Thunderboard BRD2603A Radio Board is an excellent starting
point to get familiar with the ZGM230S Z-Wave 800 SiP Module. The board is a
small and cost-effective, feature-rich prototype and development platform based
on the ZGM230S SiP Module.
It has been designed to inspire customers to make energy-friendly, battery-oper-
ated and secure connected IoT devices using Z-Wave MESH and Z-Wave Long
Range protocols. Customers can develop wide range command, control, and
monitoring applications utilizing numerous sensors, buttons, and LEDs on this
board. A built-in SEGGER J-Link debugger ensures easy debugging using a
USB Type-C cable.
The Z-Wave 800 Dev Kit is supported in Simplicity Studio and it ships with Unify
SDK, a portable environment that works with any Z-Wave end device and pro-
vides a flying start, out-of-box experience for Z-Wave applications. This Quick
Start Guide describes the steps to get up and running quickly with the Dev Kit
with Unify environment. The portable runtime comes as an executable CLI, to-
gether with Unify, a docker-compose file, and a tool which can map a Silicon
Labs device with a docker environment on Windows, MacOS, or Linux.
KEY FEATURES
• ZGM230S Z-Wave SiP Module with 512 kB Flash,
64 kB RAM
• +14 dBm TX power
•SMA antenna connector (863-925 MHz)
• Advanced Energy Monitor
• Virtual COM port
• SEGGER J-Link on-board debugger
• RGB LED, two single color LEDs, and two push
buttons
• CR2032 coin cell battery support
• 20-pin 2.54 mm breakout pads
• Mini Simplicity connector
ON-BOARD SENSORS
• Relative humidity and temperature sensor
• Passive Infrared sensor
•Hall effect sensor
• Ambient light sensor
• Pressure sensor
• LESENSE LC-sensor
• 6-axis Inertial sensor
SOFTWARE SUPPORT
• Simplicity Studio
• Unify SDK Z-Wave Protocol Controller
REQUIRED COMPONENTS
• Two Z-Wave Thunderboard Kits pre-programmed
and labelled with "Z-Wave - NCP Serial API
Controller"
• USB-C cable for controller (not included)
•Optional coin cell battery for end device (not
included)
• Docker version > 20.10.12 installed.
• Docker-compose version > 2.5.1
silabs.com | Building a more connected world. Copyright © 2023 by Silicon Laboratories Rev. 0.7

1. Setting Up Your Z-Wave 800 Dev Kit
Step 1: Unboxing
1. Unbox Z-Wave 800 Dev Kit.
2. Connect the USB Type-C connector to the PC using the USB-C cable.
Step 2: Software Preparation
1. Download and install Docker Desktop:
•Windows - https://docs.docker.com/desktop/windows/install/
• MAC - https://docs.docker.com/desktop/mac/install/
• Linux - https://docs.docker.com/desktop/linux/install/
2. Download and unzip the Unify Portable Environment, which enables the Z-Wave demo by running sample applications on 800 Dev
Kit devices. This is a containerized Unify environment that can manage a Z-Wave controller, form a network with end devices, and
provide a way to try the features of the applications.
• Windows: http://www.silabs.com/documents/public/software/portable_runtime_windows.zip
• Linux: http://www.silabs.com/documents/public/software/portable_runtime_linux.zip
• Mac OS: http://www.silabs.com/documents/public/software/portable_runtime_macos.zip
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 2

Step 3: Flash Application
The development kit devices are shipped with the NCP Serial API Controller firmware by default. To try the demo, at least one control-
ler (SerialAPI) and one end device application is needed. Therefore, one of the devices must be re-programmed before first use. The
Unify Portable Runtime Environment package contains three built-in sample applications:
• SwitchOn/Off – End device application
• Multilevel Sensor – End device application
• SerialAPI – Controller NCP application
Follow these steps to flash the new application firmware to the dev kit:
1. Connect the device to the PC via USB-C cable.
2. Open a new terminal window in the unzipped Unify Portable Environment folder.
3. Run the command to flash SwitchOn/Off application:
unify_portable_cli.exe flash-app -n switch-on-off
or this command to flash the Multilevel Sensor application:
unify_portable_cli.exe flash-app -n multilevel-sensor
or this command to flash the Serial API Controller NCP application:
unify_portable_cli.exe flash-app -n serial-api
The environment performs some actions in the background, like resetting the device, flashing the new firmware, and setting the regional
radio frequency.
If there are multiple devices connected via USB, the J-Link Serial number must be provided in the command line interface. The device's
board number can be found printed on the bottom of the Thunderboard.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 3

Step 3.1: Read Device Specific Key
To perform a secure inclusion, it is necessary to provide the device specific key (DSK) of the end device. It can be read by running the
following command:
unify_portable_cli.exe read-dsk
Select the end device from the list. The board can be identified by its board number.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 4

Step 3.2: List Connected Devices
To get more information about the connected devices, run the following command:
unify_portable_cli.exe list-devices
The output contains the serialNumber and boardSerial of each device. The boardSerial is also printed on the back of the develop-
ment kit, next to the SMA antenna. The connected boards can be distinguished from each other by this number.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 5

Step 4: Start Unify Portable Environment
1. Connect only the Controller device (Dev Kit with the Z-Wave - NCP Serial API Controller firmware) to the PC.
2. Run unify_portable_cli.exe in a terminal inside folder where you have extracted the Unify Portable Environment. It will start the
environment with the default frequency for the EU region.
Note: You may need to run the executable from an elevated terminal.
3. If there are more devices connected via USB, the J-Link serial number must be provided for the executable:
unify_portable_cli.exe -s <SERIAL_NO>
4. The serial number of the devices can be identified based on Step 3.2 List Connected Devices.
5. Firewall access must be granted for the application, Docker, and USB connection.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 6

6. Allow Docker access to the required files (mosquito-config location) if prompted in the Action Center.
7. Launch the GUI in your browser using the URL http://localhost:3080.
8. Click the header at the top of the page to enter your credentials. Set the Host to mqtt-broker and the Port to 1883and click Con-
nect.
9. In the Node List, the Controller device should now appear.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 7

Step 5: Include the End Device in the Z-Wave Network
1. Power on the end device by connecting it via a USB-C cable or by inserting a battery.
2. In the Node list, click the States button on the right side of the Controller’s row and select Add Node from the drop-down list.
3. Activate inclusion mode on the end device by pressing the button labelled BTN1 on the Thunderboard.
4. Input the first five digits of the DSK key from the label in the pop-up window or click Reject to perform an insecure inclusion.
5. A popup warning message is displayed in the lower right corner when a non-secure inclusion is performed:
6. After a successful inclusion, the end device appears below the Controller row.
The icons under the Type category indicate the supported functionalities of the nodes.
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 8

Step 6: Try the Application
• For a "Z-Wave - SoC Switch On/Off" end device, the capabilities are as shown below:
• The capabilities of the connected node can be seen by clicking the icons:
• Clicking the On/Off icon navigates to a new view where the LED can be controlled on the Thunderboard:
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 9

• For the "Z-Wave - SoC Multilevel Sensor" end device, the capabilities are:
• The capabilities of the connected node can be seen by clicking the icons:
• Clicking the Thermostat button brings us to the window where the temperature value measured by the onboard thermostat can be
read out.
• In the Configuration window, a minimum and maximum temperature threshold can be set:
QSG185: Z-Wave 800 Dev Kit Thunderboard Quick Start Guide with Unify
Setting Up Your Z-Wave 800 Dev Kit
silabs.com | Building a more connected world. Rev. 0.7 | 10