During a lot of driver packages and installs, I seem to have got myself into a weird situation.
I have a driver that appears when I logcat, but does not appear anywhere else. If I do logcat it, It does seem to be active during a scan. (It is a lan, local driver).
This should have helped. It has happened to me with LAN drivers (and I already reported it). For example, I create a driver package and install it, then, I delete the driver (uninstall > unpublish > delete). After this, if I hit “scan nearby” it seems the driver still appears but as “unknown”. Rebooting the Hub helped.
In this case:
Do you see the driver’s name?
Which version of the CLI are you using?
If you use the driver ID to uninstall, unpublish and delete, does it accept it?
I’ve also seen that I had a driver “installed” but the package was deleted. So, running these commands helped check where it appeared:
Sounds familiar. In my case it was a survivor of a factory reset of the hub. Twice. It disappeared eventually. No idea if someone deleted it for me but it certainly wasn’t anything I did.
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.