Releases: AlCalzone/ioBroker.zwave2
Releases · AlCalzone/ioBroker.zwave2
Release v2.2.4
- Fix: Most unsupporting devices should no longer use
Supervision
by default - Minor fixes and stability improvements
- New and updated configuration files, see here
Release v2.2.3
- Admin UI: Improve support for older browsers
Release v2.2.2
- Fix: Config from different instances no longer override each other
Release v2.2.1
- 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
andMeter
reports are now filtered out - Fixes to auto-assigning lifeline associations
- Small fixes to inclusion with security
- New and updated configuration files, see here
Release v2.2.0
- The devices list now includes an activity indicator and statistics for each device
- Improvements to
Scene Actuator Configuration CC
andScene Controller Configuration CC
- Some fixes for
Security S2
in combination withSupervision 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
Release v2.1.0
- Support broadcast commands
- Support multicast commands and managing multicast groups
Release v2.0.1
- 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
Release v2.0.0
- 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
version8.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 of0/-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.3
- 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
version8.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 of0/-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.2
- 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
version8.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 of0/-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