iobroker/iobroker.zwave

Legacy Z-Wave integration using OpenZWave

ioBroker zwave Adapter

---

WARNING: This adapter is no longer maintained!

The main developer of OpenZWave has announced that he'll focus on other things from now on. As a result, OpenZWave and this adapter won't get any updates going forward.

Solution: Use ioBroker.zwave2 instead.

Note: If you are going to switch to ioBroker.zwave2, be aware that the state IDs will change. It is recommended that you use the ioBroker alias function instead of the adapter's IDs in scripts and visualizations so you can change them all in one place instead of having to edit many things.

---

Zwave support with openzwave.

For this adapter is used rather good supported npm module: https://github.com/OpenZWave/node-openzwave-shared You should find out what the name has USB port of the Z-Wave stick and setup it in the adapter settings.

Important Information

• On first run, the Adapter needs some time, to calculate all Objects within iobroker.
• If you add a Device, let the adapter do it's job and wait a little bit.
• If a Device is not visible within the included Admistration Site, it's not fully imported into ioBroker.

Installation

First of all, Implementation is tested only on ARM Linux (e.g. Raspberry Pi (2)). You need a fully Development Environment (gcc, make,...)

Install additional packages

On some systems it will be necessary to install additional packages. Therefore run the following on the console before installing the adapter:

apt-get install pkg-config libudev-dev build-essential curl unzip

Raspberry Pi3 only: Activate GPIO UART

On Raspberry Pi 3, the UART is by default occupied by the bluetooth module. To activate it for use with a GPIO module, follow these steps:

1. sudo nano /boot/cmdline.txt

   1. remove console=serial0,115200
   2. save the file and close it

2. sudo nano /boot/config.txt
   Look for each of the following lines. If they are commented out with a #, remove that. If they don't exist, add them to the end of the file:

   • dtoverlay=pi3-miniuart-bt
   • enable_uart=1
   • force_turbo=1

3. reboot

First start

The GPIO module usually has an address like /dev/ttyAMA0 or /dev/ttyACM0. The USB stick can be found under /dev/ttyUSB0 or /dev/ttyUSB1.

• Go into iobroker admin and add the Zwave Adapter (the installation is rather long, be patient)
• Start the new zwave Adapter instance and select the controller device's address from the dropdown in the admin UI.
• If your device is not detected, check it or try to manually enter its address when the adapter is turned off.
• Wait until the indicator in the "Instances" tab turns green or the message "zwave.0 Scan completed" is found in the iobroker log.

Known issues

If you get the following (or similar) error after starting the adapter

libopenzwave.so.1.4: cannot open shared object file: No such file or directory

you can fix it by running

sudo ldconfig

or

sudo ldconfig /usr/local

or

sudo ldconfig /usr/local/lib64

If all of those commands don't work, the following process might:

1. sudo nano /etc/ld.so.conf.d/zwave.conf

   1. enter /usr/local/lib64
   2. quit the editor with CTRL+X, confirm with Y to save the changes

2. sudo ldconfig

Configuration

Within Admin Settings you can set following Attributes

• USB name (the USB Port of your Z-Wave stick)
• Logging (enable logging to OZW_Log.txt)
• Console Output (copy logging to the console, Logs all to ioBroker.log)
• Save Config (write an XML network layout create a /zwcfg_.xml on linux)
• Driver Attempts (try this many times before giving up)
• Poll Interval (interval between polls in milliseconds)
• Suppress Refresh (do not send updates if nothing changed)

Logfiles / Configuration Settings

If you have installed iobroker into default Folder:

• Logfile: /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/OZW_Log.txt on linux
• Configuration: /opt/iobroker/node_modules/iobroker.zwave/node_modules/zwcfg_.xml on linux

Device add or remove

If you add or remove a device, it takes 60 seconds. Then the page is automatically reloaded.

If you change the Name or Location, it takes 5 seconds. Then the page is automatically reloaded.

Features

Within OpenZWave Configurator you can see all Nodes and their classes.

Following Actions are current supported (only with context menu):

• Set Name and Set Location for Node itself
• Change Value of a class

Following global Actions are current supported:

• Add Nodes
• Remove Nodes
• Refresh Nodes (Refresh Nodes from ioBroker Communication)

Todo

ZWave Specific

• Scenes
• Group Management
• Polling
• Controller Commands
• Configuration Commands

Global

• Test more Hardware
• Move config and logfile into iobroker default path (/opt/iobroker/log, /opt/iobroker/data/files/zwave)
• Language Support (English, German, Russian)

