attempting to migrate from existing core install to a new supervised install.
existing core info:
Core 2024.10.2
Frontend 20241002.3
zwave-js
new supervised info:
Core 2025.3.4
Supervisor 2025.03.3
Operating System
Frontend 20250306.0
zwavejs-ui
zwave device is a tubeszb-zw POE chassis with the zooz ZAC93 installed
how do I move the the zwave tubeszb/zac93 to the ‘new’ zwavejs-ui?
in setting up the ‘new’ zwavejs-ui from the zwavejs-ui web page it won’t let me move past the setup without the security keys. Is there an easy way to do this? or do I have to burn it all down and start a brand new from scratch default-everything install?
If you can no longer make a backup, but you have the store directory available, you could manually create a zip file and then restore it. If you don’t have access to the store directory anymore, you’ll have to start over.
That doesn’t make any sense, the word “zwave-js” doesn’t carry any meaning on its own. Can you explain how you were running Z-Wave JS before? In a plain core installation, most people are using Z-Wave JS UI.
Since it was a core install and core doesn’t do addons, I had to set up a separate docker for zwave-js.
full disclosure: I did not know about zwavejs-ui at the time, and what to use where and when was very unclear. I didn’t understand exactly what ‘supervised’ was other than just another morph of home assistant OS/haos and saw that it was being abandoned anyway in favor of home assistant OS. Hence that’s part of the apparent confusion and mess on my side.
If I have to burn it all down again, well, so be it. Thanks.
I don’t know what docker container you are using, so it’s impossible to say. However, the settings will for sure be incompatible. You’ll need to manually transfer them over. For example, the old container should have a way to configure keys, you just need to copy the keys over to ZUI.
The container you’re using should have a “store” or “cache” directory, in that directory are *.jsonl files. You can copy those from your old install into Z-Wave JS UI, before you configure it. Those files are the Z-Wave driver cache, so if you provide those at least you won’t need to re-interview devices.
Copy *.jsonl files from old install
Install Z-Wave JS UI add-on
Before configuring add-on, upload *.jsonl files in ZUI using the Store page
Do I need to move or recreate the jsonl.lock directories in the new zwavejs-ui container? how about moving the users.json settings.json and nodes.json?it looks like those have useful info as well. Notably, settings.json has the security keys in it.
This is good! I feel better already.
thanks!
~/zwave-js-store $ ls .json
f55193f6.jsonl f55193f6.metadata.jsonl f55193f6.values.jsonl nodes.json settings.json users.json
yeah, put it down to confusion and not being able to figure out the zwave-js vs zwavejs-ui. In any case, there was no zwavejs-ui entry (no addons in core) in the old core install. So no way that I could figure to get to the zwavejs-ui. I understand the confusion…I remember being very very frustrated trying to determine the whole zwave ‘system and components’, much less the howto …well I seem to be on the right track now.
I do thank you very much for working through this with me. I’ll post how it turns out.
