#Error using a ZWA-2

1 messages · Page 1 of 1 (latest)

fallen condor
#

I recently installed a ZWA-2 with Home Assistant and it seemed to work really well. I found Z-Wave JS UI that appeared to have more features so since I was just doing testing, I removed my z-wave devices and tried to switch. I kept running into the problem where get an error "Failed to start the Z-Wave add-on". The log shows:
Failed to initialize the driver:

TypeError: Cannot read properties of undefined (reading 'valueDB')
    at ZWaveController.get valueDB [as valueDB] (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:791:44)
    at ZWaveController.initNodes (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1827:34)
    at Driver.initializeControllerAndNodes (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2040:4)
    at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1717:5)

I also found /dev/serial/by-id/usb-Nabu_Casa_ZWA-2_1... exists and I also found the ZWA-2 with: [core-ssh ~]$ ha hardware info |grep -i zwa.

[core-ssh ~]$ ls -la /config/.storage/z* did not return any files.

I tried a different Raspberry Pi loaded with Home assistant and received the same error so I assume the ZWA-2 is the problem and not Home assistant.

I am somewhat new to Home Assistant so I may be missing something obvious but I have spent many hours installing, uninstalling, rebooting, etc. I quickly discovered I was not supposed to have Z-Wave JS and Z-Wave JS UI active at the same time but removing one or the other didn't help.

Does anyone have any suggestions on what I can do to track down the problem? Is there a factory reset option for the ZWA-2? Thanks!

quick basalt
#

@summer flame Any ideas here?

summer flame
#

Can you share the entire addon logs from startup until this error? Ideally set it to loglevel "debug" first.

fallen condor
#

The debug log file is attached.

Also if it helps, I tested https://support.nabucasa.com/hc/en-us/articles/30248838949405-Running-the-adapter-recovery-tool
I selected - Recovery adapter and clicked Connect.
ZWA-2 (ttyACM0 ) - Paired and clicked Connect.
The blue light came on and I received the following error message:

Connection failed
Unable to establish a connection with your ZWA-2 adapter. This issue cannot be recovered automatically.

Please check your connection and try again, or contact support if the problem persists.

I tried it on both an Ubuntu machine and Windows with the same result except Windows connected with Nabu Casa ZWA-2 (COM3) - Paired

I also tried a different known working USB cable.

📎 Z-WaveJS-ZWA-2.log
Nabu Casa
Running the adapter recovery tool on Home Assistant Connect ZWA-2

Prerequisites

Home Assistant Connect ZWA-2.
USB data cable to connect the Home Assistant Connect ZWA-2 to your computer system. If you are unsure if your cable is a data cable, we recommend using...

summer flame
#

Did you start your network from scratch or did you do a migration? The logs show some odd information - which trips up Z-Wave JS during the startup.

#

If you migrated, please send me a backup of the old controller. I'd like to understand what happened there.

fallen condor
#

I have a lot of older Z-wave devices I'm using with an OpenHAB system with an old Aeotec Z-Stick. I unpaired 4 of them and moved them over to the ZWA-2 in Home Assistant. Since I'm somewhat new to Home Assistant, I experimented a lot at first adding and removing devices. After I found everything worked great, I decided to start from scratch and add all similar devices at the same time. I unpaired all the test devices and started over. I don’t know if it is relevant but I later found there was one device that did not get unpaired. I removed the add-on and told it I was starting with a new network. At some point I discovered Z-Wave JS UI but think the issue may have started prior to making that change.

I don’t know all the steps to recreate the issue and I don’t have any backups. Before I try the Erase NVM, is there any data I should collect to determine what went wrong?

I tried link you provide and received an error – Failed to start the driver. The only option available is HW Reset to Bootloader. I assume this is the option I want?

summer flame
#

Ok so it used to work in the beginning. Wonder how you managed to get your controller to have the (invalid) node ID 239 though. I've never seen that. Maybe an SDK bug.

#

Given that Z-Wave JS fails to start in that scenario, we can't collect info without working around the issue.

#

I'd say perform the HW Reset to Bootloader, after which you should have the option to erase the NVM, then start application.
That way you can at least use it again.