Skip to content

Latest commit

 

History

History
780 lines (649 loc) · 44.6 KB

CHANGELOG_OLD.md

File metadata and controls

780 lines (649 loc) · 44.6 KB

Older changes

3.0.1 (2022-08-27)

  • Fixed crashes related to missing or incorrectly loaded dependencies

3.0.0 (2022-08-25)

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

2.6.0 (2022-05-10)

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

2.5.0 (2022-04-03)

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

2.4.5 (2022-02-20)

  • 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

2.4.3 (2022-01-18)

  • Updated translations
  • Updated zwave-js from 8.9.1 to 8.11.2. Check out the releases for a detailed overview over the new and changed configuration files.
  • Add support for Humidity Control Mode CC
  • Add support for Humidity Control Operating State CC
  • Add support for Humidity Control Setpoint CC
  • Work around an issue where some devices could not be interviewed due to an incorrect Version CC response.
  • Fixed an issue where Supervision Get requests were not answered for sleeping nodes
  • Re-interviewing sleeping nodes now only resets the known information when the node wakes up
  • The colors dependency was recently corrupted on purpose. This patch updates all dependencies that depended on an affected version, directly or indirectly.

2.4.2 (2021-12-23)

  • Fix: Additional node-related commands now respect and update the node status
  • Fixed an issue where the communication could get stuck after aborting a command
  • New and updated configuration files, see here and here

2.4.2-beta.1 (2021-12-17)

  • Fixed the check for incomplete or incorrect value IDs

2.4.2-beta.0 (2021-12-16)

  • Experimental: The handling of messages has been rewritten from scratch and simplified. This may cause some unintended behavior.
  • Avoid interruption of the communication with a node by other nodes requesting responses from the controller
  • Improved reliability of encrypted communication
  • Battery-powered devices are nore sent to sleep more reliably
  • Fixed encoding of some configuration parameters
  • Fix: Limit allowed Node.js versions to 12.22.2+, 14.13.0+, 16+ and forbid installation on development Node.js versions
  • Fixed some crashes
  • Fixed an issue where healing the network would fail due to a too low timeout
  • Improved detection of sticks that do not support soft reset
  • New and updated configuration files, see here and here

2.4.1 (2021-11-03)

  • Fix: Correctly update UI when canceling an inclusion process
  • Fix: Check for SmartStart support before using it
  • Fix: Add missing translations
  • Fixed the automatic lifeline association for some devices
  • New and updated configuration files, see here

2.4.0 (2021-11-02)

  • Add support for SmartStart and inclusion of nodes with QR codes

2.3.2 (2021-10-26)

  • Try to detect sticks (like UZB and UZB1) that are incompatible with soft-reset and automatically disable it

2.3.1 (2021-10-25)

  • Add option to disable soft-reset, mention better solution in troubleshooting docs

2.3.0 (2021-10-25)

  • Add soft reset (restart) function for the controller
  • New and updated configuration files, see here

2.2.4 (2021-10-22)

  • Fix: Most unsupporting devices should no longer use Supervision by default
  • Minor fixes and stability improvements
  • New and updated configuration files, see here

2.2.3 (2021-10-21)

  • Admin UI: Improve support for older browsers

2.2.2 (2021-10-17)

  • Fix: Config from different instances no longer override each other

2.2.1 (2021-10-12)

  • Fixed a crash when removing a node that is included in a multicast group
  • Fix: writeonly boolean states are now set up as switches instead of buttons
  • Corrupted Multilevel Sensor and Meter reports are now filtered out
  • Fixes to auto-assigning lifeline associations
  • Small fixes to inclusion with security
  • New and updated configuration files, see here

2.2.0 (2021-09-27)

  • The devices list now includes an activity indicator and statistics for each device
  • Improvements to Scene Actuator Configuration CC and Scene Controller Configuration CC
  • Some fixes for Security S2 in combination with Supervision CC
  • Workaround for a bug in Z-Wave sticks with firmware 7.15 and higher that led to missing capabilities
  • Fix: The tab starts on "Devices" again instead of "Groups"
  • Fix: don't offer values from secure nodes under broadcast
  • Fix: display generic device class when specific device class is "Unused"
  • Fix: roles of existing states are now preserved
  • Many changed and new device configuration files, see here and here

