I think I’ve made a noob mistake. I added a ZWA 2 to my new HA Green for my Z Wave devices that were previously running on Hubitat. For reasons unknown something led me to install the Z Wave JS UI add on. I thought this was needed and have included 37 devices using JS UI. I’ve now realised that I didn’t need it (I also read that using the built in JS is recommended)
Everything is working ok but I believe both the built in JS and the add on JS Ui are running simultaneously (I can edit device parameters from either).
Looking for advice on the best way forward. Do I leave it alone as everything ‘seems’ to be running without issue? My preference would be to remove JS UI and use the built in version. I’ve seen some documentation for migrating from JS UI to built in; is that documentation relevant to my situation where both appear to be running side by side (every device was included via JS UI)
You’re running what I’ve been running for four years now… BTW
What makes you believe builtin is better ???
(for many years people rushed to ask how to migrate the other way. Core is just now getting the map features etc.)
Its the same ZWave drivers under the hood. You have a different interface and it runs out of band of your HA server so you can restart HA and ZWave keeps truckin…
I read that built in is now recommended and JS UI is or will be deprecated. I suppose I’m more concerned that I’ve got both running simultaneously as I also read that could be problematic. I’ve been backing up the built in JS not realising that I should be backing up JS UI….
(Also if you were running both on the same coordinator it wouldn’t work the second would fail because port in use.)
If you’re running the one as an app make sure you back up the app too and periodically backup your controller inside js (anytime you change the network at a minimum)
Ok your top Pic is a generic control space for an HA app. (formerly an Addon) which tells us you’re running as an App/addon (my you can bounce HA without affecting ZWave is true for you yay) your bottom Pic is the actual ZWaveJS interface also formerly known as ZWaveJSUI.. (there used to be two packages one without the UI.)
It means you have enhanced joining unjoining backup options etc.
That is inside of the integration. It list all the Z-wave devices that have connected to it. Much like MQTT, ESPHome, etc all have theirs. It is where you can see all the sensors, states, switches, buttons, etc each device has.
You are learning by exploring. Take your time, you will become and expert just all us old newbies have!
I’m away for a few days but will come back to this when I can get further details/explain better. I am sure that I’ve got two Z Wave apps running simultaneously that shouldn’t be. The built in one that was set up automatically when I added the ZWA 2 and another community maintained that I also added before including all of my devices. I think when adding the latter I was supposed to uncheck something in the former. As said it’s working but I’m convinced it’s wrong.
Ok I’ve got a better idea. Instead of searching for problems that don’t exist I’ll forget about it and continue soaking up the sun in Ibiza. I finished the book I was reading so it may be an appropriate time to read the HA Cookbook and docs…
???
