What does it mean if I am seeing devices with no name on the Z wave detail page?
Incomplete pairings have created ghosts.
2 Likes
Read this, sections 1-3
1 Like
Thank you for the info. I am feeling a bit overwhelmed and frustrated trying to figure this out.
I just migrated from my C8 to a new C8 Pro and thought all was good.
Existing zwave devices that are paired correctly all seem to be ok except for my gocontrol garage door controller. I can’t get to it right now to unplug to reboot it. Hoping that will help once I can get that done.
You mention a zwave stick. Could a smartthings hub that was unplugged a very long time ago and stored away work? Not sure I can remember where I put it though.
I have tried the refresh and then force remove but it fails on all the ghosts I am seeing.
Since this is a very recent migration would it undo some of what I have tried if I intsalled a backup from before I started trying to remove the ghosts??
Probably had those ghost devices on the old hub and moved them over. Unless you just recently attempted to pair devices to the new hub?
What good would that do? Did you somehow make things worse with your attempts? Otherwise not sure what you would be trying to accomplish. If you locked up the radio just do a shut down and unplug the hub for 30 seconds. That is outlined in those instructions I think.
No, I think you went too far in that guide, and skipped part of section 3. Stick to 1-3, the new info in section 3 covers how to switch to ZWJS to help remove the ghost nodes.
1 Like
Thank you so much for your quick reply. Yes I did overlook the part about ZWJS I think partly because I had previously referenced another post that covered similar topic, but it was older. After I found that on the Z wave page and changed it over I was able to remove the ghosts with no problem.
I guess another question is should I leave it set to this protocol or is it better to go back to the legacy protocol?
Personally, in its current state, I would go back to legacy. Maybe they will fix more of the bugs for 2.4.3...
Thank you for the advice. I did go back to the legacy.
I’m not sure if it was before I did that or after, but my goControl garage door controller had an alarm going off. Opening and closing the door didn’t do anything. I had to move the car out of the way so I could get to the opener so I could unplug it, wait for 30 seconds and then plugged it back in and the alarm was gone. Gave it time to settle back in and it seems like it’s connected OK and working and responding like it.
So glad it seemed to settle in OK because I know it can be persnickety of it loses its connection to the hub.
With the way, everything else has been going now my thought is what if the garage door decides to act up in the middle of the night and open on its own, which has happened one time before. Thankfully I have a smart plug that it’s plugged into for the opener itself not the go control. So I think I will just turn that off, so I’m not worried about whether or not the garage door will open spontaneously in the middle of the night.
Isn’t home automation fun? Usually it is especially when you’re old with plenty of time to fiddle around with things. But I do have to say there’s times that it gets frustrating.
Thank you again for your help and suggestions
Sorry about that, that was the switch to ZWJS which caused it. That one specific device does not like when ZWJS first interviews it and it goes into a lockout mode. Multiple other people had the same problem during beta testing of ZWJS and beyond. You should be fine with it now, it should not do it again.
Would removing power from the goControl before switching to zwaveJS keep it happy?
It needs to be interviewed at some point or it wont work with ZWJS. I think as soon as you plug it back in and it send a message it will get interviewed. The interview works but the device gets mad for some reason and locks itself out. I dont think there is any way around it.
2 Likes