Tested Hardware

ZWave

• ZME_UZB1 USB Stick
• RazBerry GPIO Board for RaspBerry (1/2)

Fibaro

• FGBS001 Universal Binary Sensor
• FGS222 Double Relay Switch 2x1.5kW
• FGWPE Wall Plug
• FGSS001 Smoke Sensor
• FGMS001 Motion Sensor
• FGS-223 Double Switch 2
• FGR-222 Roller Shutter 2
• FGDW-002 Door/Window Sensor 2

Danfoss

• Danfoss Living Connect Room Thermostat (type 0003, id 8010)
• Danfoss Z Thermostat 014G0013

Changelog

2.0.1

• (AlCalzone) Removed usage of adapter.objects for compatibility with JS-Controller 3.x
• (AlCalzone) Update dependencies

2.0.0

• (cburghardt) Added ldconfig to installation and upgraded openzwave. Fixes #99. If this causes issues, please run the ioBroker fixer first!

1.7.2

• (cburghardt) Fixed a crash

1.7.1

• (cburghardt) Updated openzwave

1.7.0

• (cburghardt) Added multi-instance associations

1.6.3

• (cburghardt) Update openzwave version
• (cburghardt) Verify that the correct version of openzwave is installed by checking the manufacturer revision
• (cburghardt) Don't refresh the association menu directly after adding or removing for sleeping devices as it is not updated
• (cburghardt) Add removeFailedNode command

1.6.1

• (cburghardt) Fix issues 75 and 76

1.6.0

• (cburghardt) Cleanup obsolete states on startup
• (cburghardt) Added confirmation dialog for hard reset
• (cburghardt) Translation fixes
• (cburghardt) Removed non-existing getNeighbors function
• (cburghardt) Display network map
• (cburghardt) Allow manual input of a serial port together with the selection
• (cburghardt) Suppress permission denied warnings during installation

1.5.1

• (cburghardt) The refresh node command no longer excludes the node

1.5.0

• (AlCalzone) Update OpenZWave dependency to version 1.6

1.4.2

• (AlCalzone) Also escape spaces in state IDs.

1.4.1

• (AlCalzone) Pinned version of OpenZWave to 1.4 because 1.6 is not compatible yet

1.4.0

• (AlCalzone) Fixed breaks with OpenZWave 1.6
• (AlCalzone) Switched to new testing
• (AlCalzone) Support for compact mode

1.3.2 (2018-11-28)

• (AlCalzone) Replace all chars in state IDs that are forbidden in JS-Controller 1.5+
• (AlCalzone) Include @types/iobroker and strongly type adapter config properties

1.3.0

• (AlCalzone) Experimental support for CentralScene

1.2.0 (2018-07-25)

• (AlCalzone) Forbidden chars in state IDs are replaced

1.1.0 (2018-05-01)

• (AlCalzone) Use new OZW version for compatibility with NodeJS 10

1.0.0 (2018-01-31)

• (AlCalzone) Simplified resolving the location of the JS-Controller

0.9.0 (2017-10-28)

• (AlCalzone) Fixed lifeline detection in admin UI
• (AlCalzone) Updated buttons to match their behaviour in OZW
• (AlCalzone) Only set adapter status to green after OZW is done initializing
• (AlCalzone) Fixed hard reset: also delete all nodes from ioBroker
• (Pmant/AlCalzone) Parse decimal values into floats, not strings

0.8.0 (2017-07-12)

• (Apollon77) Update to Openzwave-shared 1.4

0.7.0 (2017-07-12)

• (Pmant/AlCalzone) Several fixes and add association ui

0.6.0 (2017-05-01)

• (Pmant) Support secure devices

0.5.2 (2017-04-05)

• (AlCalzone) improved handling of instance status objects

0.5.0 (2017-01-08)

• (bluefox) Update openzwave-shared
• (ekarak) Change install process

0.4.4 (2016-11-27)

• (AlCalzone) Fix enumeration values

0.4.3 (2016-11-26)

• (bluefox) add state "info.scanCompleted"

0.4.2 (2016-11-15)

• (AlCalzone) Read devices from dev and not from serialport

0.4.1 (2016-11-14)

• (AlCalzone) Allow set of parameters

0.4.0 (2016-11-01)

• (bluefox) Rewrite adapter completely

0.2.5 (2015-12-21)

• (husky-koglhof) Object tree build now on change/added/ready from zwave
• Default Role/Type/State (needed for history)
• openzwave-shared 1.1.6
• last openzwave from github
• OpenZWave Security

