Zwave issues on NEW INSTALL, not a migration install. | Home Assistant | Page 1

west grove Mar 10, 2026, 6:35 PM

#

Long time Z-wave user.
Looking for a new platform that is NOT Windows based.
Currently successfully running Homeseer4, lots of devices.
I purchased a Home Assistant Green kit and a ZWA-2 antenna.
I purchased some new in-the-box Inovelli switches.
I plug in the Home assistant green unit, start it up and create an account.
I plug in the antenna, and head over to the integrations page. See the Zwave antenna. Click on it. Great.
Go to apps.
Download and install Z-wave-UI.
Go to the upper right corner, click the blue ‘I’ information icon and see that I have TWO zwave applications running.
Z-Wave-UI v 11.12.0
Z-Wave-JS-UI v 15.21.0
See attachement.
I also can’t get any of my new devices added.
Am I missing something here? I have a number of failure modes, the most common being "Device provisioned but not added to the network". I do understand this, and no matter what I do, I can't resolve it. Power cycle, leave it along, put it in manual inclusion mode. None work.
I know there used to be two apps. UI and JS-UI. I’ve gone down that rabbit hole, and decided to just factory reset everything and start fresh. I had some luck using the 'factory UI' version initially. the JS-UI version worked, and looked nice, but can't add devices.
The description at the top of the post is what I’m seeing ‘out of the box’ after a full factory refresh. ANy zwave device that had been added were either gracefully removed, or if not fully provisioned, deleted before the factory wipe.
Was there some change where the two Z-wave apps were joined? What software version is that, and can I load the 'previous' factory software version on my controller from somewhere?
How can I delete an app that I’ve not downloaded or installed (In this case Z-wave-JS-UI 15.21.0)?
Is there some world where my ZWA-2 is NOT being completely factory reset?
Is there some world where the Home assistant green is NOT being completely factory reset?
TIA. appreciate it.

lyric pewter Mar 10, 2026, 7:14 PM

#

You shouldn't install the Z-Wave JS UI app

west grove Mar 10, 2026, 7:19 PM

#

lyric pewter You shouldn't install the Z-Wave JS UI app

Thats the rub in the OP. I did not install the Z-Wave JS UI. Thats the problem here. I ONLY installed Z-wave JS. It is the only app shown as installed. HOWEVER, when you click the info button, it shows BOTH applications.

#

To be very clear, I flattened everything specifically for this test, and brought it all back online one by one, and specifically ONLY loaded the one app. But both show up when you click the info button.

lyric pewter Mar 10, 2026, 7:55 PM

#

But you said "Go to apps. Download and install Z-wave-UI."

#

So you skipped that the second time?

#

The info button is not showing HA "app" versions.

#

The core Z-Wave JS app includes Z-Wave JS UI. You don't have to use it if you don't want to. For clarification on version numbers, you can view https://zwave-js.github.io/which-version/. The screenshot shows the core Z-Wave JS app, based on the versions displayed.

lyric pewter Mar 10, 2026, 9:50 PM

#

There's no such thing as "Z-wave-JS-UI 15.21.0". If you look closer it just says "Z-Wave JS 15.21.0". That's the driver version.

#

So as long as all you have installed is the core Z-Wave JS app, and not also the Z-Wave JS UI community app, then you're good from that standpoint.

west grove Mar 10, 2026, 9:57 PM

#

OK. So the info button is showing me the driver version and the UI version. that makes sense. All I have installed is the 'core Z-wave JS app', NOT the Z-wave JS UI app. I flattened the whole system and started over with help from this page:
https://www.home-assistant.io/integrations/zwave_js/
for that very reason. Just to make sure I was using the (for lack of a better word) official version with no other things installed.
Thanks for the info. I'll take a look tonight and make sure I have all my assumptions correct.
WHen I go to https://zwave-js.github.io/which-version/, it does show 4 items:

Z-Wave JS Driver
Latest version:
15.21.1

Z-Wave JS UI (HA Community App)
Latest version:
7.0.0
Z-Wave JS UI version:
11.11.0
Driver version:
15.20.1

Z-Wave JS UI (Standalone)
Latest version:
11.14.0
Driver version:
15.21.1

HA Core App
Latest version:
1.0.1
Z-Wave JS UI version:
11.12.0
Driver version:
15.21.0

The fact two of them are the same name seems odd, but as long as I know the Community one is in the Community apps area aand the 'Standalone' is in the other download area, I should be able to tell the difference.

