Skip to content

ZPC Version 2.0.0 - Release Notes (Aug 3, 2026)

ZPC is a Linux/macOS-based Z-Wave gateway application that functions as a central static controller in Z-Wave networks. It provides the host-side functionality of the Z-Wave Controller and interacts with the Z-Wave network through the Silicon Labs Network Co-Processor (NCP) controller. As a static controller, ZPC remains continuously powered and acts as the primary hub for managing and coordinating communication among all Z-Wave devices in a smart home network. ZPC provides network management, device control, and state synchronization capabilities through an MQTT-based communication interface.

Note: This project is currently in beta and implements a focused subset of Z-Wave functionality for demonstration and development. This is the first public beta release of this project. Legacy ZPC releases with the same product name are available in a separate z-wave-protocol-controller-legacy repository. Legacy versions implement different APIs that are not compatible with this project.

Release Summary

Key Features | API Changes | Bug Fixes | Chip Enablement

Key Features

  • MQTT-based APIs for discovery, network management, SmartStart, device interview, network status, OTA firmware updates, and Command Class control.
  • Persistent attribute store with reported/desired value synchronization for Z-Wave device state.
  • Build, packaging, Docker, and documentation support for development and evaluation.

API Changes

  • Initial MQTT API for Z-Wave network management, OTA firmware updates, and Command Class control.

Bug Fixes

None.

Chip Enablement

Hardware and software used in verification and certification tests:

Component Hardware Firmware version
ZPC Raspberry Pi 4 Model B v2.0.0
NCP Controller BRD4001A WSTK + BRD4205B radio board Simplicity SDK 2025.12.3
End Device BRD4001A WSTK + BRD4205B radio board Simplicity SDK 2025.12.3

Key Features

New Features | Enhancements | Removed Features | Deprecated Features

New Features

Enhancements

None.

Removed Features

None.

Deprecated Features

None.

API Changes

New APIs | Modified APIs | Removed APIs | Deprecated APIs

New APIs

New API Deprecated API replaced by this (if any)
See MQTT API Index None

Modified APIs

None.

Removed APIs

None.

Deprecated APIs

None.

Bug Fixes

None.

Chip Enablement

Hardware and software used in verification and certification tests:

Component Hardware Firmware version
ZPC Raspberry Pi 4 Model B v2.0.0
NCP Controller BRD4001A WSTK + BRD4205B radio board Simplicity SDK 2025.12.3
End Device BRD4001A WSTK + BRD4205B radio board Simplicity SDK 2025.12.3

Application Example Changes

New Examples | Modified Examples | Removed Examples | Deprecated Examples

New Examples

None.

Modified Examples

None.

Removed Examples

None.

Deprecated Examples

None.

Known Issues and Limitations

Known Certification Issues | Workarounds

ID Issue or Limitation Description GitHub / Salesforce Reference (if any) Workaround (if any) Affected Software Variants, Hardware, Modes, Host Interfaces
S2 secure inclusion may fail when secured communication from another node occurs during the S2 key exchange phase, resulting in non-secure or failing inclusion. None None All
In classic networks, `normal_tx_power_dbm` values over 127 result in a lower value being used, reducing the range. None In classic networks, do not set `normal_tx_power_dbm` to a value over 127. All
For non-authenticated inclusions (S2 Unauthenticated, S0, and non-secure), ZPC reports an invalid DSK in the `Node Add` and `Node Remove` MQTT reports. None None All
The `Network/Node/Add/Abort` command has no effect while Network Management is in the `NM_WAIT_FOR_PROTOCOL` state, so network operations are blocked until the currently running operation finishes. None None All
If the NCP Controller loses power, ZPC may not handle the connection loss. None If a power loss of the NCP Controller is detected, stop and restart the ZPC application once power is restored. All
ZPC will try to ping an already removed node when the 'Remove Failed' command is issued multiple times on the same node. None None All
In Long Range networks, issuing the 'Remove Failed' command on a node that is already removed may result in ZPC sending incorrect MQTT status reports. None None All
The automatic interview process does not query the supported events of nodes supporting Notification Command Class. None Manually send Event Supported Get commands to each notification type. All
If security keys are not granted or the DSK is not accepted by the user during inclusion, ZPC fails to send an Add Report or Interview Report through MQTT. None None All
When a user answers `RequestedKeys/Report` with a `DSK/Accept` MQTT command and issues it again after `RequestedDSK/Report`, ZPC grants all requested keys. None None All
ZPC does not clear retained MQTT messages of removed nodes' Command Class states. None None All
The following documented MQTT commands are not implemented: `MultiChannelCmdEncap`, `MultiInstanceCmdEncap`, `MultiInstanceGet`, `AssociationSpecificGroupGet`, `ThermostatSetpointReport`, `ThermostatSetpointSupportedReport`, and `ThermostatSetpointCapabilitiesReport`. None None All
[Certification issues](#known-certification-issues) None None All

Known Certification Issues

This release was tested with CTT. The list of known test failures is available in the known_failing_ctt_test_cases.md file.

Certification issues will be addressed in future releases as soon as possible.

Workarounds

None.

Impact of Release Changes

Impact Statements | Migration Guide

Impact Statements

This is the first public release of this project. Legacy ZPC releases from the z-wave-protocol-controller-legacy repository are not compatible with this release.

Migration Guide

None. This is the first public release of this project. Legacy ZPC releases from the z-wave-protocol-controller-legacy repository are not compatible with this release.

Documentation Changes

Initial ZPC documentation is included in the README.md in the repository root or in the docs/README.md file.

Using This Release

Installation and Use | Help and Feedback

Installation and Use

To build and run ZPC, see the Getting Started guide.

To see the full documentation for ZPC, see the README.md file in the docs folder.

Help and Feedback