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

[Shelby67 (Mattias)]

Hi, I would like to switch from Z-wave JS to Z-wave JS UI, but before I do, I want to ask, because I also have Zigbee2MQQT installed, will the Z-wave JS UI work fine together with Zigbee2MQQT? or is required some extra steps?

[freshcoast (Z-Wave AI Bot)]

They are completely unrelated. Just make sure you use the serial/by-id USB path to avoid using the wrong controller.

[Shelby67 (Mattias)]

Thank you very much

[robmcd (Rob McDonald)]

This is amazing. Followed exactly and worked flawlessly!

[DoTheEvolutionPJ]

Working perfectly - looking over the comments i see that names and locations don’t transfer over - frustrating but only have about 15 devices so can pull up side by side from HA to the UI and add them back in.

BUT I thought the UI was to visually get a better experience along with other features, ie when looking at the graph all i see are NODES and not names - will i have to manually add Name and Location everytime I add a new device??

[freshcoast (Z-Wave AI Bot)]

@DoTheEvolutionPJ

BUT I thought the UI was to visually get a better experience along with other features, ie when looking at the graph all i see are NODES and not names - will i have to manually add Name and Location everytime I add a new device??

I must be misunderstanding your question, because how else will name and locations be added to the nodes unless you set them???

ZUI makes it easy as you can preset them either during classic inclusion or with SmartStart. Unfortunately you still need to set them, it can’t read your mind.

[DoTheEvolutionPJ]

So I had everything set up in HA with Z-Wave JS, I then migrated to UI and everything worked flawlessly per the guide - but the Names and Locations didn’t migrate over from HA > UI.

[freshcoast (Z-Wave AI Bot)]

Ok. Then unfortunately yes, you need to set them manually in ZUI if you want them synced. When you add nodes in the future, use ZUI and then they will propagate to HA automatically.

I will add, I think if you want to do it programmatically or with a text editor, you could export the nodes.json from ZUI, then hand edit/script it to add the names/locations, then import it.

[DoTheEvolutionPJ]

Last question of the evening - Anyway in HA to view an entire list of devices (with the names and areas) but also the Node ID - this way I can do split screen and update them in ZUI? Otherwise have to click into each device

[freshcoast (Z-Wave AI Bot)]

I use a Markdown card in a separate dashboard view.

Expose NodeID on the Zwave devices

Here’s a Markdown card I’ve been using for awhile now. I took inspiration from another post (which I can’t recall). [image]

Markdown card YAML

type: markdown content: > ## [Configuration](/config/zwave_js/dashboard?historyBack=1&config_entry=ef37a31dab38dcfee3fd3d1ecd1f3692) ## [Nodes](/config/devices/dashboard?historyBack=1&domain=zwave_js) {%- set ns = namespace(nodes=[]) %} {%- for dev_id in integration_entities('zwave_js') | map('device_id') | uniq…

[DoTheEvolutionPJ]

So back to naming - I updated the Device Names in ZUI restarted HA and the names did not update in HA. I understand the entity_id won’t change but the name should… what am i missing

[freshcoast (Z-Wave AI Bot)]

Names only change if you haven’t modified them in HA. The Markdown card will show that.

[DoTheEvolutionPJ]

But I saw a post by you a while ago and thought from above if you change in ZUI it will update in HA after a HA restart.

you can change name and location in ZUI at any time, and if you reload the integration in HA or restart HA, the device name, device location, and entity friendly names will be updated to match ZUI. Entity IDs will not be changed though, by design.

[freshcoast (Z-Wave AI Bot)]

That’s only when you haven’t customized names in HA. Most people would be upset if their custom names were changed.

[DoTheEvolutionPJ]

Ahh so once I mess w/ the name in HA that’s it - I understand that but the ZUI is easier to change update things so thought it would transfer that. So basically once I enroll a device be it in HA or ZUI the name and Area are set and if I change in either HA or ZUI it won’t change on the other and only way if i wanted to change a name and have both the same would be to do it manually on both…

[freshcoast (Z-Wave AI Bot)]

Right, the default name provided to the integration doesn’t override your custom one.

[freshcoast (Z-Wave AI Bot)]

Here’s a procedure to copy names from HA into ZUI:

Copying device names into Z-Wave JS UI

Here’s something I quickly wrote up, after seeing this requested many times. Let me know how it goes if you try it. Copy and paste this code into the Dev Tools Template editor: {%- set ns = namespace(nodes=[], export={}) %} {%- for dev_id in integration_entities('zwave_js') | map('device_id') | unique %} {%- set node_id = (device_attr(dev_id, 'identifiers') | first | last).split('-')[1] %} {%- set ns.nodes = ns.nodes + [(node_id | int, dev_id)] %} {%- endfor %} {%- for node_id, dev_id in n…

At some point I’ll add it to the guide, but you would save the json file after step 1 (before disabling the integration) and import it after step 7 (ZUI is setup).

[BJonas]

I use JS as the primary interface. I have jsui installed with the MQTT gateway not enabled. I use jsui when it is simpler or the only way to access a capability. Not sure why this works if the gateway is off, but it does. Switching to jsui seems complicated and has the risk of things not going well and having to rebuild things, so holding off for now. The one thing I do want is to backup the NVM on my aeotec gen5(1.2) usb controller in case of a hardware failure. Given my usage of the two addons can I use jsui to do the backup and restore to a new usb stick in case the one I am using fails even though I am still primarily on js?

[freshcoast (Z-Wave AI Bot)]

No, don’t use two add-ons. No point at all.

[SCRich]

I am failing at this point. I do not see show or ENABLE. ANd what is the Z-wave card the COMMUNICATOR ? Even IN the card I do not see an enable choice.