0.2.4 (2015-12-05)

• (husky-koglhof) fixed hardcoded values Admin Page can Add / Remove ZWave Devices

0.2.3 (2015-11-11)

• (bluefox) try to fix io-package.json

0.2.2 (2015-09-28)

• (ekarak) API changes for openzwave-shared 1.0.8+

0.2.3 (2015-11-11)

• (bluefox) try to fix io-package.json

0.2.2 (2015-09-28)

• (ekarak) API changes for openzwave-shared 1.0.8+

0.2.1 (2015-08-24)

• (husky-koglhof) Fixed Errors with Config save at OpenZwave Configurator

0.2.0 (2015-08-05)

• (husky-koglhof) Added OpenZWave Configurator, changed Dependency from openzwave to openzwave-shared, Implemented stateChange, objectChange Functions, Implemented extended Settings

0.1.0 (2015-01-03)

• enable npm install.

0.0.9 (2014-11-22)

• Support of new naming concept.

0.0.8 (2014-10-31)

• Fix names of classes.

0.0.6 (2014-10-30)

• Show in config found tty ports.

0.0.3 (2014-10-30)

• Classify channels.

0.0.2 (2014-10-28)

• Initial commit. Still non-functional.

License

Copyright (c) 2014-2019 bluefox [email protected], husky-koglhof [email protected]

SOFTWARE NOTICE AND LICENSE

OpenZWave is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

OpenZWave is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with OpenZWave. If not, see http://www.gnu.org/licenses/.

iobroker.zwave's Issues

Make adapter ready for Admin v3

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Installation process is buggy, slow and ineffective

• installOpenZWave() is called twice: once for installing the iobroker module, and then again for adding a new instance
• upon the 2nd invocation the 'unzip master.zip' is silently stalling the process (probably because it prompts for file overwriting?) and needs killing
• we shouldn't need to compile OpenZWave if its already installed!
• precompiled packages should be used when possible. It takes hours to compile OpenZWave on a Raspberry1 !

Open/Close states for blinds do something weird.

I'll check it out.

vers 1.5 association add does not work

problem with ozw 1.6 and zwave 1.5 .. i can not add any node to association

getAllAssociationGroups or getAssociations does not work also.....

but does not work.. after restart i cant see the shortcut

Command:refresh info is excluding the device

Info aktualisieren löscht noch immer Node

Nach Abändern von zig Datenpunkten, muss ich leider mitteilen, dass „Info aktualisieren“ noch immer die Node löscht auch mit aktueller 1.5.1 Version. Neu hinzufügen der Node führt zum Absturz des Adapters.

MCOHome CO2 monitor returns zero values

The device was successfully added but it does not return CO2, temperature and humidity values. I see 0 all the time. The instructions suggest to associate a gateway with Group 2. The Group 2 is in the list on the association tab but disabled (cannot be edited).
I have no any other idea how to get it working.

Thank you.

Duplicate entries

I just upgraded to version 1.4.2. As that version changes the regex to also exclude white space I now have lots of duplicate states.

Do I have to delete the old ones with whitespace?

endless loop while starting

