ubisys R0 Series 2 Firmware Change Logs

Common Functionality
- Persistent Storage 2.0: Added various improvements and optimizations for internal flash memory management during the startup phase for improved resiliency
- Added sanity checks for ubisys proprietary input configurations, which are supplied over-the-air
- Improved the start-up behavior of the input state machine (deferred initialization)
Zigbee Cluster Library
- Time client: Extended the permissible maximum interval between periodic server queries. Prior to this change, the interval has to be less than about 20 hours
- OTA client: Improved handling of duplicate image block data, i.e. data that has already been fully or partially received. This prevents unnecessary retries and speeds up the overall download process
- Added support for restoring factory default reporting configurations using the factory default configuration of an arbitrary (other) endpoint as template
Zigbee Network Core Stack
- Improved resilience: Account for the case that retry of a fragmented APS transmission might occur even after all fragments have been received
- Resolved an issue where the ‘extended nonce’ flag might not have been set when transmitting an APS encrypted Update Device command

Common Functionality
- Provided applications/platforms an opportunity to interleave with certain computationally intensive procedures
- Added verification steps when OTA images are stored in external flash
Zigbee Cluster Library
- Color Control server: Improved the internal application interface regarding the state of color transitions
- Color Control server: Improved management of Enhanced Color Mode (CCB 4071)
- Color Control server: Resolved an issue where initiating an instant color transition could result in a division-by-zero exception on some platforms
- Enhanced the attribute framework such that applications need not provide updated values when refreshing attributes if such updated values are not available or desired
- Addressed an issue where the sequence of operations was undefined, potentially lead to incorrect processing of manufacturer-specific inbound ZCL frames on certain platforms. Note: This affects only a new platform, not existing platforms and products
- Fixed an issue where an attribute with dynamic storage might not have allocated storage at initialization time
Zigbee Network Core Stack
- Improved resilience: Add defensive code to guard against invalid source route information embedded into a network frame. Based on a field issue with a third-party Zigbee stack
- Simplified and improved the way of creating ZDO simple descriptors

Added regular watch-dog timer reset during persistent storage operations that are not time-bound. This is a critical fix for all Series 2 products that shall be applied immediately and also highly recommended for all other products

Common Functionality
- Added application/platform-specific hooks to Persistent Storage 2.0 when swapping cached pages
Zigbee Network Core Stack
- Various improvements and optimizations regarding the network rejoin behavior of sleepy end-devices