I'd expect that because, as a consumer, I expect the manufacturer to work with their sub-suppliers to fix problems. This being said - I recognize the Hubitat team is working hard to fix problems that are within their ability to fix. But someone, somehow, somewhere in the silicon labs or Hubitat or whatever part of the design and manufacturing side should have this fixed after all these months.
Well, I'm off now to set up a laptop with some software that I shouldn't have to know about to fix a silicon labs defect that is endlessly frustrating.
PS - to anyone on the Hubitat side reading this - I love the new "Rooms" feature and all the great stuff you are adding and realize you guys work very hard to improve this product. Despite my frustration with this issue, I do appreciate the efforts that you guys continue to make.
Is there another platform that works the way you you have described? I've never seen one. As others have stated, this is an issue with SI labs, not Hubitat. Until SI Labs fixes it, there is nothing Hubitat, or any other platform can really do.
Bring up an old thread here but i've been going crazy trying to remove 5 ghost nodes. Tried Refresh, Remove but nothing is working. This is on my C7 Hub. These failed during power outage so they can't longer be excluded unfortunately.
If you shutdown the hub, remove power from it for 10 seconds, power it back up, open the ZWave logs in one tab and the Zwave details in another tab and then click Remove what do the logs show?
Now that i know about ghosts i check immediately after failed inclusions. Mosy often you will see a ghost there and at this pt they can be removed real easily with a simple exclusion of the same device. Saves much headache in the long run.
Migration to C8 won't remove ghosts, so best/first approach would be to get the ghosts removed. Having a UZB stick around can also be useful for upgrading FW on Z-Wave devices (faster than doing it via the hub).