After upgrade to node 10.16.3 and installation problem...the adapter is installed in version 1.6.0 (1.6.1 has same behavior - 1.5.1 isn't there any more..)

enviorment:
Ubuntu 18.10
libopenzwave1.6-dev_1.6.878
openzwave_1.6.878-0_amd64.deb

host.DaIOBroker	2019-09-22 11:15:45.531	info	Restart adapter system.adapter.zwave.0 because enabled
host.DaIOBroker	2019-09-22 11:15:45.531	error	instance system.adapter.zwave.0 terminated with code 127 ()
host.DaIOBroker	2019-09-22 11:15:45.531	error	Caught by controller[0]: io.zwave.0: symbol lookup error: /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/openzwave_shared.node: undefined symbol: _ZN9OpenZWave7O
zwave.0	2019-09-22 11:15:45.485	info	starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.16.3
host.DaIOBroker	2019-09-22 11:15:45.218	info	instance system.adapter.zwave.0 started with pid 10012

any ideas?

Install Problem

$ ./iobroker url "https://github.com/ioBroker/ioBroker.zwave.git" install https://github.com/ioBroker/ioBroker.zwave/tarball/master npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --production --save --prefix "/opt/iobroker" (System call) find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-redis-server.service-Gc20Qv’: Keine Berechtigungfind: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-fwupd.service-pmJVmQ’: Keine Berechtigung find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-bolt.service-azBFEs’: Keine Berechtigung find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-colord.service-o5llKv’: Keine Berechtigung find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-rtkit-daemon.service-dQLIfs’: Keine Berechtigung find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-systemd-resolved.service-Cb3UNP’: Keine Berechtigung find: ‘/tmp/systemd-private-274bcfdb90a64e5bb90c89a10a313fb3-systemd-timesyncd.service-WBylGI’: Keine Berechtigung find: ‘/tmp/ssh-ylh5EtJtkrjt’: Keine Berechtigung

Command failed

I am using the latest version with an Aeotec Stick. I have noticed that the following commands fail:

• "Find neighbors": message unknown command
• click on "update neighbors" for the device: message in the log is Command has failed

Netzwerk Informationen Einblenden

Z.B. so wie das bei Domoticz (auch open zwave basiert) darstellt:
ZWave Netzwerk Anzeige

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.zwave

• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2020 bluefox [email protected]" at the end of README.md
• [E816] file tsconfig.json found in repository, but not found in .npmignore

Thanks,
your automatic adapter checker.

Please check ioBroker.zwave with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Feature Request: Schnittstelle zu iobroker.javascript u.a.

Es wäre sehr hilfreich, auf einige der Funktionalität des Adapters extern zugreifen zu können - insbesondere die Aktivierung des Inclusion/Exclusion-Modus, die aktuell manuell über das Admin-Interface ausgeführt werden kann.
Eine Schnittstelle (z.b. via setzen eines States) würde es erlauben, über eigene externe Software oder Scripts die Geräte im zWave-Netzwerk zu managen, ohne dem Benutzer Zugang zu ioBroker zu geben.

ZWave is not working after 1.4 upgrade

After upgrade to version 1.4 ZWave adapter cannot start.
Here is what I see in the log:
host.iobroker 2019-05-06 17:18:06.721 warn instance system.adapter.zwave.0 terminated due to SIGABRT
Caught 2019-05-06 17:18:06.721 error by controller[1]: what(): Manager.cpp:1768 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel
Caught 2019-05-06 17:18:06.720 error by controller[1]: terminate called after throwing an instance of 'OpenZWave::OZWException'
Caught 2019-05-06 17:18:06.719 error by controller[0]: Unhandled OpenZWave notification: 31
zwave.0 2019-05-06 17:18:06.481 info State created: zwave.0.NODE6.THERMOSTAT_MODE.Mode_1 = undefined, index = 0, comClass = 64, instance = 1
Also I noticed that /usr/local/lib/libopenzwave.so.1.6 is added to the lib directory. But it looks like this new library is not used.
pi@iobroker:~ $ ldd -r /opt/iobroker/node_modules/openzwave-shared/build/Release /openzwave_shared.node
says libopenzwave.so.1.4 => /usr/local/lib/libopenzwave.so.1.4

Thanks

libopenzwave.so.1.4 => /usr/local/lib/libopenzwave.so.1.4 (0x76e04000)

Add Support for Compact mode (js-Controller 2.0 Feature)

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Adapter 1.6.0 Installation does not work

Hello, the Installation of the last Version 1.6.0. does not work.

`pi@ioBroker-slave:~ $ npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --production --save --prefix "/opt/iobroker"

[email protected] preinstall /opt/iobroker/node_modules/openzwave-shared
node lib/install-ozw.js

[email protected] preinstall /opt/iobroker/node_modules/iobroker.zwave
node lib/preinstall.js

[email protected] install /opt/iobroker/node_modules/openzwave-shared
node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird betreten
CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
../src/callbacks.cc: In function ‘void OZW::ozw_watcher_callback(const OpenZWave::Notification*, void*)’:
../src/callbacks.cc:94:26: error: ‘const class OpenZWave::Notification’ has no member named ‘GetCommand’; did you mean ‘GetHomeId’?
notif->command = cb->GetCommand();
^~~~~~~~~~
../src/callbacks.cc:99:8: error: ‘Type_UserAlerts’ is not a member of ‘OpenZWave::Notification’
case OpenZWave::Notification::Type_UserAlerts:
^~~~~~~~~
../src/callbacks.cc:100:31: error: ‘const class OpenZWave::Notification’ has no member named ‘GetUserAlertType’
notif->notification = cb->GetUserAlertType();
^~~~~~~~~~~~~~~~
../src/callbacks.cc: In function ‘void OZW::handleNotification(OZW::NotifInfo*)’:
../src/callbacks.cc:459:8: error: ‘Type_UserAlerts’ is not a member of ‘OpenZWave::Notification’
case OpenZWave::Notification::Type_UserAlerts: {
^~~~~~~~~
../src/callbacks.cc:468:8: error: ‘Type_ManufacturerSpecificDBReady’ is not a member of ‘OpenZWave::Notification’
case OpenZWave::Notification::Type_ManufacturerSpecificDBReady: {
^~~~~~~~~
openzwave_shared.target.mk:136: die Regel für Ziel „Release/obj.target/openzwave_shared/src/callbacks.o“ scheiterte
make: *** [Release/obj.target/openzwave_shared/src/callbacks.o] Fehler 1
make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird verlassen
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.19.66-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
gyp ERR! node -v v8.16.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2019-09-11T09_07_09_214Z-debug.log
`

Secure Connection to Danalock

Hi,
I tried to establish a secure Z-Wave connection to a Danalock. I've uncommented the according Opton NetworkKey in the options file before. When I try to connect the Dana first I see as type a Secure Door Lock Keypad, but after a few seconds that changes to Door Lock Keypad and I get only basic access to the lock.
Openzwave for sure supports secure connections and my java script knowledge is very, very basic, but other systems using openzwave do establish such a secure connection with another function (establish secure connection or so) and use a different extended command in openzwave. I haven't seen such in the current version of the iobroker adapter.
So do you support secure connections yet?
Thanks in advance
Uwe

Raspberry 3 + Z-Wave Me RaZberry Modul, ZME_RAZ_EU

Hello,
it is not possible to use this module in your openzwave connector. have you any ideas for me?

https://www.amazon.de/Z-Wave-Me-RaZberry-Modul-ZME_RAZ_EU/dp/B00BL9QFH6/ref=sr_1_1?ie=UTF8&qid=1484289249&sr=8-1&keywords=raspberry+zwave

USB Device Name

Is it possible to use the "com port ID" (/dev/serial/by-id/) at the "USB Device Name" like the Zigbee Adapter?

Configuration changes not applied

I have some Aeotec multi sensor 6 devices which are battery powered.
If I am not mistaken I should be able to change settings in the admin, they are buffered and when the device wakes up they are stored. And I can accelerate that when I wake up the device manually.
However this doesn't work reliably. I have changed some settings and even woke up the devices but the changes stay in red in the admin and are not confirmed.

Bump to 1.0.0 and publish on stable?

The latest changes seem stable (see forum) and I think this is mature enough for a 1.x version.

So I propose we bump this to 1.0.0 and publish it (I can't do the latter one though).

Add another possible solution for libopenzwave not found

On 64 bit systems, this might help:
https://forum.iobroker.net/topic/11792/z-wave-adapter-problem/9

Installation geht nicht

Fehler in Konsole:

gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Linux 3.18.11-v7+
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared
gyp ERR! node -v v0.10.22
gyp ERR! node-gyp -v v0.11.0
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the openzwave-shared package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls openzwave-shared
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.18.11-v7+
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker.zwave"
npm ERR! cwd /opt/iobroker
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /opt/iobroker/npm-debug.log
npm ERR! not ok code 0

Adapter not working under Windows 2019

I want to use this Adapter under Windows Server 2019, in the device manager the USB Stick is recognized as COM3. As Devicename in the Adapter I tried COM3 and COM3:, but it isn't working.

Here is my log:

zwave.0 | 2019-09-09 23:03:43.852 | error | at Manager.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\component-bind\index.js:21:15)
-- | -- | -- | --
zwave.0 | 2019-09-09 23:03:43.852 | error | at Socket.onpacket (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:236:12)
zwave.0 | 2019-09-09 23:03:43.852 | error | at Socket.onack (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:312:9)
zwave.0 | 2019-09-09 23:03:43.852 | error | at Socket.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.zwave\main.js:117:21)
zwave.0 | 2019-09-09 23:03:43.852 | error | at setAllNotReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.zwave\main.js:594:9)
zwave.0 | 2019-09-09 23:03:43.852 | error | at main (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.zwave\main.js:1051:15)
zwave.0 | 2019-09-09 23:03:43.852 | error | at require (internal/modules/cjs/helpers.js:25:18)
zwave.0 | 2019-09-09 23:03:43.852 | error | at Module.require (internal/modules/cjs/loader.js:692:17)
zwave.0 | 2019-09-09 23:03:43.852 | error | at Function.Module._load (internal/modules/cjs/loader.js:562:25)
zwave.0 | 2019-09-09 23:03:43.852 | error | at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
zwave.0 | 2019-09-09 23:03:43.852 | error | Error: Cannot find module 'openzwave-shared'
zwave.0 | 2019-09-09 23:03:43.851 | error | uncaught exception: Cannot find module 'openzwave-shared'
zwave.0 | 2019-09-09 23:03:43.764 | info | starting. Version 1.4.2 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.zwave, node: v10.16.3

