Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump @zwave-js/core from 10.16.0 to 12.0.2 #193

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 1, 2023

Bumps @zwave-js/core from 10.16.0 to 12.0.2.

Release notes

Sourced from @​zwave-js/core's releases.

Release v12.0.2

Bugfixes

  • The workaround from v12.0.0 for the 7.19.x SDK bug was not working correctly when the command that caused the controller to get stuck could be retried. This has now been fixed. (#6343)

Release v12.0.1

Bugfixes

  • Ignore when a node reports Security S0/S2 CC to have version 0 (unsupported) although it is using that CC (#6333)

Config file changes

  • Add Shelly to manufacturers (#6339)
  • Add Shelly Wave 1, Wave 2PM, update Wave 1PM association labels (#6326)
  • Add Sunricher SR-ZV2833PAC (#6310)

Changes under the hood

  • Added an ESLint rule to help with deciding whether a config parameter needs to be unsigned or not (#6325, #6338)

Release v12.0.0

Application compatibility

Home Assistant users who manage zwave-js-server themselves, must install the following upgrades before upgrading to this driver version:

  • Home Assistant 2023.10.0 or higher
  • zwave-js-server 1.32.0

Breaking changes · Migration guide

  • Remove support for Node.js 14 and 16 (#6245)
  • Subpath exports are now exposed using the exports field in package.json instead of typesVersions (#5839)
  • The "notification" event now includes a reference to the endpoint that sent the notification (#6083)
  • Keep separate Supervision session ID counters for each node (#6175)
  • Validate the device fingerprint before installing firmware update instead of when checking for updates (#6192)
  • Removed some deprecated methods (#6250)
  • Managing SUC routes with the non-SUC method variants is no longer allowed (#6251)
  • "Heal (network)" was renamed to "rebuild routes" to better reflect what it does (#6252)
  • Corrected the argument type for Driver.constructor, updateLogConfig and updateOptions (#6254, #6319)

Features

  • Detect an unresponsive stick and reset it (#6244)
  • The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms). This timeout is now configurable using the driver option timeouts.sendToSleep. This should result in significant battery savings for devices that frequently wake up. (#6312)

Bugfixes

  • 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. (#6296)
  • Removed auto-disabling of soft-reset capability (#6256)
  • Default to RF protection state Unprotected if not given for Protection CC V2+ (#6257)

Config file changes

  • Add Heatit Z-Water 2 (#6299)
  • Add Shelly Wave 1PM (#6280, #6317)
  • Add Heatit Z-TRM6 (#6263)
  • Increase poll delay for ZW500D (#6270)
  • Add fingerprint for Simon IO Master Roller Blind (#6262)
  • Add HOPPE eHandle ConnectSense (#6269)
  • Add parameters to Zooz ZEN17 from firmware 1.30 (#6189)

... (truncated)

Changelog

Sourced from @​zwave-js/core's changelog.

12.0.2 (2023-09-29)

Bugfixes

  • The workaround from v12.0.0 for the 7.19.x SDK bug was not working correctly when the command that caused the controller to get stuck could be retried. This has now been fixed. (#6343)

12.0.1 (2023-09-29)

Bugfixes

  • Ignore when a node reports Security S0/S2 CC to have version 0 (unsupported) although it is using that CC (#6333)

Config file changes

  • Add Shelly to manufacturers (#6339)
  • Add Shelly Wave 1, Wave 2PM, update Wave 1PM association labels (#6326)
  • Add Sunricher SR-ZV2833PAC (#6310)

Changes under the hood

  • Added an ESLint rule to help with deciding whether a config parameter needs to be unsigned or not (#6325, #6338)

12.0.0 (2023-09-26)

Application compatibility

Home Assistant users who manage zwave-js-server themselves, must install the following upgrades before upgrading to this driver version:

  • Home Assistant 2023.10.0 or higher
  • zwave-js-server 1.32.0

Breaking changes · Migration guide

  • Remove support for Node.js 14 and 16 (#6245)
  • Subpath exports are now exposed using the exports field in package.json instead of typesVersions (#5839)
  • The "notification" event now includes a reference to the endpoint that sent the notification (#6083)
  • Keep separate Supervision session ID counters for each node (#6175)
  • Validate the device fingerprint before installing firmware update instead of when checking for updates (#6192)
  • Removed some deprecated methods (#6250)
  • Managing SUC routes with the non-SUC method variants is no longer allowed (#6251)
  • "Heal (network)" was renamed to "rebuild routes" to better reflect what it does (#6252)
  • Corrected the argument type for Driver.constructor, updateLogConfig and updateOptions (#6254, #6319)

Features

  • Detect an unresponsive stick and reset it (#6244)
  • The default time after which battery-powered devices with no pending commands are sent back to sleep is now 250 ms (down from 1000ms). This timeout is now configurable using the driver option timeouts.sendToSleep. This should result in significant battery savings for devices that frequently wake up. (#6312)

Bugfixes

  • 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. (#6296)
  • Removed auto-disabling of soft-reset capability (#6256)
  • Default to RF protection state Unprotected if not given for Protection CC V2+ (#6257)

Config file changes

  • Add Heatit Z-Water 2 (#6299)
  • Add Shelly Wave 1PM (#6280, #6317)
  • Add Heatit Z-TRM6 (#6263)
  • Increase poll delay for ZW500D (#6270)
  • Add fingerprint for Simon IO Master Roller Blind (#6262)
  • Add HOPPE eHandle ConnectSense (#6269)
  • Add parameters to Zooz ZEN17 from firmware 1.30 (#6189)

... (truncated)

Commits
  • 506f1ea chore: release v12.0.2
  • 3726949 chore: update changelog
  • f365296 fix: recovery from missing SendData callback if command may be retried (#6343)
  • a20a90c chore: release v12.0.1
  • 96531df chore: update changelog
  • 9709e16 feat(config): add Shelly Wave 1, Wave 2PM, update Wave 1PM association labels...
  • 962f1f2 docs: recommend building the repository after cloning
  • 67c8bb1 chore: extend auto-unsigned rule to exclusive predefined options (#6338)
  • 551f61f chore: add Shelly to manufacturers (#6339)
  • ab44028 chore: add ESLint rule to check if unsigned flag is necessary or not (#6325)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@zwave-js/core](https://github.com/AlCalzone/node-zwave-js) from 10.16.0 to 12.0.2.
- [Release notes](https://github.com/AlCalzone/node-zwave-js/releases)
- [Changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md)
- [Commits](zwave-js/node-zwave-js@v10.16.0...v12.0.2)

---
updated-dependencies:
- dependency-name: "@zwave-js/core"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant