Release v2.0.0-alpha.1

Upgraded to zwave-js version 8.3.2. Notable changes include:

• BREAKING: Node.js v12.22.2 is now the minimum
• BREAKING: Reworked how endpoints and lifeline associations are handled. This solves reporting issues with many devices, but after a re-interview state IDs may change and some previously working devices may no longer report correctly. Please create an issue for every device that is affected by this.
• The device management was moved from the adapter settings to an extra Z-Wave tab.
• Some config parameters now correctly offer 0/1 as options instead of 0/-1
• Fixed a bug where the cache file could be corrupted during a shutdown
• Support for Security S2
• Support for devices which use Supervision CC to send commands
• Support for factory resetting the controller
• Support for changing the region/frequency of the controller
• Support for replacing failed nodes while keeping the ID
• Some fixes for firmware updates

Release v2.0.0-alpha.0

Upgraded to zwave-js version 8.3.2. Notable changes include:

• BREAKING: Node.js v12.22.2 is now the minimum
• BREAKING: User codes are no longer queried during the interview. They need to be queried manually on demand (not implemented yet).
• BREAKING: Reworked how endpoints and lifeline associations are handled. This solves reporting issues with many devices, but after a re-interview state IDs may change and some previously working devices may no longer report correctly. Please create an issue for every device that is affected by this.
• The device management was moved from the adapter settings to an extra Z-Wave tab.
• Some config parameters now correctly offer 0/1 as options instead of 0/-1
• Fixed a bug where the cache file could be corrupted during a shutdown
• Support for Security S2
• Support for devices which use Supervision CC to send commands
• Support for factory resetting the controller
• Support for changing the region/frequency of the controller
• Support for replacing failed nodes while keeping the ID
• Some fixes for firmware updates

Release v1.10.4

Fixed a bug where the daily config update check would cause a lot of internet traffic for an hour

Release v1.10.2

Upgraded to zwave-js version 7.7.3. Notable changes include:

• Improved how dropped invalid messages are logged in the Z-Wave logfile
• Improved handling of the legacy alarmType and alarmLevel values under some circumstances
• Improved handling of notification values for devices that support Notification CC version 2
• Improved how some devices with incorrect capability reports are queried
• Endpoints of multi channel devices should now always be queried with the correct CC version
• Throttled some automatic queries
• Avoid a situation where multiple instances of the adapter try to access the same cache files, potentially corrupting them
• Improved behavior of secure communication when transmission failures are involved
• Several new and improved config files

Release v1.10.1

Removed some warnings about wrong state value types in JS-Controller 3.3
Upgraded to zwave-js version 7.5.1. Notable changes include:

• Improved stability
• Improved healing strategy
• Several config file changes

Release v1.10.0

The associations tab now shows the name of devices along with their node ID
Associations can now also be managed on the endpoints of a node
Experimental support for updating the embedded configuration files from the adapter configuration
Support firmware updates with *.hec files
Reduced traffic after controlling devices that report automatically
Fixed an issue where Basic CC values were not stored correctly
Added and updated many device configuration files
Stability improvements
Dependency updates

Release v1.9.3

Restored the old behavior for devices that report their values via the root endpoint
Some minor config file changes

Release v1.9.2

Upgraded to zwave-js version 7.1.0. Notable changes include:

• Added reporting of usage statistics. For details, refer to the node-zwave-js documentation.
• Better support for 700-series Z-Wave sticks
• Notification values are no longer auto-reset to idle after 5 minutes by default. This behavior can now be enabled per device if necessary.
• Several stability improvements

For a full list of changes, check out https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md

Release v1.9.1

Upgraded to zwave-js version 7.1.0. Notable changes include:

• Added reporting of usage statistics. For details, refer to the node-zwave-js documentation.
• Better support for 700-series Z-Wave sticks
• Notification values are no longer auto-reset to idle after 5 minutes by default. This behavior can now be enabled per device if necessary.
• Several stability improvements

For a full list of changes, check out https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md

Release v1.9.0

Upgraded to zwave-js version 7
Nodes with a completed interview are no longer queried for all their values when restarting. As a result the adapter is now ready much much faster after a restart, but you'll see many yellow values until the devices have sent updated data.
The device list in the configuration dialog now displays a better type for the devices, for example Wall Controller instead of Routing Slave
Network heal no longer times out early in large networks
Fixed a crash: supportedCCs is not iterable. If this happens to you, re-interview affected devices.
Relaxed the checks when a report gets mapped from the root endpoint to higher endpoints
Some encrypted messages that were previously dropped are now accepted
Prevent the interview of sleeping nodes to get stuck until a re-interview under certain circumstances
After a restart, sleeping nodes have their status correctly determined even if they weren't interviewed completely before
Notification variables are now auto-idled after 5 minutes as it was intended, not after 5 hours
The deltaTime and previousValue values for the Meter CC are now hidden
Fixed a crash that could happen after node inclusion
Tons of new and improved device configuration files