Migration from Zwave to Zwave-JS

Hey,
I have performed a migration from Zwave to Zwave-JS.

First I went through the migration wizard and ended up with:
image

Checked configuration.yaml and commented/removed:

#zwave:
#  usb_path: /dev/ttyACM0

and reboot.
Looks like it work (at least the function).

If I look under Integrations I can still see:
image

In the homeassistant.log I can see:


2022-03-16 20:57:57 INFO (MainThread) [homeassistant.components.zwave] Z-Wave USB path is /dev/ttyACM0
...
2022-03-16 20:58:24 INFO (SyncWorker_0) [homeassistant.components.zwave] Starting Z-Wave network
...
2022-03-16 20:59:35 INFO (Dummy-5) [homeassistant.components.zwave] Z-Wave network is complete. All nodes on the network have been queried
2022-03-16 20:59:36 INFO (MainThread) [homeassistant.components.zwave] Z-Wave ready after 71 seconds
2022-03-16 20:59:36 INFO (SyncWorker_0) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms

Checking under supervisor, I see:

Yesterday I tried to remove the integration but then everything broke…

So I wonder if Zwave-JS is operational and it is as it should?
Please advise

OK, new take tonight.
Based on previous…I switched to manual migration

  1. Backup incl. copied the files from /config
  2. Removed the zwave config from configuration.yaml
  3. Rebooted
  4. Backup
  5. The Z-wave integration is still in under integrations
  6. Z-wave devices still works
  7. Removed the z-wave integration (from webUI)
  8. Rebooted
  9. Installed Zwave-JS in supervisor
  10. ONE device was detected and working
  11. Rebooted
  12. Still no progress what so ever

NOTE: I did not have a zwave network key and nowhere to enter it in Zwave-JS

            {
                "entry_id": "b49b7ac7b63741eaa1063cbf52897f0a",
                "version": 1,
                "domain": "zwave",
                "title": "Z-Wave (import from configuration.yaml)",
                "data": {
                    "network_key": null,
                    "usb_path": "/dev/ttyACM0"
                },
                "options": {},
                "pref_disable_new_entities": false,
                "pref_disable_polling": false,
                "source": "import",
                "unique_id": null,
                "disabled_by": null
            },

I am a little pissed by this as HomeAssistant will remove the old Zwave in 2022.4.x

As you manually installed Z-WaveJS in Supervisor, you should also manually add the Z-WaveJS integration (choose not to install the addon as you already did that)
Depending on your network and this is a “new installation” (of Z-WaveJS) it might take some time to get devices interviewed and ready, stopping the addon during this process can impact device discoveries.

Let us know if manually adding the integration works.

@RickKramer tried different approaches and back and forth and finally it went working.
I have now switched between backups for a couple of days but right now it goes pretty good. Most automations been updated.
I have likely the biggest challenge in front of me and that is to get Fibaro RGBW Controller to work, just in case I have ordered a new controller (v2)

1 Like

If the firmware version of your Fibaro RGBW (FGRGBW 441) is earlier than 25.25, then it is buggy and won’t work properly in Z-Wave JS. You’ll have to send it to Fibaro to update the firmware.

Looks like I have:
Firmware: 22.22
Instead of sending it to Fibaro it is probably easier/cheaper to get a new controller (already ordered).
This mainly because I only have one of these

Manually adding it and after some attempts it worked and I have most of the Zwave network up and running