Switching from Zwave 1.4 (Deprecated) to Zwave JS

Community Guides
164

I can not get this to work… i’ve read every post here.

I’m on Pi4 with zwave.zooz_zst10_s2_z_wave_plus_usb_stick zwave stick

My usb path is typical : /dev/ttyACM0

Key is network_key": “0x01, 0x02, 0x0A, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10”

Converted to 32: 01020A0405060708090A0B0C0D0E0F10

On save it immediately fails and log just says failed:
2021-03-12 08:51:32 ERROR (MainThread) [homeassistant.components.zwave_js.config_flow] Failed to set Z-Wave JS add-on config: Failed to set the Z-Wave JS add-on options

Any thoughts? I had 1.4 set up in config; commented it out, restarted multiple times. Retried a dozen+ times.

Thank you. Paul

165

Open up the addon and verify that the configuration parameters are set to what you think they should be. Verify every letter of the usb path. Secondly, the usb path may be different. There’s a drop down and the available paths will be populated. You’ll most likely be using the device path instead of what you had before.

166

I figured it out. I’m an idiot. ADDON not Integration.

167

Don’t feel bad, I did the same thing…

168

I getting errors:

16:11:37.546 CNTRLR « [Node 016] CommandClass Manufacturer Proprietary has 1 endpoints
16:11:37.566 CNTRLR Multi Channel: Error after interview:
supportedCCs is not iterable
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
TypeError: supportedCCs is not iterable
at new Endpoint (/usr/lib/node_modules/zwave-js/src/lib/node/Endpoint.ts:49:21)
at ZWaveNode.getEndpoint (/usr/lib/node_modules/zwave-js/src/lib/node/Node.ts:841:5)
at ZWaveNode.interviewCCs (/usr/lib/node_modules/zwave-js/src/lib/node/Node.ts:1433:26)
at ZWaveNode.interview (/usr/lib/node_modules/zwave-js/src/lib/node/Node.ts:1016:8)
at Driver.interviewNode (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:895:10)
16:11:37.724 CNTRLR « [Node 004] received location:
16:11:37.726 CNTRLR [Node 004] MultilevelSwitchCC: doing a complete interview…
16:11:37.729 CNTRLR » [Node 004] requesting current switch state…
16:11:37.983 CNTRLR « [Node 006] is named “Front Hallway”
16:11:37.984 CNTRLR » [Node 006] retrieving node location…
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

169

I have been trying to replace the old Zwave integration (thorugh configuration file) to Zwave JS. I deleted the lines in configuration file and deleted the integration.

When running the zwave JS plugin I get this error:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] config.sh: executing... 
[cont-init.d] config.sh: exited 0.
[cont-init.d] structure.sh: executing... 
[cont-init.d] structure.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:59:31] INFO: Successfully send discovery information to Home Assistant.
21:59:41.464 DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                      ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                        ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                       ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                      ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                      ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
21:59:41.506 DRIVER   version 6.5.0
21:59:41.509 DRIVER   
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
ZWaveError: The config has not been loaded yet!
    at ConfigManager.lookupSensorType (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:277:10)
    at ConfigManager.lookupSensorScale (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:288:23)
    at new MultilevelSensorCCReport (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MultilevelSensorCC.ts:408:43)
    at new CommandClass (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:108:13)
    at new MultilevelSensorCC (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MultilevelSensorCC.ts:205:1)
    at Function.from (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:331:15)
    at new ApplicationCommandRequest (/usr/lib/node_modules/zwave-js/src/lib/controller/ApplicationCommandRequest.ts:88:32)
    at Function.from (/usr/lib/node_modules/zwave-js/src/lib/message/Message.ts:222:15)
    at Driver.serialport_onData (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:1395:18)
    at SerialAPIParser.emit (events.js:315:20)
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Any pointers?

1 Like
170

I believe that is a known bug in the add-on.

try to install the add-on with the previous version. I think I’ve read 1.10 is good, v 1.11 is broken.

I don’t use add-ons so I can’t be more specific than that.

1 Like
171

Exactly the same error yesterday after updating to 1.11, I had to rollback.
I have great doubts about 1.11, can someone confirm that 1.12 will correct this??

172

Is this mentioned somewhere?? Had the same error.

173

yes, but I don’t remember where.

It’s been in the threads recently so you should be able to do a search and find it along with the bug report link.

174

Is there, I also mentioned it, thanks.

175

I personally do not recommend installing 1.11, spending lot of time to restore to 1.10. Shouldn’t be a good idea to remove 1.11 while a correction is made? Just for others…

176

Confirming that 1.12 Eliminates this error

177

Ok, meanwhile Martin, a developer of the plugin decided to block me from the github because I just say that I had the same problem. Kindergarten. Now as I wrote an email to him I’m afraid I will be banned from this forum too… Bye.

178

Don’t lie, that’s not why you were blocked and you know it. You’re safe here as long as you follow the COC.

179

I have a schlage door lock. It was connected to my previous setup via secure node. I added the network key into zwave js but for some reason it doesn’t load my schlage node. It’s there but as uknown.

I tried to remove the schlage node via the zwave js integration but it fails to remove it…Was going to re-add it afterwards.

180

Ok so had to remove the batteries and put them back for it to work.

181

Did the switch last evening. Everything is working great and faster. Thank you all for this great service and guide

182

Hi,
When I first tried switching I had the same issue my current /dev/ttyACM0 usb path wasn’t an option.

you mentioned you tried the second option, has everything okay, or have you had any more issues?

183

@phairplay
Yes, it works fine now with the second option.

1 Like