Releases: zwave-js/node-zwave-js
Releases · zwave-js/node-zwave-js
Release v11.14.1
Changes under the hood
- The
mock-server
now supports loading mocks from outside thenode-zwave-js
repository (#6261)
Release v12.0.0-beta.0
Breaking changes · Migration guide
- Remove support for Node.js 14 and 16 (#6245)
- Subpath exports are now exposed using the
exports
field inpackage.json
instead oftypesVersions
(#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)
Features
- Detect an unresponsive stick and reset it (#6244)
Release v11.14.0
Features
Driver.sendCommand
,Driver.sendMessage
andNode.setValue
now accept an optional callback as part of the options that will be called with the transaction progress (queued, active, failed, complete) (#6212)- Optimized the order of node communication during startup to ensure responsive nodes are ready first (#6233)
- Transmit reports now include the routing scheme (direct, LWR, ...) used for the transmission (#6232)
Bugfixes
- The start/stop time and date values in
Schedule Entry Lock CC
commands are now validated (#6231) - Fixed an issue where
hasDeviceConfigChanged
would return the opposite of what it should (#6240)
Config file changes
- Delay value refresh for
ZW500D
(#6230) - Update several Zooz devices to their 800 series revisions (#6218)
- Extend version range for
Vesternet VES-ZW-DIM-001
(#6216)
Changes under the hood
Release v11.13.1
Bugfixes
- Fixed a regression from
v11.13.0
whereMeter CC
andMultilevel Sensor CC
reports from an endpoint were discarded, although the endpoint did support them, but the root endpoint didn't (#6222) - Fixed a startup crash that happens when the controller returns an empty list of nodes (#6220)
- Fixed an issue where API calls would be rejected early or incorrectly resolved while the driver was still retrying a command to an unresponsive node (#6219)
- Fixed an issue where the controller would be considered jammed if it responds with a
Fail
status, even after transmitting (#6211)
Changes under the hood
- Switched formatting from
Prettier
to the much fasterDprint
(#6198) - Added a precommit hook to format files (#6205)
- Fix type definitions in the documentation for the
"firmware update finished"
controller event (#6206) - Fixed an issue during documentation generation where referencing the same type definition multiple times would not work (#6207)
- Moved the documentation for
Driver.interviewNode
toNode.interview
(#6209)
Release v11.13.0
Features
- Auto-detected serialports now prominently include
/dev/serial/by-id/*
paths (#6182)
Bugfixes
- Discard
Meter CC
andMultilevel Sensor CC
reports when the node they supposedly come from does not support them (#6178) - Abort inclusion when a node with the same ID is already part of the network (#6180)
- Fixed an issue where a node that does not support S0 and/or S2 was shown with an unknown security class (#6187)
- Fixed a regression from
v11.12.0
where devices with aproprietary
field in the device config would not finish the interview (#6202)
Config file changes
- Remove unnecessary endpoint functionality for CT100 (#6185)
Changes under the hood
Release v11.12.0
Features
- When the controller cannot transmit due to being jammed, this is now detected and exposed to applications. In this situation, nodes are no longer being marked as dead. (#6174)
- A hash of the device config used during the interview is now stored and can be used to detect whether a node needs to be re-interviewed after a configuration update (#6170)
Bugfixes
- Fixed an issue where 700 series controllers were not soft-reset after NVM backup when soft-reset was disabled via config (#6176)
Config file changes
- Correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor (#6171)
Changes under the hood
- Config file checks now detect invalid firmware version ranges where
min > max
(#6169)
Release v11.11.0
Features
- The driver configuration now includes settings for RF region and TX power which will automatically be configured on startup (#6159)
- Add support for persistent node-specific defaults for transition duration and volume (#6162)
Bugfixes
- Fixed a regression from
v11.10.1
where the controller's firmware version was not fully queried (x.y
instead ofx.y.z
) (#6165) - Fixed an issue where devices supporting
Notification CC
in push mode were incorrectly detected as using pull mode whenAssociation Group Information CC
is not supported (#6157) - Requests to the firmware update service now include the full
x.y.z
firmware version where known (#6166) - Fixed an issue where region-specific firmware updates would not be returned from the firmware update service (#6167)
Config file changes
Release v11.10.1
Bugfixes
- Change order of commands so the startup does not fail when a controller is already set to use 16-bit node IDs and soft-reset is disabled (#6153)
- Soft-reset is now always enabled on 700+ series controllers (#6154)
- Queried user codes and their status are now preserved during re-interview when they won't be re-queried automatically (#6152)
Config file changes
- Remove unnecessary endpoint functionality for CT101 (#6146)
Changes under the hood
- The
mock-server
now supports loading a directory of mocks (#6145)
Release v11.10.0
Release v11.9.2
Bugfixes
- Fixed a regression from
v11.9.1
where the startup process could stall after soft-reset when using certain pre-700 series controllers (#6132)