Rolling back worked for me
Just updated to 0.163 and so far z-wave is working OK, hopefully this was the fix!!
1 Like
it was the fix 
apologies for the issues
1 Like
Anyone interested, issue was tracking here ZWave JS upgrade from 1.61 to 1.62 broke my installation. · Issue #2540 · home-assistant/addons · GitHub, but as mention 1.63 upgrade resolves problem.
I upgraded to v.64 still having same issue error - Cannot connect to host core-zwave-js:3000
3 Likes
I have been plagued by this for the last two days. Last night, I restored from a backup and it worked until this afternoon. What is telling the device to use this IP Address? It does not exist on my network:
Retrying setup: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed (‘172.30.33.1’, 3000)]
having a similar issue with
Retrying setup: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Name does not resolve]
Also having similar issue. After Updating Z Wave JS UI addon to 1.11.0, I got the following: “Retrying setup: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Name does not resolve]” repeated over and over in the Z Wave JS integration Box on the Integrations Page. All Z Wave devices stopped communicating with Home Assistant. Could operate them from the Z Wave JS page in the side bar, but entities reported as unavailable in the Developer Tools - States Page. Reloaded Backup - Issue resolved, performed update again, problem persisted. Logs for the Addon showed no issues.
1 Like
You are still configured for using the official add-on, not Z-Wave JS UI.
or
for instructions on switching to ZUI.
My Z Wave network has been operational for months. I don’ t think it can be a configuration issue. Again reloading my backup restored HA’s connection. The update is what broke it.
1 Like
Please pay attention to the error message. core-zwave-js:3000 is the URL of the official add-on, not Z-Wave JS UI. So you are not using ZUI. If you want to use ZUI, you need to reconfigure it as in the posts above. Also: https://www.home-assistant.io/integrations/zwave_js/#can-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on
Ok, I have no idea what exactly I did, but I think it worked. I couldn’t follow the instructions verbatim because Z-Wave JS UI was already running with it’s own set of keys and everything. So, I disabled the integration, reinstalled it with the “Use the Z-Wave JS Supervisor add-on” box unchecked, left the url what it was, got the “device already configured” message, then uninstalled the official addon, and enabled the integration. Checked that everything was still working (it was), and did a complete backup (cuz I’m OCDish). I then did the update, everything still worked, so for good measure I did a complete restart of HA. And it seems we are good (knock on wood). Have no idea what all happened, but I really appreciate your help!! Thx…
Same issue here with 1.11.0 and a partial backup restore did not correct it. I’m hoping to have some time this weekend to look at it and trial some of the uninstall/reinstall and enable/disable of this addon and the offical one. I intend to track the steps I use to resolve and will report back. If it starts working again before that due to another update or seemingly arbitrarily then I will just leave it in that working state.
Hmm, the issue seems to have gone away prior to the debugging I intended to do. Thus I’ll simply leave it in its currently working state unless it reoccurs. These steps do show that the addon update alone may not be the cause. HAOS on RPi in case it helps anyone:
.
0) full nightly backup apr18
- backup for update core 2023.4.4 to 2023.4.5
- backup for update zWave JS UI 1.10.1 to 1.11.0
- full nightly backup apr19
- Observe subset of devices not reacting to automation
- restart home assistant, problem persists
- restart system, problem persists
- observe same error reported on zWave JS integration as prior user above
- restart system, problem persists
- restore partial backup from #2, problem persists
- restart system, problem persists
- backup for update zWave JS UI 1.10.1 to 1.11.0
- problem persists
- make post above in this forum, intend to debug per links above later this weekend
- backup for update TerminalSSH 9.6.1 to current (should be irrelevant?)
- restart system, problem persists
- make backup
- restore to full backup from #3 (note post 1.11.0 update)
- problem is still occurring here
- did not perform any reboots here but probably should have
- backup for update TerminalSSH 9.6.1 to current
- problem resolved
.
I was surprised to see the issue resolved here as I was mainly just trialing a restore from last full backup plus updating all components as a sanity check. I expected to be rolling back to the last full backup predating the 1.11.0 update, that would be the backup in #0.
If you are seeing error messages with core-zwave-js:3000 in them and you are using Z-Wave JS UI, then:
If you already have ZUI installed, then you can skip the add-on install steps (steps 2 and 3 in the official instructions) and just re-configure the integration as stated in the remaining steps.
1 Like
I’m having this issue reported where my zwave Js UI is in a borked state. However I’m not sure what the issue is.
Admittedly it’s been so long since I set this up so I’m always confused with all the adding. I do use zwave JsUI.
My versions:
- Zwave Js UI: 1.15.2
- Zwave JS: 0.1.185 (installed this while trying to debug what was going on but have shut it down)
- Zwavejs2mqtt: ??? ( I cannot find where this is)
What exactly am I supposed to rollback?
Updated to zwave js ui 1.15.4 - totally broke zwavejs. Restarts did not help. I revered back fine with no issue. Appears to be a similar issue as earlier. Will live on 1.15.3 until I hear otherwise.
1.15.4 also brought down my z-wave network, needed to revert back
I just restored back to Zwave JS UI 1.15.3 and no nodes are listed in the UI 
This is a part of my addon logs, not sure if this helps gives any info.
2023-08-07 20:06:02.026 INFO APP: GET /health/zwave 200 0.412 ms - 2140
2023-08-07 20:06:02.986 INFO APP: GET /api/settings 304 1037.017 ms - -
2023-08-07 20:06:03.082 INFO APP: GET /api/auth-enabled 304 0.834 ms - -
2023-08-07 20:06:12.107 INFO APP: GET /api/settings 304 1025.230 ms - -
2023-08-07 20:06:12.223 INFO APP: GET /api/auth-enabled 304 0.773 ms - -
2023-08-07 20:06:32.537 INFO APP: GET /health/zwave 200 0.372 ms - 2140
2023-08-07 20:07:02.985 INFO APP: GET /health/zwave 200 0.350 ms - 2140
2023-08-07 20:07:12.208 DEBUG SOCKET: User disconnected from s8b7fO5FiQjlMNaSAAAF: transport close
2023-08-07 20:07:12.208 INFO Z-WAVE: Removing user callbacks
2023-08-07 20:07:34.171 INFO APP: GET /health/zwave 200 0.397 ms - 2140
2023-08-07 20:07:34.478 DEBUG SOCKET: New connection JnJ0qV-zqVodCCmkAAAH
2023-08-07 20:07:34.479 INFO Z-WAVE: Setting user callbacks
2023-08-07 20:07:34.501 DEBUG SOCKET: Event INITED emitted to JnJ0qV-zqVodCCmkAAAH
2023-08-07 20:07:38.033 DEBUG SOCKET: User disconnected from JnJ0qV-zqVodCCmkAAAH: transport close
2023-08-07 20:07:38.033 INFO Z-WAVE: Removing user callbacks
Am I supposed to enable this setting?
Looks like it’s been fixed. Z-Wave won't start up with 1.15.4 · Issue #553 · hassio-addons/addon-zwave-js-ui · GitHub