I migrated from OpenZWave to ZWave JS a few months ago and it’s generally been working fine - much better updated etc. However I recently realized that I really should have gone for ZWave JS UI due to its additional perks. So I tried installing the add-on, copied over the network keys etc. from the ZWave JS add-on, disabled ZWave JS, enabled ZWave JS UI, reconfigured the integration to point to the ZWave JS UI websocket instead and after a little while the devices all came back up in Home Assistant successfully. Great success. The devices all have their same IDs so keep their names in HA, all automations work etc. I can see the nice graphical network map in ZWave JS UI.
The problem I’m having is that for some reason most of the devices show up as “Unkown manufacturer” and “Unkown product” in ZWave JS UI. Even though they’re in the device database and were identified perfectly fine by the ZWave JS add-on. Even the ZWave controller (Z-Wave.Me USB stick) shows up as “Unknown manufacturer 0x0115, 0x0400, Unknown product 0x0001” which are indeed the IDs of the well working and supported Z-Wave JS Config DB Browser
The only devices that show up are some in-wall switches (0x0060:0x0004:0x0008:0.0), none of the other ~dozen devices I have. Only these recognized devices have their configuration options shown in Home Assistant, all other devices have zero configuration options, which I guess is as expected as ZWave JS UI can’t provide them.
Any ideas? After reading other threads, I’ve tried: Cold HW restart, waiting 24+ hours, triggering re-interview of all devices through ZWave JS UI, but with no effect. I assume that the HW controller only cares about the devices IDs, network IDs, etc. and isn’t aware of any “high-level” mapping to device/entity name, available configuration options etc. I would really like to avoid re-interviewing all devices again. Can the device configuration database be brought over from ZWave JS to ZWave JS UI?
The devices that are unknown, do they show that their interview has completed? Are they mains powered or battery operated, as battery operated devices usually require a lot of time to check in and report/interview. Don’t re-interview too much devices at once and ensure that you don’t suffer from any interference (most likely USB3).
They were already working well with the ZWave JS add-on, including all device type-specific configuration options that show that they were successfully identified and looked-up in the device type database. I haven’t added any new devices, just switched add-on. I only see an option to re-interview all devices at once in ZWave JS UI, and this does work (though it takes a few minutes), it just doesn’t help any. It shows status as Interviewing->NodeInfo->Complete for all devices but they’re still (almost) all Unknown. Again, even the controller, which cannot be re-interviewed at all (makes sense of course).
They are both mains and battery powered devices. There are no issues with communication with the nodes. There’s no radio issue. They all worked fine with the ZWave JS add-on and their basic functionality (e.g. light entities exposed in HA) still works fine after switching to ZWave JS UI.
By switching to a new addon the device database (cache) will be recreated. Best if you still have the old addon files to copy stuff over as referred to in this issue:
2 maybe stupid questions
Where do I find my network key in ZwaveJS and where do I put it in zwave JS UI
I see where to setup the serial device and the documentation talks about a entry for network key, but I can’s see it.
Do I have to disable of even delete the zwave JS integration in order to use zwave JS UI?
You can find the network keys of ZWave JS in the add-on configuration page (Settings → Add-ons → ZWave JS → Configuration). There you should have configuration both for the USB device to use and also five keys, of which network key and S0 legacy key should be the same. But to be clear, this is how it looks to me - if it’s missing for you I have no idea why.
You have to stop the ZWave JS add-on before you start the ZWave JS UI add-on, as they both want to communicate exclusively with same USB device. You’ll get an error message from ZWave JS UI if ZWave JS hasn’t released the device yet. It might take a little while to stop - I tried it a couple of times before it worked but likely I just didn’t wait long enough. Probably good practice to change which one is started on boot as well right away so you don’t forget it, even if it won’t matter until next reboot.
I hope you don’t have to uninstall the ZWave JS add-on - I can’t see that it should interfere as long as it’s not running. In a similar situation I kept the Deconz add-on installed but inactive for quite a while before uninstalling it after switching to Zigbee2mqtt, with no ill effects.
Aha, it’s the S0 key, you already have it set. As I noted before, the S0 key is identical to the Network Key if you look in your ZWave JS configuration, but you don’t have to specify it twice in the ZWave JS UI configuration. Not sure why it was duplicated in ZWave JS - if there was ever a use case where they could be different. But just copying over the four unique keys worked fine for me.
Thanks things are running. But there is one HUGE drawback (at least in my case).
I am (slowly) migrating from Fibaro Homecenter2 to HA. so part of my Zwave units is still connected to my HC3.
What I see now is that there is no connection between units in HA and the units in de HC3.
also part of my automations in HA are not working even though these are HA units trying to control other HA units.
furthermore, I see all my devices which are directly connected to HA, but I don’t see any entities. And thus nothing is working.
But besides the switch Homecenter → Home Assistant, you also switched from ZWave JS to ZWave JS UI with some of the devices already moved over to HA? Did the devices (and their entities) work before switching to ZWave JS UI?
in my HA configfile I can see and control all my devices in HA.
Just view the HC2 as some sort of ZWave stick like the Aeotec Z-stick.
In HA I see all the devices and all the entities no matter if they are connected to HA or to the HC2.
That’s my stable starting point.
If I disable ZWave JS and I enable (and start) ZWave JS UI I see my HA connected devices appearing in Zwave JS UI. But no entities. so nothing is working. the Entities tab in ZWave JS UI is empty. I can’t control my lights from the Lovelace UI, nor are my automations working.
Do you have entities in your Entities tab and if yes, did they appear automated or did you enter them by hand?