From aaf478f5be93e86fee65cb81834b014f2b3a5b46 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 11:34:25 -0400 Subject: [PATCH 01/11] Bump zwave-js to 12.0.0 and zwave-js-server to 1.32.0 --- zwave_js/CHANGELOG.md | 31 +++++++++++++++++++++++++++++++ zwave_js/build.yaml | 4 ++-- zwave_js/config.yaml | 2 +- 3 files changed, 34 insertions(+), 3 deletions(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 975a0b4bc8c..c72140723f5 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -1,5 +1,36 @@ # Changelog +## 0.1.91 + +### Features + +- Detect an unresponsive stick and reset it +- The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms) + +### Bug fixes + +- A bug in the 7.19.x SDK has surfaced where the controller gets stuck in the middle of a transmission. Previously this would go unnoticed because the failed commands would cause the nodes to be marked dead until the controller finally recovered. Since v11.12.0 however, Z-Wave JS would consider the controller jammed and retry the last command indefinitely. This situation is now detected and Z-Wave JS attempts to recover by soft-resetting the controller when this happens. +- Removed auto-disabling of soft-reset capability +- Default to RF protection state Unprotected if not given for Protection CC V2+ + +### Config file changes + +- Add warnings about broken controller firmware versions +- Add Heatit Z-Water 2 +- Add Shelly Wave 1PM +- Add Heatit Z-TRM6 +- Increase poll delay for ZW500D +- Add fingerprint for Simon IO Master Roller Blind +- Add HOPPE eHandle ConnectSense +- Add parameters to Zooz ZEN17 from firmware 1.30 +- Update Zooz ZEN32 config to the latest firmware, include 800 series + +### Detailed changelogs + +- [Z-Wave JS 11.14.3](https://github.com/zwave-js/node-zwave-js/releases/tag/v11.14.3) +- [Z-Wave JS 12.0.0](https://github.com/zwave-js/node-zwave-js/releases/tag/v12.0.0) +- [Z-Wave JS Server 1.32.0](https://github.com/zwave-js/zwave-js-server/releases/tag/1.32.0) + ## 0.1.90 ### Bug fixes diff --git a/zwave_js/build.yaml b/zwave_js/build.yaml index 886ca75a242..5b0fc64a37a 100644 --- a/zwave_js/build.yaml +++ b/zwave_js/build.yaml @@ -9,5 +9,5 @@ codenotary: signer: notary@home-assistant.io base_image: notary@home-assistant.io args: - ZWAVEJS_SERVER_VERSION: 1.31.0 - ZWAVEJS_VERSION: 11.14.2 + ZWAVEJS_SERVER_VERSION: 1.32.0 + ZWAVEJS_VERSION: 12.0.0 diff --git a/zwave_js/config.yaml b/zwave_js/config.yaml index 57b45f74721..477c3b862c2 100644 --- a/zwave_js/config.yaml +++ b/zwave_js/config.yaml @@ -1,5 +1,5 @@ --- -version: 0.1.90 +version: 0.1.91 slug: zwave_js name: Z-Wave JS description: Control a Z-Wave network with Home Assistant Z-Wave JS From 0b781f80884fd6712c5aeef523aad40e9185dc9d Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 11:48:18 -0400 Subject: [PATCH 02/11] Add breaking change note --- zwave_js/CHANGELOG.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index c72140723f5..ce36a771dd0 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -2,6 +2,10 @@ ## 0.1.91 +### Breaking changes + +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible. They will be fixed in 2023.10.0 . + ### Features - Detect an unresponsive stick and reset it From ebe9902550df5bcd7373b2266ccc9e1bcddc26d6 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 12:11:38 -0400 Subject: [PATCH 03/11] stop rebuilding serial port bindings from source --- zwave_js/CHANGELOG.md | 1 + zwave_js/Dockerfile | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index ce36a771dd0..24935ddc54f 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -10,6 +10,7 @@ - Detect an unresponsive stick and reset it - The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms) +- We no long rebuild the @serialport/bindings-cpp package from source ### Bug fixes diff --git a/zwave_js/Dockerfile b/zwave_js/Dockerfile index dc1acf3436c..a92c7d37bd4 100644 --- a/zwave_js/Dockerfile +++ b/zwave_js/Dockerfile @@ -21,7 +21,6 @@ RUN \ "zwave-js@${ZWAVEJS_VERSION}" \ "@zwave-js/server@${ZWAVEJS_SERVER_VERSION}" \ \ - && npm rebuild --build-from-source @serialport/bindings-cpp \ && apk del --no-cache \ .build-dependencies From ca343011cfe78de56e44c7a72008eb6a7bb90ffb Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:41:37 -0400 Subject: [PATCH 04/11] Update zwave_js/CHANGELOG.md Co-authored-by: AlCalzone --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 24935ddc54f..b5dc3b1760c 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -10,7 +10,7 @@ - Detect an unresponsive stick and reset it - The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms) -- We no long rebuild the @serialport/bindings-cpp package from source +- We no longer rebuild the @serialport/bindings-cpp package from source ### Bug fixes From 7bd4e4ad32c6fc32cb66e433a693a0d835fce38c Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:45:45 -0400 Subject: [PATCH 05/11] Update zwave_js/CHANGELOG.md Co-authored-by: AlCalzone --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index b5dc3b1760c..e044b5ac908 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -17,7 +17,7 @@ - A bug in the 7.19.x SDK has surfaced where the controller gets stuck in the middle of a transmission. Previously this would go unnoticed because the failed commands would cause the nodes to be marked dead until the controller finally recovered. Since v11.12.0 however, Z-Wave JS would consider the controller jammed and retry the last command indefinitely. This situation is now detected and Z-Wave JS attempts to recover by soft-resetting the controller when this happens. - Removed auto-disabling of soft-reset capability - Default to RF protection state Unprotected if not given for Protection CC V2+ - +- Devices that send notifications from endpoints, e.g. Aeotec Wallmote, are now properly supported ### Config file changes - Add warnings about broken controller firmware versions From aada7652280d252bb6610bddad8ffa08046764ef Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:48:56 -0400 Subject: [PATCH 06/11] Suggestions --- zwave_js/CHANGELOG.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index e044b5ac908..0d6ac2652cf 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -4,20 +4,20 @@ ### Breaking changes -- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible. They will be fixed in 2023.10.0 . +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible.They will be fixed in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and therefore reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. ### Features - Detect an unresponsive stick and reset it -- The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms) +- Battery-powered devices are sent back to sleep after 250 ms with no command (down from 1000 ms). This should result in significant battery savings for devices that frequently wake up. - We no longer rebuild the @serialport/bindings-cpp package from source ### Bug fixes - A bug in the 7.19.x SDK has surfaced where the controller gets stuck in the middle of a transmission. Previously this would go unnoticed because the failed commands would cause the nodes to be marked dead until the controller finally recovered. Since v11.12.0 however, Z-Wave JS would consider the controller jammed and retry the last command indefinitely. This situation is now detected and Z-Wave JS attempts to recover by soft-resetting the controller when this happens. -- Removed auto-disabling of soft-reset capability -- Default to RF protection state Unprotected if not given for Protection CC V2+ +- Fixed an issue where supporting controllers would no longer be automatically restarted after failing to do so once - Devices that send notifications from endpoints, e.g. Aeotec Wallmote, are now properly supported + ### Config file changes - Add warnings about broken controller firmware versions From 6f41a10da73ce9cf65aa6d21c106c9a929da1ae4 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:49:49 -0400 Subject: [PATCH 07/11] change --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 0d6ac2652cf..42a7aab0a9a 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -4,7 +4,7 @@ ### Breaking changes -- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible.They will be fixed in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and therefore reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible. Firmware updates will work once again starting in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and therefore reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. ### Features From b8395161d63b5b1b0b88f9fb64947e9092c1710c Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 13:53:22 -0400 Subject: [PATCH 08/11] one more change --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 42a7aab0a9a..51a389af9ff 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -8,7 +8,7 @@ ### Features -- Detect an unresponsive stick and reset it +- Unresponsive controllers are now detected and automatically restarted if possible - Battery-powered devices are sent back to sleep after 250 ms with no command (down from 1000 ms). This should result in significant battery savings for devices that frequently wake up. - We no longer rebuild the @serialport/bindings-cpp package from source From 4b02ca6178d739c7b1c0fcf68265618eca95be18 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 26 Sep 2023 20:12:10 +0200 Subject: [PATCH 09/11] Tiny language tweaks --- zwave_js/CHANGELOG.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 51a389af9ff..ec75f32abb5 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -4,19 +4,22 @@ ### Breaking changes -- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backwards compatible. Firmware updates will work once again starting in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and therefore reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backward compatible. Firmware updates will work once again starting in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and, therefore, reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. + ### Features -- Unresponsive controllers are now detected and automatically restarted if possible +- Unresponsive controllers are now detected and automatically restarted if possible. - Battery-powered devices are sent back to sleep after 250 ms with no command (down from 1000 ms). This should result in significant battery savings for devices that frequently wake up. -- We no longer rebuild the @serialport/bindings-cpp package from source +- We no longer rebuild the @serialport/bindings-cpp package from source. + ### Bug fixes -- A bug in the 7.19.x SDK has surfaced where the controller gets stuck in the middle of a transmission. Previously this would go unnoticed because the failed commands would cause the nodes to be marked dead until the controller finally recovered. Since v11.12.0 however, Z-Wave JS would consider the controller jammed and retry the last command indefinitely. This situation is now detected and Z-Wave JS attempts to recover by soft-resetting the controller when this happens. -- Fixed an issue where supporting controllers would no longer be automatically restarted after failing to do so once -- Devices that send notifications from endpoints, e.g. Aeotec Wallmote, are now properly supported +- A bug in the 7.19.x SDK has surfaced where the controller gets stuck in the middle of a transmission. Previously, this would go unnoticed because the failed commands would cause the nodes to be marked dead until the controller finally recovered. Since v11.12.0, however, Z-Wave JS would consider the controller jammed and retry the last command indefinitely. This situation is now detected, and Z-Wave JS attempts to recover by soft resetting the controller when this happens. +- Fixed an issue where supporting controllers would no longer be automatically restarted after failing to do so once. +- Devices that send notifications from endpoints, like Aeotec Wallmote, are now properly supported. + ### Config file changes From 74b124cb43dabb439aed5a4e12d755bdc1f06bba Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 14:27:02 -0400 Subject: [PATCH 10/11] Update CHANGELOG.md --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index ec75f32abb5..3690d12b2f5 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -4,7 +4,7 @@ ### Breaking changes -- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backward compatible. Firmware updates will work once again starting in 2023.10.0. As a result of this breaking change, Checking for updates no longer requires communication with the device and, therefore, reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backward compatible, but will work once again starting in 2023.10.0. This breaking change ultimately improves firmware updates, as checking for updates no longer requires communication with the device and, therefore, reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. ### Features From f0f60b7f2257a06cf881f531520a26ba9b304b52 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Tue, 26 Sep 2023 14:28:19 -0400 Subject: [PATCH 11/11] Update CHANGELOG.md --- zwave_js/CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zwave_js/CHANGELOG.md b/zwave_js/CHANGELOG.md index 3690d12b2f5..01e2dfc6a9b 100644 --- a/zwave_js/CHANGELOG.md +++ b/zwave_js/CHANGELOG.md @@ -4,7 +4,7 @@ ### Breaking changes -- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backward compatible, but will work once again starting in 2023.10.0. This breaking change ultimately improves firmware updates, as checking for updates no longer requires communication with the device and, therefore, reduces the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. +- Firmware updates may no longer work properly in Home Assistant versions 2023.9.x and earlier due to a breaking change upstream that couldn't be made backward compatible, but will work once again starting in 2023.10.0. This breaking change ultimately improves firmware updates, as checking for updates no longer requires communication with the device, therefore reducing the risk of corrupting manufacturer information. This also means that updates for battery-powered devices can be detected without waking up the devices. ### Features