Hello, I am using zwavejs2mqtt. I had some issues after updating. I first had issues with my zooz 700 series usb stick not being recognized, but I got that sorted and got my zwave network back online. None of my battery powered zwave devices came back up though. So, I started working with those, having to exclude then include again. I managed to get them half working, but the entities were mostly unknown. Then I noticed that all of my Zooz devices were registered as unknown. I made sure they were part of the device list on the zwave js device database. I also looked at the zooz website which tells me to add the xml file per the instructions listed on the zwave js page: Z-Wave JS - Home Assistant
The only thing I saw on that page regarding unknown devices was to wait until they are supported, which from what I can see all of my zooz devices are already. I am on the latest update for zwave js and zwavejs2mqtt.
Can anyone help or point me in the right direction to get my devices correctly registered?
I’m unclear, are all your Zooz devices (mains powered and battery) experiencing this issues. Do you have other z-wave products from different manufactures that do work?
No, I have several battery powered and then a couple of 120v switches. The switches came back online right away, but now register as unknown. The battery powered devices had to be excluded and then added back into the network. And they are now registering as unknown. When I say registering as unknown, I mean the manufacturer, make, and most (if not all) entities register as unknown.
What happens when you include one of the battery devices right next to the controller? (with Zooz devices, I’ve noticed it’s best to exclude the device (even if it’s not included) before inclusion)
Still ended up with unknowns. I did not mention that the diagnostics all show up properly. I.e. battery level.
I am wondering if it might be tied to the old configuration file, when what it needs to do is pull a new configuration file since the update. I have no idea, just shooting in the dark unfortunately.
And I think I misread your first reply. Yes, both my 120 powered and battery powered devices are experiencing the issue. I do have some GE/Jasco switches that show up just fine.
I do not have the stick on an extension, but I will make that adjustment.
One day I came home and all my zwave devices were unavailable. So, I started by updating z-wave js add-on. Which required me to re-download the add-ons repository. I then updated zwavejs2mqtt. After updating both of those, I had to do some work with getting the computer to recognize my zwave usb stick. Once I swapped it to a different USB port and enabled it in VirtualBox, it showed up and all of my 120v devices worked. The battery powered devices would not work. I tried re-interviewing the nodes while manually waking the devices with no success. I finally got the communicating after exclusion and then adding them back in. However, the entity names changed along with their values (Open/close sensor reading on/off rather than true/false). And that is when I lost the manufacturer identification and entities. I was going to just live with it, but I wanted to set a luminance state for one of my automation and realized I couldn’t find it. That is when I started digging.
Just from memory- I think I read this- the next time you see this, run around the house and turn on/off all of your Z-wave devices. Could that be what occurred in the past couple of days?