From fea4064c4423989eaea24ba542a0827c0f29a28c Mon Sep 17 00:00:00 2001 From: Dennis Jensen Date: Tue, 25 Oct 2022 14:27:20 +0000 Subject: [PATCH] Pull request #205: UIC-2514: Remove release notes from Unify matter brige Merge in WMN_TOOLS/matter from feature/UIC-2514_Remove_release_notes_from_unify_matter_bridge to silabs Squashed commit of the following: commit 2907b5a1bc3327a3deb33a19a34c73196665f537 Author: Dennis Jensen Date: Tue Oct 25 09:28:31 2022 +0200 UIC-2514: Remove release notes from Unify matter brige --- .../unify-matter-bridge/release_notes.md | 64 ------------------- 1 file changed, 64 deletions(-) delete mode 100644 silabs_examples/unify-matter-bridge/release_notes.md diff --git a/silabs_examples/unify-matter-bridge/release_notes.md b/silabs_examples/unify-matter-bridge/release_notes.md deleted file mode 100644 index b331e8c9eb56d3..00000000000000 --- a/silabs_examples/unify-matter-bridge/release_notes.md +++ /dev/null @@ -1,64 +0,0 @@ -# Matter Bridge Release Notes - -## [0.4.0] - Oct 12th 2022 - -### Fixed - -- Fixed the issue of the bridge service does not persists mapping between endpoint numbers and - Unify UNIDs. As a consequence the endpoints may swap ids on each program - startup. - -- Fixed the issue of group mapping does not check for existing Unify groups. As a consequence the - Matter Bridge may use an already assigned Unify group. - -### Added - -- Added support for the following clusters: - - Color Control - - Temperature Measurement - - Occupancy Sensing - -- Added a commissioner command to the CLI when running the unify-matter-bridge. - -### Known Issues - -- Endpoint 0 of the bridge shows support for the Identify cluster, but the - identify commands has no effects. -- When using Google Home with unify-matter-bridge only commissioning works, all - Unify nodes appear as offline after commissioning. - -## [0.1.0] - Aug 8th 2022 - -### Fixed - -### Added - -- The Bridge has only support for a limited number of clusters, but it will - present device types of with unsupported cluster never the less. The bridge - supported mapping of the following clusters: - - Bridge Device Information - - Level - - OnOff - - Identify - - Group - -### Known Issues - -- The bridge service does not persists mapping between endpoint numbers and - unify UNIDs. As a consequence the endpoints may swap ids on each program - startup. - -- Group mapping does not check for existing unify groups. As a consequence the - matter bridge may use an already assigned unify group. - -- The bridge service does not persists its matter fabric credentials between - system reboots. After RPi reboot, the bridge will always be noncommissioned. - This can be fix by choosing a proper location for the KVS file using the - `--kvs` command line flag. - -- Endpoint 0 of the bridge shows support for the Identify cluster, but the - identify commands has no effects. - -- The version chip-tool provided with the unify matter bridge is unable to send - group cast messages. As a workaround the chip-tool from the matter master - branch can be used.