2.1.0 (2021-09-23)

  • Support broadcast commands
  • Support multicast commands and managing multicast groups

2.0.1 (2021-09-22)

  • Fix: Don't display "no devices present" if they haven't been loaded yet
  • Fix: Eliminated loading time when switching between "Devices" and "Associations" in tab
  • Fix: Add missing german translation for "Set RF Region"
  • Fix: The Controller node was missing from the association target nodes

2.0.0 (2021-09-22)

  • 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.
  • Upgraded to zwave-js version 8.3.2
  • The device management was moved from the adapter settings to an extra Z-Wave tab.
  • Added a viewer for Z-Wave logs
  • 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

1.10.4 (2021-08-07)

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

1.10.3 (2021-07-14)

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

  • Further improved handling of the legacy alarmType and alarmLevel values under some circumstances
  • Improved support for Aeotec firmware updaters
  • Nodes are no longer sent to sleep while a value change is planned to be verified
  • Hardened the checks to prevent simultaneous write-accesses for the cache files
  • The adapter should now be restarted when the serial connection is disconnected
  • Fixed a bug where associatiations on endpoints had incorrect labels
  • Updated dependencies
  • Tons of new and improved config files

1.10.2 (2021-06-10)

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

1.10.1 (2021-05-24)

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

1.10.0 (2021-04-29)

  • 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

1.9.3 (2021-04-10)

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

1.9.2 (2021-04-05)

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

1.9.0 (2021-03-16)

  • 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

1.8.12 (2021-02-23)

  • Implemented Scene Actuator Configuration CC and Scene Controller Configuration CC
  • Fixed an issue where sleeping nodes could block the send queue when it is not yet known whether they support Wake Up CC
  • Fixed a crash that could happen while logging a message while the driver is not ready yet
  • Fixed a crash that could happen while trying to bootstrap a device that does not respond after inclusion
  • The state value in Thermostat Fan Mode CC is now readonly
  • Configuration parameters may now have a unit
  • Tons of new and improved device configuration files
  • Unsolicited reports are no longer incorrectly mapped to all endpoints

1.8.11 (2021-02-14)

  • Implemented Thermostat Fan Mode CC and Thermostat Fan State CC
  • Fixed several sources of crashes
  • Fixed incorrect detection of secure nodes
  • Certain .hex firmware files are now parsed correctly
  • Added support for .bin firmware files
  • Avoid an infinite interview loop when devices don't advertise the end of the parameter list correctly
  • Sleeping nodes are now immediately marked as ready when restarting from cache
  • Unsolicited reports are no longer mapped from the root endpoint to endpoint 1 if that endpoint does not support the CC
  • Tons of new and improved device configuration files

1.8.10 (2021-02-03)

  • The startup should now be faster, especially if there are many sleeping devices
  • Fixed an issue where devices were incorrectly displayed as secure
  • Improved support for devices that use the legacy Alarm CC
  • Several improvements for Zooz and GE devices

1.8.9 (2021-01-31)

  • Labels for the Meter CC were improved to be unique
  • Many config files were added and updated
  • Improved compatibility with some devices, notably ID Lock 150, Vision Security ZD2102-5, HomeSeer WD200+
  • currentValue and similar values are now updated immediately when a set-type command succeeds. Verification is done after a short delay.

1.8.8 (2021-01-24)

  • Fixed an issue where communication with sleeping secure nodes could get stuck
  • After changing a value, the verification of the new value happens with a larger delay to avoid capturing intermediate and outdated values
  • Several hundred device configuration files were added

1.8.7 (2021-01-21)

  • The scene ID of Scene Activation CC now gets reset automatically
  • Fixed an error that could occur while configuring associations
  • Fixed two potential sources of crashes
  • The values of the root endpoint of some legacy devices are now correctly updated
  • Added support for Aeotec aerQ ZWA009-A US/Canada/Mexico version
  • Fixed invalid parameter options in many config files

1.8.6 (2021-01-17)

1.8.5 (2021-01-06)

  • The interview is no longer aborted when a device does not respond to the Wakeup Capability query
  • Fixed a crash that could happen when compressing the value DB with an existing backup file
  • Added and updated several config files

