Yep - if you see a device ID for a nonexistant device - that’s a Ghost. It usually happens when a device is removed from your system improperly. (Almost always, you removed it from the IDE but didn’t exclude it from the hub but other weirdness can cause it too, there’s a lot about the interactions between the new app infrastructure and how the hub behaves that we the general users still don’t understand…) So your hub is still telling all of your other devices that the ‘missing’ device is a valid repeater. They try to repeat through it and… Poof. In some cases they create an island of devices that cant communicate or drop a strategic repeater and cut off a whole chunk of your network.
The general repair for it is to manually create a new device (I use the ‘Zwave Device’ DTH) in the IDE, assign it the network ID of the ghost, then (VERY IMPORTANT) Delete it in the APP - not the IDE.
If teh app detects you’r eattempting to remove a ZWave Device - it actually will kick the hub into exclusion mode and try to do it gracefully, including deleting the ID from the routing table. (That’s why you need your temp device to use a DTH for a ZWave device)
Dropping it from the IDE - would be more like amputation by machete rather than amputation by scalpel. Sure, the machete gets the job done for now and with some stitches, you’ll live… We get you off the battlefield to fight another day. But it’s not pretty and there’s a mess to clean up later.