Eversping SP814

Dear Elias,
I have trouble connecting ever spring sp814 motion sensor to iobroker control with a aeon labs z-stick s2. Here is the log:

zwave.0 2017-02-07 20:31:00.076 info controller command feedback: state: "The command has completed successfully", error: "No error", helpmsg: "ControllerCommand - Completed"
zwave.0 2017-02-07 20:31:00.023 info controller command feedback: state: "The command has failed", error: "No error", helpmsg: "ControllerCommand - Failed"
zwave.0 2017-02-07 20:30:59.362 info controller command feedback: state: "The controller is communicating with the other device to carry out the command", error: "No error", helpmsg: "ControllerCommand - InProgress"

Regards,
Ilya

Confirmation for destructive action

I just clicked by accident on the hard reset button and was shocked that all my zwave devices where wiped out. While the function works as expected I would recommend a confirmation dialog.

Manufacturer/Product missing on the MCO Home CO2 sensor

1. Environment:
   1.1. ioBroker in Docker (buanet) on Synology
   1.2. node: v8.15.0
   1.3. npm: v6.4.1
   1.4. ioBroker.zwave: v1.5.1
2. Sensor: MCO Home CO2 (MCOEMH9-CO2) Multilevel Sensor (link to docu)
3. Pre-conditions:
   3.1. Update 1.4.2 -> 1.5.1
   3.2. Container stopped
   3.3. Host system restarted
   3.4. Container started
