C8, 2.3.9.184
Looks that way.
Discover doesn't do anything.
Devices page, SmartStart mgr app show nothing out of order.
Where do I go from here?
Same procedure as for non-LR?
I did that once. Will have to brush up, if that's the case.
Thanks.
Nope. You can't remove LR devices with a secondary controller (they don't even show up on them), you can only do it from the primary. So you can't follow the other guide for removing LR ghosts.
Only guidance I have is:
Try removing the smartstart entry and shut down and removing power and see if it goes away on its own.
If it doesn't, make sure the device is fully offline and refresh and hope that remove button comes up after some time, and actually works.
I had this happen early on in hubitat's LR support, and was never able to resolve it.
@danabw if this isn't in the guide, may I suggest that next time you edit it, this goes somewhere in the top, Bolded?
Might save somebody a lot of frustration!
S.
2 Likes
It doesn't show up on smartstart, and there is no way for me to tell what device it is referencing. I don't see anything missing, device wise, but I'll keep looking, I guess.
Is it still hanging around?
No, as I reset my zwave radio since then.
2 Likes
Usually just a reboot will take care of these now.
There is some sort of caching issue with LR nodes and stuff gets stuck in there.
2 Likes
I've tried a shutdown/power cycle once.
I'll try just a reboot.
Probably wont help if a shutdown did not.
Check the node number though after rebooting, see if it changes by chance. If smart start keeps trying to add some device it would use a new node each time.
Reboot with db rebuild didn't help.
The node number is constant: 012f (303)
Ah crap, was on my list, but forgot to add that. Thanks for the reminder. 
OK, topic updated at the intro, and at the start of section 4 (the UZB Z-Wave stick section).
1 Like
How about saving a backup to the cloud, resetting z-wave radio, and restoring? Seems dangerous, lol.
Agreed, dangerous, more likely to make it worse not better.
I would just ignore it for now. Since its on LR there is no mesh so its not hurting anything.
Hopefully the next platform update will get some more LR attention.
3 Likes
Yeah. Instead of Matter and Aqara? Maybe not.
Usually the team divides and conquers. Each member of staff have their own specialty. So I don't think it is either/or in situations like this, it is just who was able to get their changes into the pipeline at whatever point.
Apparently Z-wave improvements haven't worked their way into the firmware cycle (for public release) yet. We don't know why we haven't seen these changes, it could be ready tomorrow or months from now for all we know.
1 Like
Well, I'm courting danger....
I've restored several cloud backups, (I've been doing them weekly), with the radio option.
I found a backup from three weeks ago that did not have the ghost. Alas, since then I added maybe 9 LR devices, but not much in the way of rules.
If I really wanted to get rid of it, would I exclude/un-smartstart them in the current version, go back to the three week old version and then re-add them (smartstart)?
Or, could I just go right to the three week old version, and then proceed to add them? Would I have to do factory resets first?
In any event, hardly seems worth it, considering it's LR and there's no potential mesh disruption involved.
I'm back to the present. Interestingly hitting discover and/or refresh got me an "unknown" device. From a previous iteration, if I Remove it from the device page, it will go to Force Remove, and will just resume its ghost like appearance on the Z-wave details page.
Any suggestions?
Yes you would have to either do an "exclude" on them or factory reset. You can exclude devices on any hub even if not included on it, it will wipe out the attachment to a hub so you can include it again with doing a full reset on the device.
Correct.
Are you sure there is not a device on that node still? Usually the discover only works if a device responds, especially suspect since the clusters info populated. Unless it is cached in the radio. Although I did have this happen on a regular node on anther hub to me not too long ago, so could be a current platform bug.
I'm not sure of anything-maybe "Refresh" only did it...I don't really know.
The log version of the above is:
I think it's a radio artifact type of thing, as in cache. But I don't know anything.
The debug log is related to the smart start device naming but I am not sure how Bryan jammed that in place. Normally when you see a "parse" it is because the driver got a message from a device but the hub could be doing something with SS to force a parse through, not sure.
