I repeatedly keep getting shown new Things, Shelly devices for the most part but also virtual things from openweathermap binding.
I can choose to ignore or remove them, but they keep reappearing after some time, possibly after an OH restart.
Does anyone know how I can permanently disable device discovery ?
I’m not sure there is a way. It’s weird you keep getting OWM Things, That’s not something I’ve experienced nor seen reported for that binding. The way Shelly works I’m not surprised about seeing this behavior for it. I personally also see it for Chromecast.
Do you have Settings → Inbox → Autoignore enabled? That probably won’t completely solve the problem but it might mitigate it somewhat. But I beleive disabling autodiscovery overall will require a change in core. I see not setting that seems to disable it. I might have missed something though,
Likewise, I’ve been wondering about the same. I have 40+ devices in discovery, all have been added (from different bindings, Wled, Esphome, Mqtt autodiscovery, chromecast, upnup and the like.
Though esphome it might be related because we need to change the original name (not label) of the thing created so it’s not the same.
Yes, ignored things are back every time OH restarts.
to add some oil to the fire! 
I run a test-openHAB in a docker, which somehow(?) get autodetected. right now it’s 322 of them:
adding my few words…
also have some things in the inbox, which have been already added via (the unloved) textual configuration:
Seems to be IPv6 specific (bits 33 to 64 are different in each entry, at least the ones shown by the screenshot), afaik this is part of privacy-extensions.
Yes, that’s what’s apparently behind it. But the docker container does not fire up every day or so!
it’s only restarted with the OH-updates.
all standard docker setup. Perhaps the container itself gets (or asks?) for a new IPv6 after lease time is up…? I’m not that firm with docker to get into that specific configuration.
privacy extensions result in changing IPv6 very frequently, depending on configuration, these are temporary IPs and are valid only a (relatively) short time, maybe 6 hours.
Isn’t that a bug, then ? I’d say they should remain ignored.
That’s what I believe as well, and while I cannot find the discussion anymore, it has already been brought up in the past and the answer was “this is the expected behavior”.
just read myself into those privacy extensions. My homeserver runs on Debian and with ip -6 addr all virtual NICs are valid “forever”, not one is “temporary”. Privacy extensions are not active as it seems for me.
But is this true for docker?
