After upgrade to Zwave JS UI to version 7.1.0 I have got the same situation. Restoring to the restore point which was made by the upgrade did not work. Restoring to a full back-up made last night did also not remediate the problem
I get the message Failed setup, will retry: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed (‘172.30.33.2’, 3000).
The log info selected for Zwave JS UI shows normal behavior.COntinuously updating values. The Zwave JS log shows : Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port.
The entities are not available for display in the dashboard.
I do not know what to do next, because a restore did not help. And I have the feeling that it is a configuration mismatch caused by the upgrade.
You can’t use both the core app and Z-Wave JS UI community app at the same time. Pick one of them. Currently you are using the core app. Recommend staying with that since it includes Z-Wave JS UI and the community app will eventually be deprecated.
Sorry, but I am not sure what that means. My configuration always worked until today. I have 27 Zwave nodes and hundreds of entities configured.
I can still see all the nodes and is I select zwave JS and these are all updated. See included picture My dashboard refer to the entities which seem not to be available anymore.
I am very confused why this happened. Please provide steps to take (hopefully not reconfigure all the dashboards and the automation) to make it work again. Thx in advance.
Which means you have actually been using the Z-Wave JS core app, not the community app. Installing the Z-Wave JS UI community app should not have been done. This dual app configuration has never worked, and you were just lucky.
I think you can just uninstall the Z-Wave JS UI app, but you should make a backup before doing so.
I uninstalled Zwave JS UI. I now have no longer the ability to check from the menu on the left with the many details. And entities are (still) no longer provided by the zwave JS integration.
It seems that 16 out of 27 devices are not included. With 627 entities in an unknown state a reconfiguration effort will be immense. For now I will revert back to the the backup made just before removing zwave JS UI and will execute a restart. A lot related to zwave will not work but at least other essential automations will. I will do further research tomorrow.
All suggestions a still welcome. It disturbs me very much that this update caused these problems while everything worked well yesterday. Even if it should not have.
It seems that 16 out of 27 devices are not included.
I think that’s a bad translation. In your case it surely means 16 of the devices are “not ready”, because your Z-Wave JS UI community app made a mess of things. Try restarting the core app first. If that doesn’t work, you may need to re-interview them. Look in the Web UI for a better view of things.
It disturbs me very much that this update caused these problems while everything worked well yesterday. Even if it should not have.
This is actually a normal occurrence when you are running both apps at the same time (invalid configuration). Search the forums and you’ll find numerous topics.
My reply was to the other poster to address their problem, which seems unrelated.
This message would indicate a configuration problem, as it should be connecting to ws://core-zwave-js:3000 instead. What happens if you fix that?
Check the app logs, if the integration cannot connect it would be an issue there. Memory on a RPi3 is not usually enough with multiple apps and integrations, so that could be a concern.
I de-installed ZWAVE JS UI app. I watched the netwerk and some nodes did not become online right away (17 out of 27)
Waited (went to sleep). During sIx hours remaining nodes were reinterviewed. Many nodes are now online. (5 out of 27 are still left and being reinterviewed. 4 out of 5 are sleeping).
I am sure I will get the remaining back in the network again
I needed to toggle the side bar on because the uninstall of zwave js ui removed it. Now I can see the details of the nodes again.