Home Assistant

Z-Wave

Instructions on how to integrate Z-Wave with Home Assistant via Z-Wave JS.

#

and agreed - It appears I have JUST the HA Core App installed currently. This is where I 'assume' I want to be to start testing my new system.

lyric pewter Mar 10, 2026, 10:54 PM

#

"Device provisioned but not added to the network" means a SmartStart QR code has been scanned in HA and it's waiting for it to be provisioned (added to Z-Wave network).

west grove Mar 11, 2026, 12:40 AM

#

OK. Can confirm. The only app I have installed (in total) is the Z-wave JS app. Poked around, looks like that jives with the drivers I'm seeing in the info window.
Can confirm 2 switches I scanned and put into 'provisioning' mode are now showing up. Thats about a 20+ hour provisioning time.
Seems long to me. Per the instructions above it should take 'seconds to minutes'. I'm seeing extremely longer times.
I'm coming from a fully functioning Homeseer4 system that adds devcies 'as expected' in that seconds to minutes range. Something with this HA kit is really taking a long time.

I'll try a few more switches tonight and see if I'm still getting the wildly long add times. As far as setup goes, it appears Home Assistant and the ZWA-2 are properly configured, it's just taking ages for the devices to be added.
thanks again for all the help.

lyric pewter Mar 11, 2026, 12:49 AM

#

Usually takes seconds for me. If the entry is not ready prior to the device being powered on the device could try too early and either give up or back off

west grove Mar 11, 2026, 1:09 AM

#

I"m adding a Inovelli switch now. The smart start wouldn't work, so I tried the old school inclusion method. Settings-Zwave-Add devicel-put device in inclusion mode (Triple tap favorites button). That worked immediately, the software saw it immediately, but its going on about 5 minutes with the spinning wheel of "Getting device information".
This particular switch is in my living room, less than 20' from the antenna.

#

I should add the antenna firmware is on 1.2, showing 'latest version' in the description

#

I aborted and 'removed foreign device'. So it tries to add it, it just takes an eternity. last add was going on 15 minutes

#

OK. Dunno whats up here, but it seems fishy.
Aborted. Removed. Closed HA on my laptop. Grabbed mobile phone. air gapped the switch in question (above, with failed add). Settings-zwave-add device. Made sure switch was off and air gap switch was pulled. Clicked in the air gap to power it on. Added instantly, gave it a second, had control of the switch.

#

Works as expected, and frankly is a much better add experience that Homeseer. Not sure why, but the mobile phone method works "as I was expecting" and the laptop add fails miserably.

west grove Mar 11, 2026, 3:34 PM

#

Wanted to close the loop on this.
First - Thanks for all your help. I appreciate it.

My local experience remains the same:
The length of time taken to add a device will vary greatly depending on what appears to be four different things:

'Computing device' used to add the unit. Mobile phone vs. MacBook Pro in my case. This makes no sense to me, but it appears to be a factor. Don't know if it has something to do with the device (very Doubtful) or how i'm accessing the 'add' feature within the UI itself (seems more likely). At the end of the day, mobile phone workflow worked much faster. Again, this doesn't make much sense to me, but it was enough for me to note it down.
Whether or not the device was gracefully removed from a previous Z-wave controller, factory reset from the front of the switch or 'new out of the box'. All of this is what i'd call 'pretty typical' in my Z-wave experience. You win some and you lose some re-adding switches from an old system, or even removing and re-adding them to the same system.
Provisioning with QR code vs. the 'old fashioned' put device in inclusion mode from the switch via manufacturers recomendations. This was a wildly mixed bag and I can't really tell you that one way worked better than the other.
Secure vs. Insecure (no security) add methodology. I had an S2 device not added to the network after approximately 15 - 20 minutes. I
aborted the process. I re-tried using the Insecure methodology and it added immediately.

#

It took about 4 hours last night to add 7 switches. One LED strip still will not add or provision to the system despite going into inclusion mode as expected after a factory wipe. One switch remains physically stuck 'on' after being added to the system. The only button press that turns the lights off is the air gap switch on the bottom. 120v Breaker reset doesn't fix it, un-wiring it didn't fix it, software didn't fix it. It appears that some how, during add, the relay has actually welded itself closed. Software appears to work, but the relay is dead.
I'm happy to chalk some of this up to Z-wave and it's inherent system variables.

#Zwave issues on NEW INSTALL, not a migration install.