4. Steps to reproduce:
   4.1. Open instance settings dialog ->Devices
   4.2. Check "Manufacturer" string for the MCO sensor
   4.3. Check "Product" string for the MCO sensor
   4.4. Call "Refresh Info" command
   4.5. Wait (check status by log)
   4.6. Check "Manufacturer" string for the MCO sensor
   4.7. Check "Product" string for the MCO sensor
5. Actual results
   5.1. "Manufacturer" column contains "Unknown: id=015f"
   5.2. "Product" column contains "Unknown: type=0902, id=5102"
6. Expected results:
   5.1. On 4.2 and 4.6 it should by real manufacturer description (like in version 1.4.2) - "MCO Home ..."
   5.2. On 4.3 and 4.7 it should by real product description (also missed in version 1.4.2)

The problem with the libopenzwave of 1.6

When upgrading to version 1.5.0, an error occurs:

host.iobroker2-1 instance system.adapter.zwave.0 started with pid 25116
--
2019-07-11 13:59:11.154 - info: zwave.0 starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.zwave, node: v8.16.0
2019-07-11 13:59:12.560 - info: zwave.0 scanning homeid=0xc6bdb0d0...
2019-07-11 13:59:12.561 - info: zwave.0 driver ready: homeid = 3334320336
2019-07-11 13:59:12.568 - info: zwave.0 Update zwave.0.NODE1
2019-07-11 13:59:12.580 - info: zwave.0 Update zwave.0.NODE1
2019-07-11 13:59:12.610 - error: Caught by controller[0]: io.zwave.0: symbol lookup error: /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/openzwave_shared.node: undefined symbol: _ZNK9OpenZWave7ValueID15GetTypeAsStringB5cxx11Ev
2019-07-11 13:59:12.610 - error: host.iobroker2-1 instance system.adapter.zwave.0 terminated with code 127 ()
2019-07-11 13:59:12.610 - info: host.iobroker2-1 Restart adapter system.adapter.zwave.0 because enabled

recommendations from "known issues" didn't help.

Objects get lost after restart of adapter

Hello,

I made a fresh install of the 1.6 iobroker.zwave adapter (before deletion of 1.5.1 iobroker.zwave adapter). After all devices were recognized and included I renamed needed objects within iobroker objects page (column name) to have clear arragements wihin Blockly. Just for validation reasons I restarted the adpater. All zwave objects which were renamed before were deleted after adapter restart. It would be good to hold the renamed objects after a restart.

Thanks for support
Michael

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.zwave

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.zwave"
• [E301] Tests on Travis-ci.org are broken. Please fix.

