Ok in repair my Home assistant installion.(a ionic vitrytual machine running on a Mac OS X host) I have haaos 18.2. with core 2026.8.3). sit Z-Wave and Zwave .js UI. When I add a sensor (Zooz Zse 11). I at a node. that does not show any of the sensor attributes. Keepinh HA going with the new “features”. ha turned iinto a full toke job. How do I add a device and not a not a node. I am sure I missed something iin the readme fils. Thought and prayers ?
If English is not your first language you should use a translator. That post reads like gibberish.
Try restarting HA
I added a Zen 15 last week, new product for me that had the same behavior, it added a node with no entities. But then I read the instructions, I had done it incorrectly. This was a smart plug. I had plugged it in and then scanned the QR code, but the instructions said to scan the QR code and only after it was added, plug it in. So it was my fault and it sounds like the same issue. The hard part was to make sure I’d removed the mistaken node before doing it properly. I also had to go into the integration, three dot menu and remove foreign devices or something like that. I had never even looked at that menu before but it was referenced in a Zooz documents that talked about removing failed nodes
Thanks for takin time
The Zooz Instructions In dealing with Inclusion that does not work (and in fact other manufacturers also say this). usually state that I should exclude the offending device and do the inclusion process again. The trouble have is that with HA adding the device only as a node, I can’t find the correct device to exclude..
It’s easy to find it, go into the integration and then devices and you’ll see one called node. Get rid of it and restart.
ok my post sort of one English
that goes back to the integration “…” menu. Disable is an option but delete is not.
From what I can remember I selected the node in the zwave JS UI advanced menu for that device, and then removed the node using that menu.
I also deleted from home assistant devices.
I also went to the integration menu for Zwave, clicked on the gear icon, clicked on provisioned devices or something like that and then deleted the bad one.
You will need to know which one to delete under the provision devices menu, I believe it’s the one with the same 16 digit code as is on the QR code sticker.
Then I started from scratch and re-added properly.
I got this information and it worked for me from a Google search for Zooz zwave remove node. Follow the instructions.
Some of that sounds familiar. but in three days of frustration I think I have made it worse
A lot of the reminds me of insteon as it was dying
I no longer see the node on the Z-Wave JS UI and I am getting warning about missing network keys.
I think I am going to go nuclear and factory reset the Z-wave Interface. ZWA-2. Switching to that as the beginning of my problems.
Thanks again
I think you’re asking that you don’t see the ZSE11 as a “Zwave device” but you do see it in Zwave JS UI as a node?
Also note that there are several hardware versions of the ZSE11 (Q sensor). A 500 series, 700 series and now 800 series. All are unfortunatley called ZSE11 so you might want to call out which one you’re trying to include.
Here’s what I would do to get the device paired.
- Go to Settings->Zwave->Provisioned devices. If the DSK is listed there, remove it. That will prevent it from trying to be added via SmartStart while you’re doing this.
- Inside the Zwave panel, go to Options->Remove foreign device. Click “remove”, then “Start Exclusion”. This will put your zwave adapter into exclusion mode. On your ZSE11, press the button 3 times quickly to put it into exclusion mode. You should see that it excluded 1 device, regardless if the adapter had the device details in its database. This will do two things, remove any old inclusion information about the device AND put the device itself into a reset state where it can be added via SmartStart.
- Remove power to the device, either battery or USB.
- Now inside the same Zwave panel, go to Add Device. Scan the DSK QR code when prompted. This will put the device on the provisioning list.
- Now you can power up the device via battery or USB. Note that you’ll want to use the same method to power it during inclusion as it will be used normally. Otherwise it will register as the wrong type of device (sleepy vs mains powered).
- The device should associate itself within 10 minutes since you already had it on the SmartStart provisioning list. You shouldn’t need to push the button to include.
- You should see the number of devices increase, and it will indicate its pending, or interviewing. It may take a few minutes to go thru the whole process.
Note that I have seen issues with some 500 series devices and SmartStart. Some work great and some don’t always work. So if you have the 500 series ZSE11 we may want to change the provisioning/inclusion process if this doesn’t work.
Good luck!
Thanks you!!
I have tomorrow (day 4). mapped out for me. My idea if factory resetting the ZWA-2. didn’t work. I raise its finger at me
I now see I new t develop a list of m DSK. See who is who
Yes my ZSE-11 are a mixed bag. One annoying thing is that Zooz puts the ID and QR code on the cover. soooo.
Before I even install a new ZW device, I take a picture of its QR code (and save them all in a folder on my OneDrive). That makes both the initial install and any future do-overs a ton easier.
The SmartStart QR code typically includes 5-digit DSK right above or below the code, so that’s usually the easy way to distinguish it from any marketing QR codes that may be on the packaging.
Good luck, A few other notes:
- I do not do any actions for including/provisioning inside JS UI. I use that for admin but it is not the generic front end for most operations. I think of it more as a low level tool like PC Controller is, seeing internal details and letting you manage very specific elements of the network. But also capable of messing things up unless you know what you’re doing.
- Excluding the device (even if you think its not already included) is often the trick to get a device to SmartStart correctly. You can also do a “factory reset” on the device but not all support that.
- As a general rule, I always exclude a device before including it regardless of its history. New in the box, used on the same zwave adapter, it doesn’t matter. It takes out a lot of variables and puts the device (and the coordinator) into a known state.
- As @Hydro130 mentioned, taking a photo of the QR codes is super handy for later, esp when a device is mounted or behind a wall plate. The Zwave Add Device->Scan QR code can’t read from an image (camera only, at least on the Android client) so I often use a QR scan app (or AI) to read the actual code from the barcode and paste that into the “optional” method of adding the device.
This idea by you and Hydro13 makes great sense even in hind sight. I have been noticing that I have most of my problems with battery powered devices.(not counting my own stupidity" Exclusion for me has been problematic. I thought by factory resetting the ZWA-2 interface I could get Z-wave to a fresh start but no joy there . I am giving some thought to start with a new virtual machine (a new canvas so to speak). Thanks for all the input
Day 4, OK following worse case scenario. I did everything I could find to factory reset my ZWA-2 and build a new VM. As far as I can tell all the node and broken devices are gone I have a fresh zwave ALL devices are gone which is ok EXCEPT I have enable HTTPS on HA to scan QR codes That is how iI spent that last couple of hours. The HA won’t cooperate on a manual inclusion (I even tried a manual exclusion on the device (Zoooz ZSE11 800lR) MAYBE this will all come together to morrow. after I figure how to get my HA secure
Good luck. It sounds like your zwave adapter isn’t communicating properly with HA thru whatever virtualization you’re running.
Basic inclusion and exclusion (meaning triggered by hand) should work every time. You may not get S2 inclusion but it should just work.
Exclusion is the easiest test. Start exclude on HA, and then trigger an exclusion on ANY zwave device with whatever button sequence it requires. If things are working, it should say that it removed 1 device.
If you’re not getting that, nothing else is going to work either. Check logs, check USB VM settings, etc. Virtualized HA with USB adapters seems like a bad idea to me but I guess people do it.
well at the present with the new VM. I have NO z-wave. device besides the interface/dongle l , Manual inclusion results in the correct device but stuck in provisioning. Maybe I will be more successful when I get https. working ( a separate post). I know of no other other then a virtualized HA using usb adaoters. Thie all worked before the last round of updates which would seem to indicate I missed something in the REAME. I have grown to hate Z-wave. it seems to be going the same way that Insteon did My zigbee ie working fine but ut has a different adapter.
Thanks for taking the time with me