Z wave Ghost issues

[danabw]

Longer answer from the Z-Wave Ghost removal topic:

@danabw

Why doesn't Hubitat just fix this!?

Details

TL;DR: They can't - they are limited to the tools and options provided in the SilLabs Z-Wave SDK, as well as limitations imposed on them since they are a Z-Wave Certified hub.

Long answer: Ghost removal issues are due primarily to the Z-Wave SDK provided by SilLabs to all Z-Wave 700 & 800 hub vendors. That SDK (and its associated bugs/limitations and operating agreement that HE must conform to for certification) control/limit what the HE hub can do. HE has worked steadily to improve the Z-Wave experience in areas they have some control, but in the area of Ghost removal they're limited by what SilLabs provides in the SDK and the requirements of their Z-Wave certification. Software used in the ghost removal process detailed in the PDF here is not constrained in the same was as it is a developer tool and relies on a different SDK/process to remove ghosts, one that consumer-certified hubs like Hubitat cannot use.

SilLabs has continued to release Z-Wave updates and Hubitat integrates & releases those updates. Things are much better than they used to be, and should hopefully continue to improve over time.

The most important thing you can do to simplify issues related to ghosts is avoid them in the first place by creating a robust Z-Wave mesh, and checking each Z-Wave device on your Z-Wave Details page as you join it to ensure a proper pairing w/the hub.