Thanks,
your automatic adapter checker.

Associations for group

is it possible to assign associations to groups? the fibaro relay has 2 groups of associations, in the adapter it turns out to bind only to the first group. Is there a way to do that would be to bind to the second?
if I run the script #17 . in response, I get this error message:
javascript.0 ReferenceError: group is not defined at Object.sendTo [as cb] (script.js.Z-Wave.associations:5:22) at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3666:71) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30) at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at Socket.onevent (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:270:10) at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:228:12) at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8) at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)

Aeotec Wallmote Quad node does not update/create states

Hi,
I've recently ordered a Aeotec Wallmote Quad in order to switch a few things on/off using one smart switch to control several devices .
Unfortunately iobroker doesn't update any states when I push buttons from the switch.
There is a switch_binary folder as well as a switch_multilevel folder. There are way too few states available I guess.

I've read something about central_scene_command class. Is it maybe not available in ioBroker yet?
What can be changed to make the switch work?

Thanks,
Kevin

Should we move 0.8 to stable?

It has been out for a while now.
Also, the changes from #21 to #23 have been on GitHub for a few weeks, we should probably move to 0.9.

Rauchmelder von Devolo

Hallo
Ich habe einen Rauchmelder von Devolo gekauft, und ich habe ein Problem mit der Verbindung. Ich habe 2 Mal gekauft, aber den Rauchmelder kann ich nicht mit iobroker verbinden
kann jemand mir helfen bitte
mit freundlichen grüßen
Tolas

Cannot delete devices which are not recognized properly

Hi
I have several problems with Nodon Wallswitches. The include process doesn't work properly but this is maybe more a Nodon problem. But now I have about 5 devices in my device list and when I choose delete device from the option list the OK message appears but nothing happens.

I'm using a Aeotec ZW090 Gen5 Stick and it works perfect with all other devices and brands.

Is there some advice you can give me how to remove them devices?

Thanks and kind regards
Beat

🚩 Certain Object Values Not Updating For Single Node

I've got several z-wave devices successfully included and working with this adapter.

• Raspi 3
• Node.js v10.16.3
• NPM 6.9.0
• zwave adapter 1.6.1
• ozw 1.6
• only one instance

Recently I added a Qubino (Goap) ZMNHDD1 Flush Dimmer

• ZWave+_Version 1
• Application_Version 3.01
• Library_Version 3
• Protocol_Version 4.24

✔ Inclusion went well
✔ Changing configuration objects in zwave.0.NODE15.CONFIGURATION work as expected
✔ Device can control the attached lamp correctly

For example, if I change dim level
zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1
from 0 to 50, the lamp is getting turned on and dimmed to 50%.

⚠ But there is an issue when changing object values.
If I change object values from
zwave.0.NODE15.SWITCH_MULTILEVEL
the new values are correctly executed (example from above) but the newly entered values does not appear as new values. The object value stays unchanged until I change the object value again. Than the value becomes the number I entered first.

Again example from above:

• I change zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 from 0 to 50
• The lamp turns on and dims with 50%
• But the value of zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 does not change to 50 as it should but stays on 0
• Changing then zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 from 50 to 75
• Lamp goes up from 50 to 75% brightness
• Value of zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 now becomes 50 instead of expected 75
• Now changing zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 from 75 to 0
• Lamp turns off (75 to 0)
• Value of zwave.0.NODE15.SWITCH_MULTILEVEL.Level_1 now becomes 75 instead of expected 0

ℹ with every change "last updated" becomes the current time (confirmed: true, quality: ok) even though there are no changes visible for this value

📌 The odd thing is, that this only happens for some objects and only for this one NODE.
Changing objects values from zwave.0.NODE15.CONFIGURATION works as expected and changes are instantly visible.
But some other values - that are read only -, like from zwave.0.NODE15.METER never update them self.

📢 To get the current values for those misbehaving objects, I need to restart the instance.
Only then, current values are pulled and stored in the object.
There is nothing to be found in the logs that would hint to an issue.

ℹ What I've tried:

• I excluded/re-included the device
• Completely removed/setup again adapter

ℹ The device works well in Domoticz and Home Assistant.

Any idea what could be wrong or how I could further debug this issue?

Restart of adapter after calling RefreshNode

1. Environment:
   1.1. ioBroker in Docker (buanet v3) on Synology
   1.2. node: v8.15.0
   1.3. npm: v6.4.1
   1.4. ioBroker.zwave: v1.5.1
   1.5. openzwave-shared: v1.5.6
   1.5. openzwave: v1.6
   1.6. Actuator:
   1.6.1. Manufacturer: "FIBARO System"
   1.6.2. Product: "FGWPE/F Wall Plug Gen5"
   1.6.3. Type: "On/Off Power Switch"
