I’ve got a device I tried to pair, and it’s been stuck at Initializing for days now. It obviously failed, but even when I run an exclude and do so on the device, it won’t remove from the list. Is there a way to add a force forget option?
I’m assuming I can just reboot the hub to clear it, but wanted to see if it eventually cleared itself first.
I opened a support ticket yesterday on this. I have a rogue device that won’t go away from the discover devices page. It also shows up in the zwave settings too. I have rebooted many times and it won’t go away.
My experience is that you can successfully pair it - ignore the “stuck” entry. Treat it as informational 
I don’t know your specific case but for me, it means the ID # for that device is in the ZWave USB stick and copied into the Hubitat’s internal db. Because of the way I joined my Hubitat to my Existing ZWave network, I have several that are from devices I have and no longer use. The db transferred over when I joined the Hubitat, and they aren’t going to go away.
I’ve found that I need to cycle through the Discover Devices a lot of times, triggering the device to try and get the device and the USB Stick to be chattering at the same time. Eventually it works. I’ve had this happen on a dozen devices and eventually they all joined properly.
Does anyone know what ‘Re-Initialize’ is supposed to do? I was assuming that it was like the ST Z-Wave ‘Replace’ (which allows an unpaired device to join the network using an existing Device ID, as opposed to generating a new one, thus allowing automations using that ID to keep working without re-editing) but whenever I’ve tried it it doesn’t succeed.
I think I have the same problem. I tried to join an Aeon Z-Stick on a PC running Zensys Tools, and it never finished “initializing” (I think? Or did it…because it now shows up as a device and lets me rename it) but now shows up every time I try to add new devices, even if I remove it. I’m pretty sure this happens even when the Z-Stick, which I haven’t powered on in a couple weeks (but does have a battery), is way out of range and definitely not in “pairing” mode. I even tried restoring my DB to a backup I made before this happens.
Let me know what you find out. I’m contemplating just restoring my hub since I’m mostly just using mine as a radio for Home Assistant now and so that’s where most of my logic lies (and re-adding my devices to my MQTT bridge app is all I’ll really need to make that work), but the Xiaomi devices I’m testing would be the biggest pain there. I’m also trying not to bother support, but let me know if you figure anything out, and maybe I should.
Reminder, the Hubitat Zwave USB Stick has memory and pairing is done to it, not the Hub. The hub then reads that database in.
The hub gets the device ID from the USB Stick and then starts conversing with the device to get it’s configuration/capabilities. I think that activity is called “initializing” on the Hubitat, but I don’t actually know with certainty. Not finishing the initializing process would be, I believe, because the USB Stick has a device ID that got transferred into the Hub, but when the hub tries to converse, gets nothing but silence.
This silence would be normal for a battery device which may not wake for hours, thus the Hub will wait for hours
Download the Hubitat app
