I am receiving the following error message from Z-Wave JS. I’ve searched the archives and haven’t found this error. My Z-Wave (GE/Jasco) switches are operating correctly, as are my automations involving these switches. I am not using the IP address noted in the error message. I had set up to use the call noted in the error as “cannot connect to host”.
Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.3', 3000)
I’ve updated to the latest HA OS, latest HA Core and latest Z-Wave JS, If I specify core-zwave-js:3000 for the Z-Wave communications, I receive the same error. I don’t see in the documentation that the IP call to port 3000 is a requirement. I tried that and it didn’t seem to eliminate the problem.
What a coincidence. This just happened to me as I upgraded to the latest HA OS and HA Core as well, and migrated to Z-Wave JS. It was working okay but suddenly started throwing this error after I restarted the addon.
What I ended up doing was reboot the host (I am using a RPi4) and it was all working again.
@tmpugh Thanks for the explanation. I have never run Zwave2mqtt… is it a requirement? If I load zwave2mqtt will the error clear? Everything ZWave that I do use seems to be working fine, except for this annoying error.
Is the error repeating, or is there only one log entry? If you upgrade or restart the add-on while HA is running you will always see the error, it’s perfectly normal.
@tmjpugh I have only one copy of ZWaveJS running…? If that’s what you’re asking me…?
@freshcoast The error is does not recur, if that’s what you mean…? I don’t recall what sequence I used for the updates, but it’s certainly possible you’ve caught exactly what I did. The error did recur…I just don’t remember the start sequencer I used.