ioBroker.zwave2 ioBroker z-wave2 adapter has not been updated for a while

I first posted this question on ioBroker Facebook group, but was requested by the group expert to post it here instead:

I'm considering to make ioBroker my main smart home system, but for that I need to start using the zwave2 adapter. However, it appears that the available adapter is based on a rather older version (v10.23.6) of node-zwave-js which is now v13.10.1?

I seems no to be a good idea to rely on the zwave2-adapter available since it hasn't been updated in a year?

Would an alternative good solution be to install zwave-js-ui as a stand-alone and run states/data over to ioBroker via MQTT?

My apologies if this is not the appropriate place to post such a question.

Oct 25 '24 22:10 nesheimt

is there any further development?

Nov 04 '24 11:11 TiDO2k

I'll update it soon

Nov 04 '24 12:11 AlCalzone

Will this updated version of ioBroker Zwave2 have (automatical) dependency bump (?) from the underlaying node-zwave-js components that are constantly updated and improved?

Nov 04 '24 18:11 nesheimt

soon? I'll change to HomeAssistant. No further development here.

Feb 03 '25 16:02 TiDO2k

soon? I'll change to HomeAssistant. No further development here.

Looks you might be right about this adapter. But a way around is to use Zwave JS UI as stand alone, and use MQTT to ioBroker. This takes a few more things to handle(and fiddle with) but works quite nice. Once you are past this hurdle(requires some efforts), but then you are no longer dependent on any adapter even though an adapter would be very nice.

Mar 03 '25 20:03 nesheimt

I can understand the frustration. This year alone (8 weeks), my kids have been home sick 3 weeks, I've been sick 1 week, and I've been on vacation for 1 week. The remaining time needs to be somehow divided between work, family and everything else that's going on.

Hard to find the 3-4 hours it will take to update the adapter, considering I don't even have much of a smart home right now.

I still plan on updating, but it's far from my highest priority at the moment.

Mar 04 '25 11:03 AlCalzone

Take car of yourself. Health and family are of course much much higher priority! I'm sure that this is not only my personal oppinion.

Mar 04 '25 11:03 mcm1957

Hello, I just wanted to ask what it looks like. As a father myself, I know how difficult it is to find time. Best regards Tobias

Jun 20 '25 20:06 WendlTo

Hello AlCalzone, do you see a chance for update or do you recommend to go for the proposal mentioned above: Zwave JS UI as stand alone, and use MQTT to ioBroker?

Aug 06 '25 11:08 LaplaceII

After months of using Zwave JS UI as stand alone I can in general say that it's very stable. There might be something I do wrong but here is one isseue for actuators that operates with "current value - target value pairs". If a device is turned off by a local switch or auto off, the current value in Zwave JS UI is updated, but not the target value(which stays at the "on-value" of 99).

That poses a problem when turning on again using MQTT. Since the target value is already 99 and I'm sending 99 there is no change and hence the value is not sent. I have not managed to send value updates(as opposed to value changes) with MQTT without causing ringing/feedback. My workaround is a JS-handler triggering on current value=0 -> targe value=0.

Aug 06 '25 20:08 nesheimt

@AlCalzone So you didn't find the necessary 3-4 hours to update the adapter in the last 5 month? No offense, you are doing this in your free time, but then I'd call this project as currently not being maintained. I suggest you place a message in the Readme WARNING: This adapter is currently not maintained! as it is in the GitHub repository of the original ioBroker z-wave adapter (https://github.com/ioBroker/ioBroker.zwave) so people know they are installing legacy software without having to read through the issues list first.

Unfortunately there is no alternative z-wave adapter for ioBroker available that is actively maintained aside from Zwave JS UI over MQTT.

Given that z-wave integration is an essential protocol for any home automation system as is Zigbee, this is probably the final motivation for me to move over fully to home assistant.

Aug 22 '25 14:08 PG248

@PG248 hm… about which exact issue we talk? If all is working why you push for an update? Or is it about missing feature?

I don‘t get it

Aug 22 '25 22:08 Apollon77

@Apollon77 I have been reluctant to push the question of upgrades since it's peoples sparetime any effort is taken from. Instead I use the MQTT-approach. I must however admit that I never tried the zwave2 adapter fearing that it would come to a sudden stop caused by some breaking change from the "ioBroker components/framework" and a not up to date adapter. But, based on your answer above...such a scenario is not likely? If so, I will definitely install the zwave2 instead of using the MQTT(which have a few particularities).

Aug 25 '25 15:08 torbjornnesheimbring

Without trying no one knows ;-) I will try to do some basic eep updates in next days.

Aug 25 '25 16:08 Apollon77

Alright ... ok I did some relevant updates to ensure it runs in models js-controllers and such https://github.com/AlCalzone/ioBroker.zwave2/pull/1097

