Hi all. I've got two ghost devices that I can't get rid of. I know what they were (minoston power meter outlets) and still have them. Is there any way I can add them back and remove them successfully to get rid of these ghost devices? or do I need to buy the zwave stick?
Secondary controllers not officially supported, so I wouldn't say "need." Ghosts also aren't a guarantee of a problem, though they are good to get rid of; using another controller could also cause problems, even if many have done so with success.
Have you tried just waiting a day or two before trying removal again? Patience is often the key with Z-Wave. If the device is still powered up, removing power may also help (though if it's been successfully included afterwards, there's no way the hub should know this was it...but it can't hurt.)
You could try refreshing the browser tab and click remove button again. The fact that you see the remove button is promising that you'll be able to get rid of them. The problem is when the remove button isn't showing.
I've hit the remove button and waited three days and it still hasn't gone away. I've read ghosted devices can cause issues, so I'd like to remove it if possible.
I had an idea recently that you could try. You would need an extra Zwave device to pair (or the same device if you are not using it anymore). Click refresh until you get the remove/replace options but do replace instead of remove. Put your extra device into pairing mode and see if it will pair. Since your nodes are S2 it will ask for the DSK but you can just uncheck the security boxes and downgrade it to no security.
If you can get a device to pair into that node, you can then do a proper exclusion and it should remove it.
The ghost devices are still present after clicking "remove" and waiting a few days. So, is my only option to now purchase a z-wave stick and remove them?
If so, I'm unsure which z-wave stick to purchase. If someone could recommend what they've purchased and instructions they've used, I'd appreciate it.
He showed the log message up above. Same error as always when this happens. no longer in failed node list, which has been shown to occur in the past even when the device was ripped from the wall and smashed to bits, or shipped across the country.
