Releases: zwave-js/node-zwave-js
Releases · zwave-js/node-zwave-js
Release v4.1.2
Bugfixes
- Reduced CPU usage in networks with a lot of values
Release v4.1.1
Bugfixes
- The
Basic CC
interview is no longer performed if any actuator CC is supported - If a node does not respond to a
Basic CC::Get
, the interview is no longer aborted. Instead theBasic CC
is marked as unsupported.
Release v4.1.0
Features
- Added the ability to send
Multilevel Sensor Reports
using the newsendReport
method
Misc
- Updated dependencies including bugfixes and security patches
Release v4.0.7
Bugfixes
- Replaced Sentry.io DSN
- Each installation now generates a random ID that is can be used to suppress error reports on a per-user basis
Release v4.0.6
Bugfixes
- Logs are no longer split across two logfiles.
Release v4.0.5
Bugfixes
- Made
Meter CC::Reset
accessible through theSET_VALUE
API.
Release v4.0.4
- During the interview, endpoint associations are now converted to node associations if required
- Allow
Set
andSupportedSet
commands inAlarm CC
V2
Release v4.0.3
Bugfixes
- If a node fails to respond to
Multi Channel Endpoint Find
, the interview is no longer aborted and sequential endpoints are assumed instead - Renamed the manufacturer
Goap
to Qubino - For many Qubino devices, the lifeline now uses a node association
Release v4.0.2
Bugfixes
- The driver no longer goes into an infinite loop when receiving a
CRC-16 Command Encapsulation CC
(#888)
Release v4.0.1
Breaking changes
See "Changes under the hood". I don't expect anything to break, but to be safe, I'll declare this as a major version.
Bugfixes
- It is now assumed that the Basic CC API is always supported
Features
- Mandatory supported CCs that are defined in the device class config are now respected. This should improve support for legacy devices that don't include all CCs in the NIF.
- Added support for
Sound Switch CC
- Added support for
Alarm Sensor CC
. This CC will only be interviewed ifNotification CC
is not supported. - Added a
sendReport
command to theNotification CC
API, which can be used to send customNotificationCCReport
s.
Changes under the hood
-
Moved the definition of legacy Z-Wave device classes to a config file.
-
This project has been converted to a monorepo and split into the following packages:
zwave-js
: As before, this is the main entry point for consumers@zwave-js/config
: The configuration files and methods to access them@zwave-js/core
: The core modules, which are shared betweenzwave-js
and@zwave-js/config
@zwave-js/serial
: A lightweight wrapper aroundnode-serialport
with a built-in parser for received serial API messages@zwave-js/shared
: Utility methods that are shared between all other packages
It is likely that other packages will be added in the future.