Moving from Zwave JS UI to Zwave JS

I’ve looked and asked in other threads. Can someone help me understand how to go from Zwave JS UI → Zwave JS? I want to migrate to a Zooz 800 controller and I cannot use the migration tool in the ZwaveJS integration when using UI. I’ve been told just do the steps in reverse. I can’t figure out how to do that without loosing all 70 Zwave devices and information.

I think it would just be easier to do the migration in Z-Wave JS UI. There are several guides to do so.

  1. Z-Wave JS integration docs: https://www.home-assistant.io/integrations/zwave_js/#how-to-migrate-from-one-adapter-to-a-new-adapter-using-z-wave-js-ui
  2. ZWA-2 guide, it’s the same as above and works for every controller: https://support.nabucasa.com/hc/en-us/articles/29529265751965-Migrating-an-existing-Z-Wave-network-to-Home-Assistant-Connect-ZWA-2. See Scenario 2 steps. The one explicit step missing there is to be sure and re-configure the USB path/serial path to point to the new controller.
  3. Or here’s a video with the same steps if that’s more your style (timestamp for ZUI migration linked).

The thing is, I moved to UI to get zwave associations to work, which don’t really. Or, they do but automations are just easier/better. Other than that, UI information is lost on me. I’d prefer the easier, more straightforward JS addon. That said, I can’t figure how to easily go back.

Well, the good thing is you don’t need to use ZUI if you don’t want. You can keep it installed for the zwave-js-server and just stick to the HA UI. Besides the NVM migration it’s identical. You can pretend ZUI doesn’t exist.

That said, if you really want to switch you can try going in the reverse of this guide: Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community)

Basically:

  1. Disable the Z-Wave integration
  2. Download cache files from ZUI Store (Backup will do it), and copy your security keys
  3. Stop ZUI add-on
  4. Install the Z-Wave JS add-on manually
  5. You might need to start the add-on, then stop it, to create the addon data directory
  6. Copy the cache files to the addon cache directory
  7. Start the add-on and configure it with USB path and security keys
  8. Re-add the Z-Wave integration but enable the Supervisor add-on checkbox

Just wondering: JS UI is built on top of JS, so why you need JS if everthing JS has is kinda available in JS UI?

The information in UI makes no sense to me. I am not a computer wiz, just a hobbyist. If I add things in JS, the names don’t track in UI, which my OCD requires that they do.

that i can relate to :smile:

Thanks for this, I was able to get migrated to my new Zooz stick. Now, I ordered the new HA tower and will migrate to that to test.

I guess I don’t need to move back away from UI…I’ll try to ignore it.