After 2025.2, I had a second z-wave integration popup as detected in my HA install pointing to my existing z-wave add-on, and I (foolishly?) clicked add. It seemed to not break anything, so I just kept on keeping on. One is using a local domain and one is the ip of the Z-Wave JS Add on:
I was happily ignoring this for the last month, but I’ve noticed if I trigger a z-wave scene, in the Dev Tools > Events > Listen dialog, I see everything duplicated:
What is the safe way out of this? I disabled one of the two integrations yesterday and a bunch of my z-wave nodes went unavailable, so I paused until I had time to ask this question. Thanks!
They will fight for the same hardware using the same drivers, and flip/flop without you realizing it leaving you say WTF… (ask me how ?I know…)
I’m not certain the process I used to fix this, but in the end I suggest removing zwave add-on and using the zwave js add-on. either will preform similar, bit that one give you more buttons to push. If you do not like buttons to push, keep the zwave one. also if you click the box on the integration set-up, it will load the zwave add-on for you if you want it or not.
I’m not sure I understand what you’re saying. I have one Z-Wave JS UI add-on, but two integrations now. One pointing to a0d7b954-zwavejs2mqtt and one to the internal ip of 172.30.33.2.
If I disable a0d7b954-zwavejs2mqtt, my z-wave devices go to unavailable. If I re-enable it my devices come back.
If I disable the 172.30.33.2, my z-wave devices go to unavailable. If I re-enable it my devices come back.
But having two is clearly problematic. How can I get rid of one if simply disabling one makes all of my z-wave devices drop off?
EDIT: Maybe I wasn’t giving it enough time. I disabled one, reloaded it, restarted the Z-Wave JS Add-on and it seems all but one battery device are fine. Oddly though, that device shows fine (online) in the actual add-on.