if someone likes to verify you can use Admin - Expertmode - Custom install (Github icon) - Custom tab and use "https://github.com/Apollon77/ioBroker.zwave2#update-deps0825" to install from my fork.

Aug 26 '25 16:08 Apollon77

Thanks, I'll test it hopefully tonight.

Aug 27 '25 12:08 nesheimt

Hi @Apollon77 The adapter did install, but when I come to think about it....the zwave-js version is still on v10 level (I'm not too skilled in this, so sorry if I'm wrong) and it looks like the current is v15. In the "zwave-js versions" there are a device configs that have constantly been improved and debugged. So if I then install a new controller(ioBroker Zwave2) using old version of the config files(v10) I fear there can be domino effects?

Aug 28 '25 07:08 nesheimt

One step after the other :-) My main goal for now was to make sure that the current Adapter version also works in modern js.controllers and node.js versions that might cause issues because of outdated dependencies. I never told that. I also updated the Zwave.js version. This is an update from 5 major versions and that will need a "bit" more effort.

Aug 28 '25 08:08 Apollon77

Yes, I was only me realizing the Zwave.js vesion when doing the installing. I did go one step further and "your fork" reads the devices from my stick, so the adapter seems to be running fine. However, to test further it seems like the adapter needs to re-interview all devices, and that can introduce problems to some devices in respect to device configs.

Aug 28 '25 08:08 nesheimt

Iwould not know why it needs to re-interview all devices? As said the zwave.js version did NOT change!

Aug 28 '25 08:08 Apollon77

My bad, the various device info/config/controls were populated for each node steady but slowly in the state/object list, no re-invervju required. I can also control the devices(testes a few) using the zwave2.

Aug 28 '25 10:08 nesheimt

Hi, thanks for efforts. Would be great to update the zwave2 to the current zwave-js version. E.g. integration of new AeoTec Stick 10 Pro ist very interesting (integrated in zwave-js since June 25). Stick does work with zwave js ui but currently not with IOBroker... ...I guess there are some more devices which might not work with the current zwave-js version in zwave2 adapter...

Aug 30 '25 11:08 LaplaceII

I shifted the #1100 to this issue. Might be that there are also other devices not working due to non updated zwave js version...

Sep 24 '25 13:09 LaplaceII

