primal lantern
I started the Home Assistant Connect ZWA-2 installation and it failed. Now my Z-Wave JS configuration won't load. I tried reloading, reconfiguring, and restarting. Nothing works to bring it back online. The error I get on reloading is "Failed setup, will retry: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.1', 3000)]".
Any ideas about how to recover?
upbeat crypt
I would look in the add-on logs to see why it's failing to start
primal lantern
I would look in the add-on logs to see why it's failing to start
Thanks for that tip, I see this but it's not helping me to understand what to do next:
14:39:58.439 SERVER [ERROR] failed starting driver.
ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)
at Driver.openSerialport (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1835:9)
at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1598:5)
[18:39:59] WARNING: Halt add-on
upbeat crypt
It means something else is using the port. Are you running Z-Wave JS UI at the same time?
primal lantern
It means something else is using the port. Are you running Z-Wave JS UI at the s...
No, Not running Z-Wave JS UI. I unplugged the ZWA-2 from the USB port on my Home Assistant Yellow. The /dev/ttyAMA1 device was assigned to the 800 Series Long Range GPIO Module. I didn't remove that (per the instructions). So the hardware is exactly as it was before. No changes. I just can't get the Z-Wave JS integration to start.
primal lantern
It means something else is using the port. Are you running Z-Wave JS UI at the s...
Update: I recovered by performing a reconfiguration and switching it back to /dev/ttyAMA0. I said in an earlier message that the current GPIO-based Z-Wave adapter was on /dev/ttyAMA1 but that's not true. It's at ttyAMA0. When the reconfiguration dialog came up, it was set to ttyAMA1 which I suppose is where it was trying to migrate to for the USB port that the ZWA-2 was plugged into. When the migration siezed up, I suppose it had switched the config to the new port. In any case, I'm breathing a sigh of relief that I may not have to rebuild my entire Z-Wave network. At least not today. I had hoped the ZWA-2 upgrade was going to be smooth but I'll set aside a rainy day and try again then. Thanks for your help.
upbeat crypt
Weird. The ZWA-2 does not have path /dev/ttyAMA0 or 1
primal lantern
Weird. The ZWA-2 does not have path /dev/ttyAMA0 or 1
Very weird. On Home Assistant Yellow, which device would you expect ZWA-2 to appear on when connected to the two USB-A ports?
primal lantern
Weird. The ZWA-2 does not have path /dev/ttyAMA0 or 1
I found the problem. The USB-C cable that shipped with the ZWA-2 was bad. I swapped it for another USB-A to USB-C cable I had, and it was able to complete the migration.
upbeat crypt
800-series USB controllers are usually /dev/ttyACM<N>.
HA will pick the /dev/serial/by-id path regardless, AFAIK.
Only GPIO devices use /dev/ttyAMA<N>.
primal lantern
Only GPIO devices use `/dev/ttyAMA<N>`.
Very helpful. Thank you. Evidently, when the bad USB cable caused the ZWA-2 to disappear during the setup, I must have tried to assign the wrong device. When I backed it out, that assignment was not correct for the old GPIO-based Z-Wave radio. After replacing the UCB-C cable that shipped with the ZWA-2, the setup went smoothly. Thanks again for your help.
upbeat crypt
Odd, glad you figured it out.