1.8.4 (2021-01-03)

  • Logfiles are created again

1.8.3 (2020-12-30)

  • Added a config file for Technisat Dimmer and series switch
  • The level low property of the Battery CC is now called Battery Level Low
  • Fixed a bug where the wrong Binary Sensor types were requested. To fix this, affected devices must be re-interviewed
  • The retry strategy for sending commands to nodes has been revised. This should improve communication with devices that take long to respond.
  • Some event values like Central Scene CC scenes are now automatically cleared after 1 second.

1.8.2 (2020-12-23)

  • When a node does not respond because it is asleep, the message is no longer discarded. This should improve the interview behavior of sleeping nodes.
  • Added new config files
  • Fixed wrong label and description for Z-Wave.Me UZB
  • Added missing label to Binary Sensor CC
  • Added missing % unit to Battery level
  • The targetValue for the Binary Switch, Multilevel Switch and Basic CCs is no longer removed when a report without one is received
  • Some more interview timeouts are ignored

1.8.1 (2020-12-14)

  • The targetValue of switch-type CCs is no longer overwritten with undefined when a report without target value is received
  • Added a config file for Jasco ZW3010
  • Added a config file for HeatIt Z-TRM3
  • Added a config file for Eurotronic Air quality sensor (Luftgütesensor)
  • Improved support for Qubino Flush 2 Relay
  • The Multi Channel Association CC, Z-Wave+ CC and Node Naming and Location CC values are now hidden
  • Color Switch CC: Setting the warm white targetValue no longer falsely claims that the propertyKey is missing
  • Removed some debug logging which could blow up the log file size
  • Removing a node association no longer throws an error when both multi channel and normal associations are supported.
  • Notification CC Reports are now parsed correctly when the V1 Alarm bytes are not zero
  • Added support for *.gbl firmware files and Aeotec updater executables which include a checksum and a target chip byte.
  • Fixed an issue where the wrong response could be mapped to some commands
  • ... and some more minor bugfixes

1.8.0 (2020-11-14)

  • Improved config files for Fibaro Keyfob (no special chars anymore) and Shenzhen Neo PD03Z
  • Non-critical steps during the interview of Central Scene CC, Configuration CC V3+ and Association Group Info CC are now skipped when the node does not respond or responds incorrectly
  • Multi Channel Lifeline Associations are no longer created automatically if the device does not support the Multi Channel CC - this should fix compatibility with most Qubino devices
  • Fixed an issue where marking nodes with active transaction as asleep would mess up the serial communication with the controller
  • Empty user codes are now also handled as strings instead of Buffer objects
  • The targetValue property for the Binary Switch, Multilevel Switch and Basic CCs is now created even if it has no value
  • Values for Notification events (one-time events) are now created. Previously only Notification variables were available as states

1.7.10 (2020-11-04)

  • Improved compatibility with devices that don't follow the User Code CC and Notification CC specifications correctly (like Zipato Keypad)
  • Added the ability to edit binary values (e.g. RFID codes) using hexadecimal strings, e.g. 0xbada55.

1.7.9 (2020-11-01)

  • Fixed a crash in the adapter settings when a node's device type is not yet set

1.7.8 (2020-10-25)

  • Fixed a crash while sending a Door Lock command under specific circumstances
  • The timespan that a node is assumed to be awake is now prolonged when it acknowledges a command
  • Fixed a bug where Alarm Sensor CC reports could be assigned to a non-existing node
  • Including nodes which can act as controllers is now supported
  • For nodes with an unknown status, the "remove failed node" button is now enabled
  • The loglevel for warnings about insecure communication because of a missing network key has been reduced to warning.

1.7.7 (2020-10-21)

  • Objects and states are now created for all nodes immediately after the driver is ready
  • States are no longer marked as stale (orange) after a node was interviewed for the first time
  • Fixed an error that would cause the interview of nodes with User Code CC V1 to abort
  • Fixed an error that would cause the interview of nodes which support Central Scene CC but not Association Group Information CC to abort
  • For several CCs, the interview now continues without a fresh value if the node does not respond to a non-critical request
  • Fixed the secure inclusion process for some devices that would behave strangely when nonces were sent without requesting an acknowledgement
  • Fixed an error during logging of a DoorLockCC::ConfigurationSet command
  • After a complete interview, battery-powered nodes that are temporarily mains-powered (e.g. Multisensor 6 with USB power), are no longer sent into a "go to sleep" loop
  • When a node requests multiple nonces in a short timespan, only respond to the most recent request