2. Steps to reproduce:
   2.1. Open z-wave instance settings dialog ->Devices
   2.2. Find device in list
   2.3. Open commands list ("Select operation")
   2.4. Select "Refresh info"
3. Actual results
   3.1. Adapter restarted:

---

2019-08-28 23:01:33.248 - [32minfo[39m: zwave.0 Execute refreshNodeInfo for 23
2019-08-28 23:01:35.260 - [33mwarn[39m: host.iob instance system.adapter.zwave.0 terminated due to SIGSEGV
2019-08-28 23:01:35.260 - [31merror[39m: host.iob instance system.adapter.zwave.0 terminated with code null ()
2019-08-28 23:01:35.260 - [32minfo[39m: host.iob Restart adapter system.adapter.zwave.0 because enabled
2019-08-28 23:02:05.300 - [32minfo[39m: host.iob instance system.adapter.zwave.0 started with pid 6415
2019-08-28 23:02:05.989 - [32minfo[39m: zwave.0 starting. Version 1.5.1 in /opt/iobroker/node_modules/iobroker.zwave, node: v8.16.1

Wrong Horstmann HRT4-ZW thermostat setpoint type

The thermostat Horstmann HRT4-ZW has setpoint type Cooling_1_1 instead Heating_1_1 after update from version 1.6.0 to 1.6.1

Z-Wave Secure Boiler Receiver HRT - doesnt update relay status

Device marked as supported, added to openzwave properly, shown as it should, i can control relay position, but cant see relay status if it change by thermostat.
With vera lite, relay status shown properly, so receiver send it to controller, but when i try to use it with openzwave - i can not see state, openzwave ignore state change

raspberry pi4 und Z-Wave Stick von Aeotec

Gilt hier auch die Änderung wie für den Raspberry 3 ? Ich kann nämlich keinen USB-Port einstellen.

Bewegungssensoren bleiben hängen

Hallo,

wie angedroht :-) Bei mir bleiben immer wieder einige Bewegungssensoren kleben/hängen. Sie aktualisieren den Status nicht und signalisieren weiter "Bewegung" oder "nicht Bewegung".
Netzwerk ist riesig, an Empfang kann es nicht liegen. Betroffen sind die Typen Aeon Multisensor 6 und das Fibaro Auge (FGMS001-ZW5 Motion Sensor). Fehler tritt aber nicht erst seit dieser Version auf. Weiß leider nicht mehr genau wann es anfing aber an den OZW Update liegt es denke ich nicht.

Karte vom Netzwerk nicht leserlich

Hallo,

erst mal wieder Danke für das neue coole Feature. Aber bei mir kann ich auf der Karte leider nichts erkennen. Schaut aus wie ein riesen Wollkneul der sich ständig hin und her bewegt wie ein Schwarm Bienen oder Fliegen.

Getestet unter macOS mit Chrome und Safari. Jeweils aktuelle Versionen.

JavaScript selector fails

In my setup I am using selector: $('state[role=value.battery]) but it fails with error - can't find 'common' in undefined object.
After investigation I found that there are such id's in selector: zwave.0.NODE9.awake
And it appears that there is no object (getObject returns null) for such ids (*.awake)

Verify Compact mode for your adapter

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

No feedback from the config UI in Admin 3

Buttons correctly set the controller in inclusion mode, etc. but no feedback reaches the admin UI and buttons don't get updated. Because of that, inclusion can only be stopped by restarting the adapter - which can take a long time on large networks.

v1.5.0 Fibaro Wall Plug - no Switch Binary

With the last Update the Command Class Switch Binary will not create so the Wall Plug can not be switched on / off.

Beschreibung der unterstützten Fibaro Produkte ergänzen

Folgende Fibaro Produkte werden ebenfalls unterstützt, bitte in der Beschreibung ergänzen:

FGS-223 Double Switch 2
FGR-222 Rollo Shutter 2
FGDW-002 Door/Window Sensor 2

Can i use Aeotec AEOEZW090-C ?

can i use this one ?

https://www.amazon.de/Aeotec-AEOEZW090-C-Stick-eingebauter-Batterie/dp/B00YETCNOE/ref=sr_1_2?ie=UTF8&qid=1516127243&sr=8-2&keywords=zwave+usb+stick