Version Identification
- OTA file version: 0192020D
- Application: 1.9.2
- Stack: 2.0.13
New in version 1.9.2
- Migration to new factory block format (FB1)
- Migration to new Persistent Storage 2.0 format and increase of NVM space from 2KB to 20KB
- Migration to ubisys Compact Firmware Upgrade 2.0: CFWU 2.0 is an encrypted, signed and compressed OTA file format. This improves security, cuts update time per device in half with positive effects on battery life for battery powered devices and reduced network bandwidth utilization, and increases available space on the device for future upgrades and new features. We are making all ubisys devices ready for the next major Zigbee release with lots of new features – stay tuned
- Migration is a one-way process and devices will have a different OTA image type after the upgrade. The new image type is 0x7b28
- Added human readable version string
- Added product URL
- Added product code (EAN)
ubisys Compact7B Stack Changes between 2.06 and 2.0.13
Introduced a new version management system and versioning scheme. Using semantic versioning with major.minor.patch in-line with Compact7B Zigbee stack release strategy.
The 2.0.13 release is the first release under this new regime.
- Overall improved reporting reliability
- New reporting engine with collated attribute reports
- Enhancements: Core stack changes to support Amazon’s Works With All Hubs cluster
- Optimizations of IEEE 802.15.4 MAC implementation (remove support for IEEE 802.15.4 beaconing networks, which are not used in Zigbee)
- Improved APS duplicate rejection filter algorithm
- Improved routing, in particular interoperability with third-party Zigbee stacks
- Improved source routing (account for local link failure)
- Improved handling of network-wide broadcasts
- Improved address conflict resolution on behalf of end-devices
- Bug-fix: Route discovery table entry would not expire under rare circumstances
- Bug-fix: Certain code paths need to be reentrant
- Bug-fix: Invalidate outgoing cost on link breakage
- Bug-fix: Issue only a single confirmation for APS data requests to multiple binding targets
- Bug-fix: End-device maintenance scheduling and triggering upon rejoin
- Bug-fix: Channel change was not properly persisted
- Bug-fix: Defer deleting binding targets until they are no longer in use
- Bug-fix: Guarantee that APS sequence numbers are unique (indirect messages live for longer periods of time)
- Bug-fix: APS security material was not always erased from persistent storage
