Releases: zwave-js/node-zwave-js
Releases · zwave-js/node-zwave-js
Release v14.3.8
Bugfixes
- Fixed an issue with restoring the network cache from disk on some systems (#7560)
Config file changes
- Preserve all endpoints for Fibaro FGFS101, FW 26.26 (#7561)
- Preserve all endpoints for Fibaro FGFS101, FW 25.25 (#7558)
- Updates to AEON Labs Minimote (#7544)
- Auto-assign Lifeline for Trane XL624 (#7547)
- Disable Supervision for Everspring SP817 Motion Sensor (#7475)
- Add wakeup instructions for ZSE43 (#7454)
- Add wakeup instructions for ZSE42 (#7489)
- Add wakeup instructions for ZSE41 (#7488)
- Add Zooz ZSE70 800LR (#7496)
- Add new device config for Philips DDL240X-15HZW lock (#7498)
- Add Z-Wave.me Z-Station (#7521)
Release v14.3.7
Bugfixes
- Fixed: Firmware updates fail to start on some devices with error "invalid hardware version" (#7452)
Changes under the hood
- Classes that emit events are now based on the DOM compatible
EventTarget
class instead of Node.js's proprietaryEventEmitter
. This means that some methods likeprependListener
no longer exist, but we haven't found any usage of this in the wild.
Release v14.3.6
Bugfixes
- Fixed another issue where some CC API methods would incorrectly fail validation of their arguments, causing the node interview to fail (#7435)
Release v14.3.5
Release v14.3.4
Release v14.3.3
Bugfixes
- Fix parsing of some older 500 series NVM formats (#7399)
- Fixed an issue where
mock-server
would not start due to an incorrect module format (#7401) - Fixed an issue where the auto-generated argument validation for CC API methods would not work correctly in some cases when
zwave-js
was bundled (#7403)
Config file changes
- Add HomeSys HomeMech-2001/2 (#7400)
Release v14.3.2
Bugfixes
- Fixed an issue where encoding a buffer as an ASCII string would throw an error on Node.js builds without full ICU (#7395)
Release v14.3.1
Release v14.3.0
This release is broken. Do not use!
This release adds support for using the WebCrypto API as the cryptography backend. Unlike the node:crypto
module, this API is supported by all modern browsers and JS runtimes.
Technically this is a breaking change, as SecurityManager2
now needs to be instantiated asynchronously using await SecurityManager2.create()
instead of new SecurityManager2()
. However, we don't expect anyone to use this class directly, so this will not be marked as a semver-major release.
Changes under the hood
- Improve portability of the library by supporting the WebCrypto API as cryptography backend (#7386)