Z Wave conversion from "Z Wave" to "Z Wave JS UI" issues

[zxplod]

Hi! I was using the HA native Z-Wave and then decided to upgrade to Z Wave JS UI. I am semi new to HA and having some odd issues if anyone can offer assistance?

Am I still supposed to have 4 things installed including “Z Wave”, “Mosquito Broker”, “Z Wave JS”, “Z Wave JS UI”? This seems redundant, and I am having some odd issues, so just making sure I was not supposed to remove something.

Thank you!

[freshcoast]

ZHA is Zigbee, and Z-Wave JS UI is Z-Wave. What do you mean by “upgrade”? Did you replace all of your Zigbee devices with Z-Wave? You can’t just switch between these software which support different protocols.

[zxplod]

Good catch! Sorry about that. I meant the build in HA “Z Wave”, not ZHA. I edited my post above. Thank you!

[freshcoast]

Ok, that makes a bit more sense.

Now when you refer to “native Z-Wave”, are you referring to the long obsolete OpenZWave-based integration (legacy Z-Wave), or the Z-Wave JS official add-on? If you are referring to the latter, you can follow this guide to switch:

Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community)

Introduction This guide describes how to switch from the Z-Wave JS official add-on to the Z-Wave JS UI HA Community add-on, without losing any downtime caused by the re-interviewing of nodes. In this guide, Z-Wave JS UI will henceforth be abbreviated as ZUI. Who is this guide for? This guide is for HAOS add-on users who have already installed the official Z-Wave JS add-on and the companion Z-Wave integration, and desire extra functionality that isn’t provided by HA, such as: Adding and remov…

If you mean OpenZWave, there’s no migration path. You can just install Z-Wave JS UI and start over. You don’t need MQTT.

[zxplod]

Haha @freshcoast . I for sure got mixed up in all the lingo.

So I do not misspeak again here are screenshots of what I have right now…