I could connect to the version Apollon77 provided above. However, its a blank stick with no devices connected. Here the log from the adapter installation: `$ iobroker url https://github.com/Apollon77/ioBroker.zwave2#update-deps0825 --host OT-FHS6-Beelink --debug

install Apollon77/ioBroker.zwave2#160251714471a13db63037cef3bb5c9e555877fc

NPM version: 10.9.3

Installing Apollon77/ioBroker.zwave2#160251714471a13db63037cef3bb5c9e555877fc... (System call)

npm warn skipping integrity check for git dependency ssh://[email protected]/Apollon77/ioBroker.zwave2.git

[email protected] install > node buildcheck.js > buildcheck.gypi && node-gyp rebuild

C:\ioBroker\node_modules\buildcheck\lib\index.js:133 throw new Error('Unable to detect compiler type');

^ Error: Unable to detect compiler type at new BuildEnvironment (C:\ioBroker\node_modules\buildcheck\lib\index.js:133:15) at Object. (C:\ioBroker\node_modules\cpu-features\buildcheck.js:5:12) at Module._compile (node:internal/modules/cjs/loader:1706:14) at Object..js (node:internal/modules/cjs/loader:1839:10) at Module.load (node:internal/modules/cjs/loader:1441:32) at Function._load (node:internal/modules/cjs/loader:1263:12) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) at node:internal/main/run_main_module:36:49 Node.js v22.19.0

[email protected] install > node-gyp rebuild

gyp info it worked if it ends with ok

gyp info using [email protected] gyp info using [email protected] | win32 | x64

gyp ERR! find Python gyp ERR! find Python Python is not set from command line or npm configuration gyp ERR! find Python Python is not set from environment variable PYTHON gyp ERR! find Python checking if the py launcher can be used to find Python 3 gyp ERR! find Python - executable path is "" gyp ERR! find Python - "" could not be run

gyp ERR! find Python you can try one of the following options: gyp ERR! find Python - Use the switch --python="C:\Path\To\python.exe" gyp ERR! find Python (accepted by both node-gyp and npm) gyp ERR! find Python - Set the environment variable PYTHON gyp ERR! find Python - Set the npm configuration variable python: gyp ERR! find Python npm config set python "C:\Path\To\python.exe" gyp ERR! find Python For more information consult the documentation at: gyp ERR! find Python https://github.com/nodejs/node-gyp#installation gyp ERR! find Python ********************************************************** gyp ERR! find Python gyp ERR! configure error gyp ERR! stack Error: Could not find any Python installation to use gyp ERR! stack at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:306:11) gyp ERR! stack at PythonFinder.findPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:164:17) gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5) gyp ERR! stack at async configure (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:27:18) gyp ERR! stack at async run (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js:81:18) gyp ERR! System Windows_NT 10.0.26100 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd C:\ioBroker\node_modules\diskusage gyp ERR! node -v v22.19.0 gyp ERR! node-gyp -v v11.2.0 gyp ERR! not ok

[email protected] install > node-gyp rebuild

gyp info it worked if it ends with ok

gyp info using [email protected] gyp info using [email protected] | win32 | x64

gyp ERR! find Python gyp ERR! find Python Python is not set from command line or npm configuration gyp ERR! find Python Python is not set from environment variable PYTHON gyp ERR! find Python checking if the py launcher can be used to find Python 3 gyp ERR! find Python - executable path is "" gyp ERR! find Python - "" could not be run

gyp ERR! configure error gyp ERR! stack Error: Could not find any Python installation to use gyp ERR! stack at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:306:11) gyp ERR! stack at PythonFinder.findPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:164:17) gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5) gyp ERR! stack at async configure (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:27:18) gyp ERR! stack at async run (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js:81:18) gyp ERR! System Windows_NT 10.0.26100 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd C:\ioBroker\node_modules\unix-dgram gyp ERR! node -v v22.19.0 gyp ERR! node-gyp -v v11.2.0 gyp ERR! not ok

@serialport/[email protected] install > node-gyp-build

added 64 packages, and audited 1842 packages in 2m

371 packages are looking for funding run npm fund for details

70 vulnerabilities (14 low, 25 moderate, 27 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run:

npm audit fix --force Some issues need review, and may require choosing a different dependency. Run npm audit for details.

upload [18] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/.eslintrc.js .eslintrc.js application/javascript

upload [17] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-J724PBLX.js build/chunk-J724PBLX.js application/javascript

upload [16] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-J724PBLX.js.map build/chunk-J724PBLX.js.map application/json

upload [15] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-QC74SDCH.js build/chunk-QC74SDCH.js application/javascript

upload [14] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-QC74SDCH.js.map build/chunk-QC74SDCH.js.map application/json

upload [13] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-RV4HM636.js build/chunk-RV4HM636.js application/javascript

upload [12] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/chunk-RV4HM636.js.map build/chunk-RV4HM636.js.map application/json

upload [11] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/index.js build/index.js application/javascript

upload [10] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/index.js.map build/index.js.map application/json

upload [9] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/log.js build/log.js application/javascript

upload [8] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/log.js.map build/log.js.map application/json

upload [7] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/tab.js build/tab.js application/javascript

upload [6] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/build/tab.js.map build/tab.js.map application/json

upload [5] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/index_m.html index_m.html text/html

upload [4] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/log_window.html log_window.html text/html

upload [3] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/script/d3.min.js script/d3.min.js application/javascript

upload [2] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/style.css style.css text/css

upload [1] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/tab_m.html tab_m.html text/html

upload [0] zwave2.admin C:/ioBroker/node_modules/iobroker.zwave2/admin/zwave2.svg zwave2.svg image/svg+xml

Updating objects from io-package.json for adapter "zwave2" with version "3.1.0"

Process exited with code 0`

Sep 24 '25 14:09 LaplaceII

@LaplaceII Python nnot found? Strange ... versuch mal "iob fix" und dann adaoter uninstall und neu install

Sep 25 '25 07:09 Apollon77

IMO the shelly wave shutter devices are not supported as well.

Sep 25 '25 09:09 PG248

@LaplaceII Python nnot found? Strange ... versuch mal "iob fix" und dann adaoter uninstall und neu install

Windows Installation of IOBroker. This might explain. However, I installed python (incl. pathes) + visual studio build tools (incl. C++). Looks much better now: `$ iobroker url https://github.com/Apollon77/ioBroker.zwave2#update-deps0825 --host OT-FHS6-Beelink --debug

install Apollon77/ioBroker.zwave2#160251714471a13db63037cef3bb5c9e555877fc

NPM version: 10.9.3

Installing Apollon77/ioBroker.zwave2#160251714471a13db63037cef3bb5c9e555877fc... (System call)

npm warn skipping integrity check for git dependency ssh://[email protected]/Apollon77/ioBroker.zwave2.git

@serialport/[email protected] install > node-gyp-build

added 64 packages, and audited 1845 packages in 2m 370 packages are looking for funding

run npm fund for details

70 vulnerabilities (14 low, 25 moderate, 27 high, 4 critical) To address issues that do not require attention, run:

npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run npm audit for details.