1.7.6 (2020-10-15)

  • The roles of states are now determined depending on the value they represent instead of just "value"
  • Added a new option to configure if user-defined names for states may be overwritten
  • The targetValue state of Color Switch CC no longer has write set to false

1.7.5 (2020-10-11)

  • Fixed the creation of some missing states (Alarm Sensor CC in idle state, Multilevel Switch CC V1/V2)
  • When a message should be sent to a node that is assumed to be dead, the node is now pinged first to check if it is really dead
  • Improved compatibility with devices that support Notification CC V2+ but send V1 commands.

1.7.4 (2020-10-05)

  • Added a configuration file for Electronic Solutions DBMZ EU
  • Fixed a crash when receiving truncated messages
  • Fixed a crash when trying to send secure commands with an expired nonce (Security CC requires a nonce to be sent!)
  • Several fixes regarding battery-powered nodes (this should prevent the dreaded E5 error on some thermostats, which was back since v1.7.0), including:
    • Battery-powered nodes are actively sent to sleep again when they have no pending messages
    • Compatibility queries are now discarded when the node is asleep, avoiding duplicate queries on wakeup
    • Sending a node to sleep now continues to work even if it failed once

1.7.3 (2020-10-03)

  • Fixed two crashes during the Notification CC interview

1.7.2 (2020-10-01)

  • Added an option to improve the compatibility with legacy switches. If this option is enabled, targetValue (Binary and Multilevel Switch) will be overwritten with currentValue whenever currentValue is updated.
  • When healing the network, the progress should now show up immediately
  • Fixed two crash sources
  • Several improvements to Notification CC
    • The interview now detects whether a node is push or pull
    • Push nodes now have their supporting values set to idle if no value is yet known
    • Pull nodes are now auto-refreshed every 6 hours and on wakeup
  • Including secure devices now fails if the device takes too long to respond (as required by the specifications)

1.7.1 (2020-09-29)

  • Added two options to increase the driver timeouts and/or send attempts. This should allow increasing the network stability at the cost of decreased responsiveness.
  • Added support for User Code CC V2
  • Fix: Nodes are no longer marked as dead or asleep if they acknowledge a message but don't respond to it

1.7.0 (2020-09-25)

  • The quality parameter is now set for state updates when reading (potentially stale) values from the cache
  • Changed the serialport setting field to use autocomplete instead of a dropdown, added a tip how to use serial-over-tcp connections
  • The adapter will now attempt to restart if starting the driver fails
  • Upgraded zwave-js to version 5.0.0. This includes many changes including the following:
    • The driver has been completely rewritten with state machines for a well-defined program flow and better testability. This should solve issues where communication may get stuck for unknown reasons.
    • All interview messages now automatically have a lower priority than most other messages, e.g. the ones created by user interaction. This should make the network feel much more responsive while an interview process is active.
    • Improved performance of reading from the Value DB
    • A node is no longer marked as dead or asleep if it fails to respond to a Configuration CC::Get request. This can happen if the parameter is not supported.
    • The interview for sensor-type CCs is now skipped if a timeout occurs waiting for a response. Previously the whole interview was aborted.
    • If a node that is known to be included securely does not respond to the Security CC interview, it is no longer assumed to be non-secure
    • If a node that is assumed to be included non-securely sends secure commands, it is now marked as secure and the interview will be restarted
    • Added a configuration file for ABUS CFA3010.
    • Added a configuration file for Everspring AC301
    • Removed parameter #5 from Aeon Labs ZW130 because it doesn't seem to be supported in any firmware version
    • In addition to real serial ports, serial-over-tcp connections (e.g. by using ser2net) are now supported. Use these ser2net settings to host a serial port: <external-port>:raw:0:<path-to-serial>:115200 8DATABITS NONE 1STOPBIT
    • Fixed a crash that could occur when assembling a partial message while the driver is not ready yet.

