Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/alcalzone/iobroker.zwave2
Z-Wave for ioBroker. Better. Faster. Stronger.
https://github.com/alcalzone/iobroker.zwave2
adapter iobroker smarthome wireless z-wave
Last synced: 3 days ago
JSON representation
Z-Wave for ioBroker. Better. Faster. Stronger.
- Host: GitHub
- URL: https://github.com/alcalzone/iobroker.zwave2
- Owner: AlCalzone
- License: mit
- Created: 2019-05-05T13:10:42.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2024-10-03T19:43:10.000Z (3 months ago)
- Last Synced: 2024-10-14T04:07:21.116Z (2 months ago)
- Topics: adapter, iobroker, smarthome, wireless, z-wave
- Language: TypeScript
- Homepage:
- Size: 25.1 MB
- Stars: 23
- Watchers: 8
- Forks: 13
- Open Issues: 58
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG_OLD.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# ioBroker.zwave2
[
](https://www.npmjs.com/package/iobroker.zwave2)
[](CHANGELOG.md)
[](https://lgtm.com/projects/g/AlCalzone/ioBroker.zwave2/context:javascript)
[](https://weblate.iobroker.net/engage/adapters/?utm_source=widget)
Z-Wave for ioBroker. But better.
Z-Wave 2 is a brand new Z-Wave implementation for ioBroker. It is based on [`zwave-js`](https://github.com/AlCalzone/node-zwave-js), which was written from the ground up for your benefit.
Unless [`ioBroker.zwave`](https://github.com/ioBroker/ioBroker.zwave/) it does not require `OpenZWave`. This means that the installation and updates are fast, and no compilation of static libraries and other complicated steps are necessary.
Furthermore, some devices just don't work in the original adapter, e.g. the Fibaro Roller Shutter 3.
Easy usage in ioBroker was kept in mind during the whole development. For example, some devices reuse configuration parameters to configure many different things. In this adapter, most of them are split into separate states and no complicated math is necessary:
| Config params in ioBroker.zwave2 | vs | Config params in ioBroker.zwave |
| --- | --- | --- |
|  | vs |  |
---
## Documentation and usage
* [FAQ](docs/en/FAQ.md)
* [Troubleshooting](docs/en/troubleshooting.md) · [bei Problemen](docs/de/bei-problemen.md)
---
## Changelog
[Older changes](CHANGELOG_OLD.md)
### 3.1.0 (2023-09-27)
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](https://github.com/zwave-js/node-zwave-js/releases) for details
### 3.0.5 (2023-01-28)
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](https://github.com/zwave-js/node-zwave-js/releases) for details
### 3.0.4 (2022-09-21)
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](https://github.com/zwave-js/node-zwave-js/releases) for details
### 3.0.3 (2022-09-06)
Fixed some more communication issues. If a device isn't working properly after upgrading to 3.x, try to re-interview it.
### 3.0.2 (2022-08-30)
* Fixed some crashes and communication issues
## License
MIT License
Copyright (c) 2019-2023 AlCalzone
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.