Releases: zwave-js/node-zwave-js
Releases · zwave-js/node-zwave-js
Release v5.3.5
Bugfixes
- Errors while updating the
Multilevel Switch
value in response to aSupervision
report are now caught - Added missing metadata to the
duration
property inColor Switch CC
Release v5.3.4
Config changes
- Updated config param description for
Z-Wave.Me ZME_05459 Blinds controller
- Added a device config for
Z-Wave.Me ZME_06436 Flush Mountable Blind Control
Changes under the hood
- Added more debug logging to track down a particularly sneaky bug
Release v5.3.3
Bugfixes%0A* Including controller-type nodes (the bare minimum) is now supported%0A* Alarm Sensor CC Report
s no longer overwrite the node ID with 0
.%0A* The timespan that a node is assumed to be awake is now prolonged when it acknowledges a command%0A* Fixed a crash while serializing a DoorLockCC::ConfigurationSet
with invalid input%0A%0A### Changes under the hood%0A* In case of an unexpected error while handling a message, the original error stack is now preserved if possible
Release v5.3.2
Bugfixes%0A* Added / fixed some missing or incorrect exports from zwave-js
:%0A * The CCAPI
type is now exported%0A * NODE_ID_BROADCAST
and NODE_ID_MAX
are now value exports%0A * The Endpoint
class is now exported%0A * The InterviewStage
enum is now exported%0A* Several user-facing errors were converted from Error
to ZWaveError
in order to be consistent with other errors.%0A* Warnings about insecure communication with a node because of missing security configuration are now emitted as ZWaveError
s with code ZWaveErrorCodes.Controller_NodeInsecureCommunication
%0A* Internal references to @types/fs-extra
and jest
are no longer leaked, allowing users to consume this library without skipLibCheck
%0A* User Code CC
no longer uses V2 methods during the interview of a V1 node%0A* Fixed an error during the Central Scene CC
interview that could occur if Association Group Information
is not supported%0A* For several CCs, missing responses to non-critical requests are now ignored during the interview%0A* Sent nonces are now transmitted using the ACK
and AutoRoute
transmit options to fix secure inclusion issues with some devices%0A* Fixed an error during logging of a DoorLockCCConfigurationSet
command%0A* After a fresh interview, battery-powered nodes that are temporarily mains-powered, are no longer sent into a "go to sleep" loop%0A* When a node requests multiple nonces in a short timespan, only respond to the most recent request%0A%0A### Changes under the hood%0A* SpyTransport
was moved to @zwave-js/testing
, a development-only testing package
Release v5.3.2-alpha.0
Bugfixes
- Added / fixed some missing or incorrect exports from
zwave-js
:- The
CCAPI
type is now exported NODE_ID_BROADCAST
andNODE_ID_MAX
are now value exports- The
Endpoint
class is now exported - The
InterviewStage
enum is now exported
- The
- Several user-facing errors were converted from
Error
toZWaveError
in order to be consistent with other errors. - Warnings about insecure communication with a node because of missing security configuration are now emitted as
ZWaveError
s with codeZWaveErrorCodes.Controller_NodeInsecureCommunication
- Internal references to
@types/fs-extra
andjest
are no longer leaked, allowing users to consume this library withoutskipLibCheck
- Sent nonces are now transmitted using the
ACK
andAutoRoute
transmit options
Changes under the hood
SpyTransport
was moved to@zwave-js/testing
, a development-only testing package
Release v5.3.1
Bugfixes
- The
targetValue
metadata inColor Switch CC
no longer claims that the value is readonly
Changes under the hood
- Changed how the transaction creation stack is included in error logs
Release v5.3.0
Features
- Transactions now remember where they were created. This can be used to track down unhandled transaction rejections.
- When a message should be sent to a node that is assumed to be dead, the node is now pinged first to check if it is really dead.
- If a device supports
Notification CC
but sendsAlarm CC
(V1) frames, those are treated asNotification Report
s if possible.
Bugfixes
- The value IDs controlling
Start/Stop Level Change
commands in theMultilevel Switch CC
are now also created for V1 and V2 nodes during the interview - The
Alarm Sensor CC
value IDs for supported sensor types are now created as soon as they are known to be supported.
Release v5.2.3-beta.0
Bugfixes
- The value IDs controlling
Start/Stop Level Change
commands in theMultilevel Switch CC
are now also created for V1 and V2 nodes during the interview
Release v5.2.2
Config changes
- Added
Electronic Solutions DBMZ EU
Bugfixes
- Fixed a crash when receiving truncated messages
- When an unexpected error occurs while executing API commands (e.g.
Security CC requires a nonce to be sent!
), the corresponding transaction is now retried or rejected instead of crashing the driver. - Nodes are sent to sleep again when they have no pending messages
- Compat queries are removed from the queue when a node goes to sleep
- Pending pings are resolved when a node wakes up
sendNoMoreInformation
now continues to work after it failed onceWakeUpCC::NoMoreInformation
is no longer moved to the wakeup queue when a node falls asleep
Changes under the hood
- Removed some unused code
Release v5.2.2-artecktest.2
Debug release for Arteck
Bugfixes
- Nodes are sent to sleep again when they have no pending messages
- Compat queries are removed from the queue when a node goes to sleep
- Pending pings are resolved when a node wakes up
sendNoMoreInformation
now continues to work after it failed onceWakeUpCC::NoMoreInformation
is no longer moved to the wakeup queue when a node falls asleep