1.6.3 (2020-09-04)

  • Further performance optimization
  • Improved compatibility with devices that send invalid Multi Channel CC commands

1.6.2 (2020-09-04)

  • Reduced CPU load in large networks

1.6.1 (2020-09-01)

  • Fixed interview issues with devices that claim they support Basic CC, but don't respond

1.6.0 (2020-08-29)

  • Added the possibility to send Multilevel Sensor Reports from scripts
  • Dependency updates for bug and security fixes

1.5.0 (2020-07-30)

  • Added the possibility to send custom commands from scripts (documentation).
  • Added a reset state under Meter CC
  • Bugfix: Logs are no longer split across multiple files

1.4.2 (2020-07-05)

  • During the interview, endpoint associations are now converted to node associations if required
  • The interview process no longer fails if a node supports Notification CC V2

1.4.1 (2020-06-30)

  • 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

1.4.0 (2020-06-26)

Updated zwave-js to v4.0.1. This includes the following features:

  • Improved support for legacy devices that don't include all CCs in the NIF, like Fibaro FGRM 222.
  • Added support for Sound Switch CC
  • Added support for Alarm Sensor CC. This CC will only be used if Notification CC is not supported.

1.3.8 (2020-06-18)

  • Fixed transmission issues caused by overlapped secure transactions

1.3.6 (2020-06-17)

  • Added some details to the Multi Channel Association CC interview logging
  • Configured lifeline node associations of newer devices should now be set correctly
  • CRC-16-encapsulated commands can now be received
  • The log file is complete again

1.3.4 (2020-06-16)

  • The association UI no longer crashes if an empty association object is returned
  • The target endpoint selection for associations is now hidden if an association does not support multiple target endpoints
  • Fixed an incompatibility with nodes that have a different number of "normal" associations than multi channel associations, e.g. FGRM-222
  • The association UI now distinguishes between associations to the device and the root endpoint
  • Many fixes related to handling associations and multi channel associations
  • Creating a log file works again
  • Added support for Devolo Dimmer (MT2760) and Shutter (MT2761) (thanks @nicoh88)
  • When the interview process fails to set a lifeline association with Multi Channel Association CC, it now tries again with Association CC

1.3.3 (2020-06-15)

  • Logfiles are now logged in the correct order and some unnecessary logging was removed
  • Fixed an error when using the DoorLockCC setValue API when not all configuration values have been received
  • Errors while sending firmware fragments are now caught and logged
  • The adapter no longer crashes when the serial device exists but does not respond
  • Improved compatibility with some devices that send invalid Multi Channel Endpoint Find Reports, e.g. TKB Home TZ74 Dual Switch

1.3.2 (2020-06-15)

  • Fixed a crash that happens when a Multi Command CC is received

1.3.1 (2020-06-14)

  • Fixed an issue where secure Multi Channel Association Reports were not correctly deserialized
  • Fixed an issue where some associations to the root endpoint could not be removed

1.3.0 (2020-06-14)

  • Added support for firmware updates. WARNING: Use at your own risk!
  • Fibaro FGMS-001 Motion sensor: All association groups are now configured to point to the controller
  • When re-interviewing a node, the information about its command classes is also reset

1.2.1 (2020-06-13)

  • The inclusion dropdown works again

1.2.0 (2020-06-12)

  • Added a possibility to restart the interview for single nodes
  • The cached lifeline associations (for Multi Channel Association and Association CCs) are now updated if they are changed during the interview

1.1.0 (2020-06-11)

  • Added support for Door Lock CC V4
  • Added support for Lock CC
  • Fixed the E5 issue with Danfoss thermostats (hopefully)
  • Fixed an issue where sleeping nodes could block the entire send queue
  • Fixed an issue where some CCs did not store the received values
  • Fixed an issue where the values of endpoint 1 of some multichannel devices were not updated
  • The node interview is no longer aborted if a response for the following requests times out:
    • Battery status
    • Battery health
    • Binary Sensor status
    • Multilevel Sensor status

1.0.0 (2020-06-04)

  • Changed the compatibility config queries for Danfoss thermostats, so queued setpoint changes are not overwritten

