Releases: zwave-js/node-zwave-js
Releases · zwave-js/node-zwave-js
Release v12.5.0-beta.0
This release adds support for Z-Wave Long Range thanks to the amazing work of @jtbraun. Application developers planning to add support should read this to get started.
Features
- Support Z-Wave Long Range (#6401)
Config file changes
- Add 2nd product ID for Ring Panic Button Gen2 (#6595)
Changes under the hood
- Fix compatibility of ESLint plugin with Node.js 18 (#6580)
Release v12.4.1
Release v12.4.0
Release v12.3.2
Release v12.3.1
Bugfixes
- Fixed an issue where the unresponsive controller recovery could put "immediate" commands to a sleeping node on the wrong queue, blocking all outgoing communication (#6507)
Config file changes
Release v12.3.0
Features
- Allow disabling the unresponsive controller recovery feature (#6480)
Bugfixes
- Do not abort timed out
Send Data
commands twice (#6484) - Ensure the default Basic CC values are only exposed if they should be, even with the compat
event
enabled (#6485) - Auto-remove failed SmartStart nodes when bootstrapping times out (#6483)
- Do not attempt to poll values from nodes that are considered dead (#6470)
- Fixed an issue where the send queue was blocked when recovering controller from missed Send Data callback failed (#6473)
- Instead of restarting the driver, the serial port is now reopened if controller is still missing ACKs after soft-reset (#6477)
- Do not attempt to recover an unresponsive controller before fully initializing (#6480)
Config file changes
- Tweak Heatit Z-TRM6 options (#6464)
- Add Ring Alarm Panic Button Gen2 (#6453)
- Update fingerprints for Vesternet devices (#6460)
Changes under the hood
Release v12.2.3
Bugfixes
- Mark
Central Scene CC
scene
property as stateless. The previous fix wasn't working. (#6458) - Preserve
stateful
andsecret
flags for dynamic CC values (#6457)
Config file changes
- Correct product id for Fakro ZWS12 (#6454)
- add PM-B400ZW-N (#6421)
- Ensure
kWh
is written consistently in parameter units (#6456)
Changes under the hood
- Bot: Consider
zwave_js
to be a valid logfile name in issue reports (#6459)
Release v12.2.2
Bugfixes
- Fixed an issue where nodes would appear to have two lifeline associations, one with and one without target endpoint 0 (#6448)
- Writing to the
volume
value of theSound Switch CC
no longer throws an error, but pre-sets the volume to use for the next tone to be played using thetoneId
value (#6450, #6451) - The
defaultToneId
value of theSound Switch CC
now also lists the names for each possible tone (#6452)
Config file changes
- Treat
Binary Switch Set
andThermostat Mode Set
as reports forSRT321 HRT4-ZW
(#6423)
Changes under the hood
- Add compat flag to treat
Set
commands asReport
(#6423)
Release v12.2.1
Bugfixes
- Add ESLint rule to ensure all types used in a public CC API are exported (#6438)
- Throttle
firmware update progress
events for OTA updates (#6435) - Mark
Central Scene CC
scene
property as stateless (#6424)
Config file changes
- Override supported Thermostat modes for Eurotronics Spirit TRV (#6436)
- Correct firmware warnings for Zooz controllers (#6433)
- Correct overridden
thermostatMode
metadata for ZME_FT (#6420) - Add MCOHome C521/C621 shutters, fix C321, make shutters consistent (#6419)
Changes under the hood
- Add all
EventListener
methods toTypedEventEmitter
interface (#6437) - Bug reports, feature requests and request for tech support have been moved from issues to discussions. We'll escalate them to issues if necessary.
Release v12.2.0
This release includes several more fixes and workarounds for the problematic interaction between some controller firmware bugs and the automatic controller recovery introduced in the v12
release:
- Added a workaround to recognize corrupted
ACK
frames after soft-reset of controllers running an 7.19.x firmware or higher. Previously this triggered the unresponsive controller detection and recovery process. (#6409) - When the response to a
Send Data
command times out, the command is now aborted, instead of retrying and potentially putting the controller in a bad state due to not waiting for the command cycle to complete. When this happens, Z-Wave JS no longer attempts to recover the controller by restarting it, unless the callback is also missing. (#6408) - When the callback to a
Send Data
command continues to be missing after restarting the controller, Z-Wave JS no longer restarts itself. Instead the old behavior of marking the node asdead
is now restored, as the node being unresponsive/unreachable is most likely the actual problem. (#6403) - In addition, the
Send Data
callback timeout has been reduced to 30 seconds and ongoing transmissions are now aborted before reaching this timeout. This should limit the impact of the controller taking excessively long to transmit, especially in busy networks with lots of unsolicited reporting and end nodes expecting a timely response (#6411)
Features
- The
Driver
constructor now accepts multiple sets of options and curated presets are available (#6412)
Additional Bugfixes
- Only auto-refresh
Meter
andMultilevel Sensor CC
values if none were updated recently (#6398) - Export all option types for
Configuration CC
(#6413)