zwave-js/node-zwave-js v6.0.0-alpha.2

Release v6.0.0-alpha.2

on GitHub

Breaking changes · Migration guide

• Logging can now be configured through driver options. However, the environment variables for logging are no longer evaluated lazily, so they now need to be set before requiring zwave-js.
• The second (string) parameter of the "interview failed" event handler was removed
• The type ValueMetadataBase has been renamed to ValueMetadataAny. The old type ValueMetadataAny was merged into ValueMetadataBase.
• The retry strategy for sending commands to nodes has been revised. By default, a message is no longer re-transmitted when the node has acknowledged its receipt, since it is unlikely that the retransmission will change anything. The old behavior can be restored by setting the attempts.retryAfterTransmitReport driver option to true.
  To compensate for the change and give the response enough time to reach the controller, the default for timeouts.response has been increased from 1600 to 10000.
• The driver now distinguishes between stateful and event values. The latter are now exclusively exposed through the "value notification" event.
• The deprecated nodeInterviewAttempts option was removed
• The options fs and cacheDir have been renamed to storage.driver and storage.cacheDir.

Config file changes

• Added Technisat Dimmer and series switch
• Add Lifeline association to Danfoss MT 2649
• Add product id/type to NAS-WR01ZE
• New versions of @zwave-js/config are now automatically released every night if only config files were changed since the last release.
  You can run npm update @zwave-js/config in the zwave-js install dir to pull the latest config files. For now, a driver restart is required afterwards.

Features

• An option was added to enable logging to the console, even if it is not a TTY
• An option was added to control the filesystem access throttling
• Improved the label for Level low property in BatteryCC

Bugfixes

• Fixed an off-by-one error in the Binary Sensor Supported Report bitmask.
  Note: If your devices are affected by this bug, re-interview them to remove corrupted values.
• Expire nonces for keepS0NonceUntilNext devices until after the next nonce was received by the device