0.14.9 (2020-06-03)

  • Placeholder object names (e.g. Node 003) for non-reachable nodes are now overwritten with the correct name when the nodes are interviewed.

0.14.8 (2020-06-03)

  • Fixed an issue where secure sleeping nodes could block all communication with other nodes

0.14.7 (2020-06-03)

  • Fixed an issue where interviews could get stuck for sleeping nodes
  • Fixed a crash that happened when decoding a secure message with an unsupported payload

0.14.6 (2020-06-02)

  • Added support for Protection CC
  • Fixed several bugs in Security CC
  • Updates from a node that span multiple messages are now correctly decoded
  • During the startup, device objects are created for asleep and dead nodes. This allows removing failed devices from the network even after the cache was cleared.

0.14.5 (2020-06-01)

  • Non-securely included nodes which support Security CC should no longer stall the interview process
  • Added an indicator in the devices list to show which nodes are communicating securely

0.14.4 (2020-05-30)

  • The correct status of devices is now shown in the device table instead of unknown
  • The inclusion status is no longer incorrectly shown as active when the adapter was just started
  • Improved handling and retransmission of messages that require nested communication (like Security CC).

0.14.3 (2020-05-27)

  • Added a button to generate a new network key
  • Added a tooltip to explain the network key format
  • It is now possible to copy-and-paste a network key (e.g. from the original adapter). The pasted key is automatically cleaned from unnecessary characters.
  • Fixed a crash that happened when removing nodes with associations to a node that only supports Multi Channel Association CC V1
  • When a node is removed, its interview process is now canceled
  • When a node is manually woken up, the interview is now immediately continued if the adapter was waiting for a response from the node
  • All non-critical errors are now correctly logged instead of undefined

0.14.2 (2020-05-27)

Various fixes related to Security CC when the network key is not configured. This means that the adapter will not crash, but in many cases no meaningful communication with secure nodes will happen and interviews will not be completed.

0.14.1 (2020-05-25)

  • Fixed various crashes:
    • Security CC can only be used when...
    • issuedCommands.has is not a function
  • known issue: Retransmitting secure messages may cause a crash

0.14.0 (2020-05-24)

  • Added support for secure communication (S0) and choosing between secure and non-secure inclusion of nodes
  • Fix: It is now possible to stop inclusion and exclusion processes again

0.13.5 (2020-05-24)

Fixed the frontend that was broken in v0.13.3

0.13.4 (2020-05-22)

User-defined node names are now really preserved

0.13.3 (2020-05-21)

  • Initial values for ready and status states are now read from the nodes
  • Ensure that the adapter notices when a node is ready

0.13.2 (2020-05-21)

  • Various stability and speed improvements during the interview
  • Config parameter #5 has been removed from the Aeotec WallMote Quad for firmware versions <= 1.5

0.13.1 (2020-05-18)

  • Empty node names are now overwritten with the default name
  • Fixed an issue where Multi Channel Associations for older devices were missing

0.13.0 (2020-05-17)

Added a user interface to manage associations between nodes

0.12.2 (2020-05-17)

  • Previously missing updates from multi channel devices should now be received again
  • Fixed an issue where the interview process was stalled by requesting information the devices don't understand
  • Fixed a crash that could happen when the adapter is restarted

0.12.1 (2020-05-12)

  • The cache file is now loaded again correctly. This fixes some missing reports from newer multi channel devices.
  • Nodes are now sent to sleep 1 second after waking up if there are no pending messages. This fixes issues with some devices that expect this behavior.

0.12.0 (2020-05-08)

  • BREAKING: Raised minimum Node.js version to 10
  • BREAKING: Some duplicate states for the root endpoint have been removed
  • The network heal now updates the routes from all nodes to the controller and between associated nodes
  • Significantly reduced CPU consumption and filesystem accesses during the adapter startup
  • Added support for the Color Switch CC
  • Fixed a crash that happened when trying to set an invalid configuration value
  • Updated dependencies

0.11.7 (2020-04-25)

  • Fixed a crash that happened when setting invalid values in ioBroker
  • Fixed some compilation issues with newer typings

0.11.6 (2020-03-22)

Changing values of the Fibaro CC now sends commands to the device

