You could try a soft-reset, but probably would not resolve your issue. It would not (should not!) hurt anything. I haven't heard a soft reset resolving a Ghost issue. It can resolve general database corruption...
1 Like
I'll try.
2 Likes
To clarify - that the hub's H2 database. Not the z-wave radio's internal db.
2 Likes
Yes...hence the unlikelihood that it would do anything about the ghost. But won't hurt, and just in case there is anything else going on (weird switch behavior) might help. 
2 Likes
Went thru the soft reset.
Nope, it came up as before.
When I tried to remove it, it just went "pending".
Thanks guys!
Maybe it will fix itself😳
You can just wait to see if it causes problems (usually things like slow response of other Z-Wave devices).
If it doesn't harm, then you can ignore it. I had a ghost that was harmless. I did finally remove it, but more for me than anything else.
If it does cause harm, and normal processes won't remove it, you'll have a couple choices:
- Z-Wave radio reset (not too much fun, but not the end of the world)
- UZB stick and PC Controller app (a bit of a process, costs you $ to buy the UZB stick). Link to that process below:
1 Like
Btw, I did go around and pull the tabs on all my paddles, didn't help, so it has to be one of the toggles.
I could go to the breaker panel for most of the switches and power down all but the hub's breakers...
Would that work?
3 Likes
Yup - if the breakers align and you don't have to kill anything you need related to the network and hub, that is an approach that others have used. Go for it. (But don't tell anyone at home who you inconvenience that I suggested you kill their power.)
2 Likes
Yup. You can also take your hub to some other location (friend’s house), power it up and remove the ghost.
2 Likes
No problem it's just a 71 year old man (me).
2 Likes
Oops - he tried the tinfoil faraday cage and that didn't work.
That means theoretically that killing power won't work either. But killing power is more "for sure." So worth doing...
1 Like
Tomorrow. Time to hit the sack.
Nite guys.
I'll keep you posted.
2 Likes
Hey, we "mature" people matter too!! 
@aaiyar is about 124 or so, IRRC. 
He still has a slide rule.
1 Like
This never worked for me 
2 Likes
After doing that, it still talked to all the devices.
2 Likes
Same experience. One of my friends told me to try the fine metal mesh on my window screens, but i wasn’t upto sacrificing a screen.
3 Likes
Turned off every circuit in the house (hub and network are on battery backup).
Could not remove 0B, still pending.
Looks like the only way to get rid of it is a rebuild of the zwave database or some kind of record deletion routine (seems like that routine is already there, but records are locked) with a warning that you could cause destruction.
I have an OLD knowledge of random databases and know of pointers to "next/prior" records. Is it possible that the record, being the "base" record it has a problem being removed because the pointer is 0?
If it's giving you the option to remove regardless of the warning it's likely safe to do it.
What would be the reason for "pending" and when does pending end?
And does "pending" impede access to that record?
