Release v3.1.0

Updated zwave-js to 10.23.6. This includes the following changes:

• Added support for Security S2 multicast
• Added support for parsing additional information from Notification CC Reports. Note that this may change the values reported for Door/Window sensors! If you rely on the old behavior, use the new Door state (simple) value instead.
• Added support for Energy Production CC and Window Covering CC
• On devices where legacy alarm values are mapped, the resulting Notification values are now created during the interview.
• Fixed an issue where communication with a node included with Security S2 was not always using encryption.
• Fixed an issue where the Z-Wave stack would not start on Windows systems
• Z-Wave controllers hosted remotely over TCP can now be discovered using mDNS
• Disconnects of Z-Wave controllers hosted remotely over TCP are now detected again
• All commands contained in a Multi Command CC are now properly handled
• Failures while assigning routes to nodes no longer mark the node as dead (unless they actually are)
• Values for unsupported Door Lock CC features are no longer created
• Several reliability/correctness improvements for device interviews
• Auto-assign routes between nodes after creating a new association
• Values for Battery, Meter, Multilevel Switch and (in some cases) Notification CC are now queried periodically or on device wakeup
• Notification variables (like Lock jammed) are now updated when another received report indicates a change, even if the device did not update the notification variable itself.
• Fixed a startup crash that happens when the controller returns an empty list of nodes
• Fixed a crash that happens when message from an unknown node was received
• Several improvements for auto-assigning Lifeline associations
• Lots of new and updated configuration files, see Z-Wave JS releases for details

Release v3.0.5

Updated zwave-js to 10.5.4. This includes the following changes:

• Fixed a memory leak caused by a dependency
• Fixed an issue where multiple re-interview tasks for sleeping nodes could be queued and would be executed in parallel
• Fixed an issue where firmware updates could use a too large fragment size after upgrading to v10, causing the update to fail
• Several improvements related to Security S2
• New and updated configuration files, see Z-Wave JS releases for details

Release v3.0.4

Updated zwave-js to 10.2.0. This includes the following changes:

• Fixed an issue where the possible states for Notification values could be incomplete
• Fixed an issue where setting the time on some devices would always use UTC, even this should be done with local time
• New and updated configuration files, see Z-Wave JS releases for details

Release v3.0.3

Fixed some more communication issues. If a device isn't working properly after upgrading to 3.x, try to re-interview it.

Release v3.0.2

• Fixed some crashes and communication issues

Release v3.0.1

• Fixed crashes related to missing or incorrectly loaded dependencies

Release v3.0.0

Updated zwave-js to 10.0.0. This includes a ton of changes, including:

• Dropped support for Node.js 12
• Several improvements to secure communication, especially with Security S2
• Changed how nodes are sent to sleep, preventing the queue from stalling when the node is already sleeping
• Changed how Supervision CC Reports are sent out, preventing the queue from stalling
• Obfuscated more sensitive data in logfiles
• Fixed a bug where commands that should be discarded would still store their values
• Improved the handling of incoming commands which are received out of order
• Made it possible to disable SmartStart provisioning entries. When excluding a node, its provisioning entry will now be disabled instead of removed.
• New and updated configuration files, see Z-Wave JS releases for details

Release v2.6.0

Updated zwave-js to 9.2.2. Notable changes include:

• The doorStatus/latchStatus/boltStatus states are no longer created if unsupported by the door lock
• Fixed an issue where some 500-series controllers would incorrectly be detected as not supporting Smart Start
• Fixed an issue where some incoming reports would not be processed while an API command was ongoing
• Fixed an issue where changing the color of some devices would use a random duration
• Value changes now also get verified when the device sends an intermediate report
• Retry the initial connection to sticks hosted via TCP
• When the Z-Wave stick is disconnected while the adapter is running, the adapter will automatically try to reconnect again
• Improvements to healing and Smart Start
• New and updated configuration files, see Z-Wave JS releases for details

Release v2.5.0

Updated zwave-js to 9.0.1. This includes many changes, including the following:

• Worked around an issue where certain 500-series controllers take too long to respond when attempting communication with unreachable nodes
• Node queries now timeout faster if no response is received. This should avoid battery-powered nodes to go back to sleep mid-interview.
• Add support for Irrigation CC
• The legacy network cache file <homeid>.json was converted to an appendonly .jsonl file in order to prevent data loss
• Almost all CC API methods now validate their arguments, making it safer to execute custom commands from user code
• User codes and network keys are no longer included in logfiles
• Support for legacy devices which only support the obsolete Multi Channel CC V1
• New and updated configuration files, see Z-Wave JS releases for details

Release v2.4.5

• Update zwave-js to 8.11.6
• After healing, battery-powered nodes are sent back to sleep again
• Added a workaround for thermostats that don't advertise all their supported thermostat modes. When such a thermostat enters such an "unsupported" mode, the mode is now dynamically added to the list of supported modes.
• New and updated configuration files, see Z-Wave JS releases for details