0.11.5 (2020-03-16)

Fixed a bug that caused the interview process to be stuck on the Fibaro CC

0.11.4 (2020-03-15)

Fixed a crash that happened when saving the network state including a Manufacturer Proprietary CC to cache

0.11.3 (2020-03-11)

Fixed a crash that happens when controlling blinds using the Fibaro Venetian Blind CC

0.11.2 (2020-03-09)

Updated zwave-js to v2.15.3. This includes the following fixes:

  • Fixed an issue where the firmware version of nodes would not be read correctly
  • Fixed an issue that caused the interview procedure for the Manufacturer Proprietary CC to be skipped

0.11.1 (2020-03-07)

Updated zwave-js to v2.15.2. This includes the following improvements and fixes:

  • Shortened the interview procedure for some multichannel devices
  • Updated ZHC5002 configuration for firmware versions >= 2.02
  • The clock of devices supporting Clock CC can now be automatically kept in sync with the controller
  • Completed support for the Fibaro Venetian Blind CC
  • Added support for older devices supporting Multi Instance CC
  • The name and status of the controller is now correctly shown in the objects list
  • Values for the root endpoint are now hidden if a corresponding values exists on at least one endpoint

0.10.0 (2020-02-13)

  • Updated zwave-js to v2.13.3 to improve support for older Multi Channel devices
  • Added an actions dialog to the device overview, which allows performing node-specific actions. The first available action is removing failed nodes.
  • Added a ready state for nodes which can be used in scripts to check if the node is ready to accept commands
  • Value that are set to undefined are now converted to null before being passed to ioBroker. This avoids a bug in the javascript adapter where triggers would be called with wrong state values.

0.9.6 (2020-02-10)

Updated zwave-js to v2.13.2. This includes the following fixes:

  • Improved support for older devices with multiple endpoints
  • The HeatIt Z-Push Button 8 should now correctly be detected
  • Potential fix for weird behavior of Start Level Change commands in some devices.

0.9.5 (2020-02-07)

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

  • Improved support for some notifications types
  • Added support for the Clock CC.
  • Fixed a bug where unsolicited commands could wrongly be interpreted as a response to the current request

0.9.4 (2020-02-02)

  • Small performance improvements
  • Fixed an error that could happen when a state was changed before the driver is ready
  • Updated zwave-js to v2.12.3. This includes the following changes:
    • The interview sequence for Thermostat CC V1/V2 should no longer get stuck
    • Improved handling of nodes that don't respond to a request
    • Minor stability improvements and bugfixes

0.9.3 (2020-01-26)

  • Updated zwave-js to v2.12.2. This should fix issues with older Thermostats.

0.9.2 (2020-01-25)

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

  • When a node is removed from the network, all associations to it are also removed
  • The interview procedure is now canceled and retried when an error occurs instead of silently failing all futher steps
  • Improvents to the network heal process were made
  • Several stability improvements regarding the interview procedure and handling of sleeping nodes

0.9.1 (2020-01-21)

  • The progress report for network healing now correctly distinguishes between not yet healed nodes and nodes that failed to heal
  • A potential source of stalled communication because of a missing timeout was eliminated

0.9.0 (2020-01-21)

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

  • Improved Multilevel Switch support for some devices that report the immediate state after a targetValue change but not the final values
  • Fixed two issues where the communication with nodes (especially during the interview) could get stuck

0.8.2 (2020-01-18)

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

  • Locally reset devices are now treated like failing nodes and automatically removed from the controller
  • The Notification status is now also queried on wakeup
  • The status of non-reporting listening nodes is now regularly queried
  • The controller is now correctly treated as an awake node when prioritizing messages

0.8.1 (2020-01-07)

  • Brand new icon!
  • Updated zwave-js to v2.9.1. This includes the following fixes:
    • Notification CC Reports that are received as a response during the interview are now correctly handled
    • Status changes for nodes are now handled better
    • The scenes of the Scene Activation CC are now automatically reset after the duration has elapsed.

0.8.0 (2020-01-04)

  • The cache file is now saved in iobroker-data, so it doesn't get lost between updates
  • Added a button on the device overview tab to clear the cache

