- Full control for Configuration Command Class, version 4
- Added generated OnOff cluster commands for nodes issuing Basic Set commands to the ZPC.
-
Changed configuration keys for OTA config, if these have been specified in the ZPC config file, they need to be updated to the new keys manually
- Changed
zpc.ota_chache_path
tozpc.ota.cache_path
- Changed
zpc.ota_chache_size
tozpc.ota.cache_size
- Changed
-
Default get retry timer is lowered to 3s instead of 20s to mitigate against Wake Up nodes falling asleep during node interviews.
- ZPC gets stuck at reset in some rare cases.
- ZPC stops controlling OnOff if Binary Switch Set without supervision failed.
- ZPC stops granting S2 keys in some cases after a reset.
- ZPC does not let Iot Services control/remove a node after SmartStart self-destruct failure.
- ZPC consider Wake Up node failings if they fell asleep while communicating with them
- Re-interview a Wake Up leads to a difficult to recover situation
- Not all MQTT publications unretained after a node exclusion.
- S2 DSK of the previous node saved again with the next node if it does not support S2.
-
Partial Control for Central Scene Command Class
- Populating Scene Attributes to reflect the node's capabilities (total number of scenes)
- Central Scene is mapped to the Scene Cluster.
-
Issuing Generated Commands based on interaction with Z-Wave nodes
- Issuing RecallScene when receiving Central Scene Notifications.
- Issuing RF Telemetry reports at each transmission when RF Telemetry is enabled
-
Support for RF Telemetry (reporting transmissions events)
-
Monitoring if Offline nodes are responding again with regular NOPs commands.
-
Network Polling
-
ZPC datastore file key has been changed from --datastore.file to --zpc.datastore_file
-
Default datastore file has been changed from /var/lib/uic/database.db to /var/lib/uic/zpc.db
- If you used the default configuration, keep your previous database by running
mv /var/lib/uic/database.db /var/lib/uic/zpc.db
- If you used the default configuration, keep your previous database by running
-
Increased Z-Wave Tx Queue robustness to multiple Tx sessions.
-
Communication with Z-Wave Module optimized
- Interviewing an offline node would make it appear online.
- Missing Wake Up Interval Set during interview for door/window sensor
- ZPC hangs and stops resolving attributes when DevGUI sends a MoveWithOnOff command
- ZPC is Z-Wave Certified against the Z-Wave Specification release 2021A.
- Support of Z-Wave Command Classes
- Firmware Update
- Control of Z-Wave Command Classes
- Firmware Update
- Indicator
- OTA UIID has been updated to include hardware revision
- Fixed various certification issues
- Build issues
-
Implementation of Unify specification 1.0
-
Support for performing Over The Air update(OTA) of Z-Wave devices
-
Z-Wave Long Range
-
MQTT TLS encryption support
-
Wake up device support
-
Multi cast support
-
Failed node handling
-
Support for Z-Wave command classes
- Indicator
- Version
- Manufacturer
- Z-Wave plus
- PowerLevel
-
Control of Z-Wave command classes
- Alarm
- Firmware Update
- Binary Sensor
- Inclusion controller
- Association Group Information
- Association
- Battery
- Binary Switch
- Wake up
- Door lock
-
Z-Wave support for Z-Wave transports
- Multi command
- Multicast non-secure and S2
- Transport Service
- Multi Channel
- Security0
- Security2
-
ZCL Mappings
- IAZ FireSensor
- IAZ COSensor
- IAZ WaterSensor
- IAZ BatteryLow
- TemperatureMeasurement
- Basic
- DoorLock
- Level
- IlluminanceLevelSensing
- OccupancySensing
- OnOff
- Various bug fixes
- UAM Language updates
- Documentation updates
ID | Known issues | Note |
---|---|---|
UIC-1162 | When device have multiple functionalities on the Z-Wave end, which is mapped to the same ZigBee attribute, the mapping will be incomplete. | Update the UAM file to avoid overlap. |
UIC-1088 | Potentially wrong controller NIF after controller migration. | Usually no problem in practice |
UIC-1603 | When ZPC includes a sleeping device, sometimes the node interview does not succeed and therefore, the full functionality of the node will not be presented to the use. | Wait until the next Wake Up or re-include the node |
UIC-1697 | Nodes with S2 granted keys sending Reports to Follow will trigger a SPAN increase out-of-sync situation. | No workaround. |
UIC-1785 | Wake Up Nodes sending a Wake Up Notification during bootstrapping get put to sleep without interview. | |
Exclude and re-include the node if it happens. | ||
UIC-1798 | ZPC not able to compile with CMAKE_BUILD_TYPE=Release | Build with CMAKE_BUILD_TYPE=RelWithDebInfo instead |
Devices which are tested with the ZPC can be found in the list below. Working devices will be marked with an x and none working devices will be marked with an -.
Vendor | Name | Working (x) or not working (-) | Security inclusion |
---|---|---|---|
Aeotec | LED Bulb Multi-White | x | S0 |
Aeotec | Door/Window Sensor | x | S0 |
Aeotec | Water sensor (6 GEN) | - | Non-Secure |
Aeotec | Range extender 6 | x | S0 |
Aeotec | Door/Window sensor 6 | x | S0 |
Hank | Door/Window Sensor | x | S2-Unauthenticated |
Hank | RGB Bulb | x | Non-Secure |
Hank | Smart plug | x | S0 |
Fibaro | Fibaro Flood Sensor | x | S0 |
Fibaro | Heat Controller | x | S2-Authenticated |
Philio | Smart energy plug-in switch | x | S0 |
Secure | Smart Plug 302 | x | Non-Secure |
Ring | Alarm motion detector (1 Gen) | - | S2-Authenticated |
Yale real living | Door Lock | x | S0 |
Alarm.com | Smart water valve | x | S2 Authenticated |
Alarm.com | Dry contact sensor | - | Non-Secure |