It’s 4 hops. The originating device and the receiving device don’t count.
Orig—>1—>2–>3–>4–>Destination
Is 4 hops.
2 Likes
They change based on traffic and obstructions. If a repeating device is busy with another message, then that route isn’t available. If a human is walking through the house, their body can block signal, making a route unavailable. The network is taking into account a lot of information that you don’t have when you’re just looking at the list of nodes the last route went through.
a body pack transmitter can be 50 to 70% less effective than a handheld transmitter simply because of the antenna location being against the human body
4 Likes
@RBoy So I just tried this process twice and my ghost still remains in another devices path. Does it take a while for the IDE to update or did the process fail?
Thanks for the info, but I noticed something different. Can’t find it in this topic with Find.
I see at Type so called “placeholder”.
Here how it looks, one picture with the duplicate name next to the functioning device, the other filtered on “placeholder”.
I will try to remove the placeholders and see what happens.
Grtn Ben
placeholder is for devices which are connected using Cloud to Cloud integrations using the new ST app. If you delete then you will need to reconnect them. They don’t have any impact on zwave or ZigBee
1 Like
Tnx for the info.
Thought delete it would solve my ghost devices.
DO NOT DELETE or otherwise mess with placeholder devices unless you want to fix whatever it breaks.
2 Likes
The path that you see in the I DE is the last reported path, but it can indeed take quite a while for this to update. (At one point it only updated once a day, but I think they’ve made it more often than that.)
So the first thing to do would be to actuate the device That path is for so at least there’s a new “last used” route. But you still might not see it in the IDE for a while.
2 Likes
Thanks for the input
1 Like
Can’t tell what is broken now, I removed the placeholder devices.
But the duplicate / ghost devices are gone now in the app.
None of the steps included in the original post worked in my case. tried 4 times with the same result…ghost device still remained, even after a day. In the end, I had to exclude and re-include the end device that was using the ghost infested path.
Finally figured it out-
I had bought a new Zooz power strip, and it was probably bad. Even though I had removed it after the problems stated, I had left it plugged in. That was flooding the z-wave network.
Unplugged it and everything worked. I had to exclude and include a bunch of stuff, because I was trying to diagnose the problem - but otherwise, it would be all working.
1 Like
Have the same issue. Message after Force Delete: “this device can’t be deleted because it is operating normally”. Did you solve it?
Yes, I switched to Hubitat for my ZWave controls.
I think ST is fixing that in the next firmware update: Hub Firmware Beta 0.35.x
3 Likes
I hope so. I’ve been updating firmware on some Leviton switches, and have run into issues where ghost devices appear when the ID changes on the switch. Sometimes the removal procedure works, sometimes it doesn’t. And for those that it didn’t, they magically disappeared several days later. Ya gotta love consistency!
I had this problem in the app on several Android devices. I finally went to the IDE and deleted it without issues.
Good afternoon. I have the newer GE smart switch installed as a new repeater… So far, Im having nothing but problems.
The new smart switch is working but its not being used by the front door schlage lock.
This Device (0A) ↔ Unknown Device (F2) ↔ Unknown Device (1F) ↔ Unknown Device (1D) ↔ Gatlinburg Chalet Hub
I have followed instructions for ghost devices, and have deleted them, and do a zwave repair. Then after a few minutes, new unknown devices pop up.
Mind you, All I have that’s zwave is the hub, the front door lock, and the repeater. I don’t own anymore zwave devices. I even removed the ecobee that was tied into smartthings.
I’m at a loss for words since this is our cabin, and nothing I do is working. The monoprice repeater just made everything work instantly, but even now this GE smart switch is not working and the front door schlage cannot communicate with us
This has now turned into an awful experience, especially when everything was running so well (A guest either broke or stole our monoprice repeater and that’s when our problems started)
Any hints? Tips? Suggestions? THis is for our rental and its been bad dealing with not using unique door codes. We use the Rboy rental app software and can no longer communicate with the lock due to no repeater working in the ROUTE
Does anyone know what to do if the “unknown route” just displays “Unknown Device(???)” instead of an ID. It seems like for this process you need an ID, but my IDE is not giving me an ID, just question marks instead.