0.7.2 (2020-01-04)

  • Fixed an issue where indicators with boolean values could not be written to

0.7.1 (2020-01-03)

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

  • The driver is no longer reset when unexpected data is received. Instead the invalid bytes are skipped.
  • Basic CC reports no longer create a value when they are mapped to another CC
  • IndicatorCC: Binary indicators now use boolean values
  • IndicatorCC: V1 indicators (unspecified) are now ignored if an endpoint is known to have V2 indicators

0.7.0 (2020-01-02)

  • Added a config option to write debug logfiles
  • Updated zwave-js to v2.6.0 to add support for Scene Activation CC

0.6.4 (2020-01-01)

  • Bugfixes

0.6.3 (2019-12-30)

  • Updated zwave-js to v2.5.1. This includes the following changes:
    • Fixed issues with the Meter CC and Indicator CC
    • Fixed an issue where the information about device endpoints was not correctly saved and restored
    • Several configuration parameters with duplicate labels were renamed
  • Node objects and states are now synchronized when the node is ready (rather than waiting for the interview to be completed)
  • When udevadm is not installed on a unix system, the adapter no longer crashes when opening the configuration UI
  • If a node name was manually changed, that change is now preserved
  • The debug log is no longer filled with "state changed" logs
  • Updated some dependencies

0.6.2 (2019-12-22)

  • When nodes are removed, the channel objects are now also removed
  • BasicCC commands from some devices are now mapped to more specific CCs
  • Fixed the interview procedure for IndicatorCC
  • Fixed some causes for crashs

0.6.1 (2019-12-18)

  • Enabled scrolling in the device list

0.6.0 (2019-12-17)

  • Improved handling of sleeping nodes
  • New interactive network healing process in the configuration UI

0.5.2 (2019-12-14)

  • Fixed installation issues with alcalzone-shared

0.5.1 (2019-12-13)

  • A new settings page has been added with a device overview and buttons to add and remove nodes from the network
  • Minor bugfixes

0.4.0 (2019-12-11)

  • The network map is now drawn correctly when there are only unconnected nodes
  • Nodes and command classes are now represented with device and channel objects
  • Updated zwave-js to v2.2.0. This includes the following changes:
    • Less errors are logged when opening the serial port fails
    • Accessing a node's or endpoint's commandClasses property with Symbols no longer causes a crash. (This should not be an issue in ioBroker)
    • Revised querying logic for devices without Z-Wave+ or Lifeline associations
    • Added support for Indicator CC

0.3.4 (2019-12-07)

  • Non-critical errors from zwave-js are now logged instead of crashing the adapter
  • Fixed a crash that happens when the object for a state is missing
  • When the Z-Wave driver fails to start, an error is now logged instead of crashing the adapter
  • The adapter settings are no longer polluted with the serialports list from the frontend

0.3.3 (2019-12-01)

  • Updated zwave-js to v2.1.0. This includes the following changes:
    • Support for the Meter CC
    • Support for unsigned configuration parameters

0.3.2 (2019-11-28)

  • Fixed a crash when property(Key) names contain weird punctuation

0.3.1

  • Fixed a crash from v0.3.0

0.3.0

  • Updated zwave-js to v2.0.0. For the full list of changes, see here. Notable improvements include:
    • Added configuration files for over 1000 devices. This improves support for some older devices and greatly improves the Configuration CC.
    • Basic CC is now hidden if a node support other Actuator CCs
    • Fixed Binary Sensor support
  • Improved generation of state names for complex property names

0.2.1

  • The network map now correctly displays the nodes' IDs

0.2.0

  • Update zwave-js from v1.5.0 to v1.7.0. For the full list of changes, see here. Notable improvements include:
    • Complete Multi Channel support
    • Improved Multilevel Switch support
  • improve value/metadata logging and change loglevel to debug
  • use unit from value metadata
  • use translated property keys to name states

0.1.3

  • Update zwave-js dependency. Notable improvements include:
    • Support for Time and Time Parameters CCs. This automatically sets the correct time on supporting nodes.
    • Support for Battery CC v2
    • Cleanup of CC values
  • Update misc. dependencies

0.1.2

  • Several bugfixes and working admin menu

0.0.1

  • initial release