Recent upgrade OH2->OH3. I noticed Things that I have ignored in my inbox reappear in my inbox as if they were not ignored I do not have show ignored checked) after reboot. Is this expected behavior?
I think it should not happen, but what I see in my setup is that sometimes “new” devices appear that are actually the same and this is because of different IDs, example:
Both are entries by the chromecast binding for the same device, while other previously as “ignored” entries stay hidden for me:
Thanks @chrismast - unfortunately this appears to be a different problem for me. There are no item sin my ignored items anymore.
This happened to me after several updates, too.
No clue if it is expected behavior…
@Kai - sorry to bug you on something small, but can you weigh in if this is expected behavior or if I should file a bug report?
I’ve had this problem for a long time as well, and I’m currently on a 4.3 snapshot. Does anyone know a solution? It’s not a big deal since everything is very stable, and I only need to restart very rarely 
It’s a problem I keep seeing, too.
Things also pop up as “new” after I turned them into a Thing (rather than ignore).
I’ve observed this mostly with Shellies, but obviously it happens with other bindings, too.
Can you please open a Github bug with openhab-addons ?
Yes, I can open an issue. But are you sure it is in the addons? Because I see this for Hue, Homematic, Android-TV, Harmony.
Not 100% but in the first place thing discovery is a binding-specific implementation.
Devs will move the issue anyway should it be more appropriate elsewhere.
Please provide as much info as possible, upload /var/lib/openhab/jsondb/org.openhab.core.config.discovery.DiscoveryResult.json
Best would probably be when you can reproduce it for a new device.
Ensure the binding loglevel is on debug and upload the relevant lines of openhab.log, too.
OK, there was already an issue on Github and it seems that it is a “feature” rather than a bug.
But it’s not a satisfying status quo.
Somewhere in the comments @Lolodomo suggests someone make a feature enhancement request for adding the capability to dynamically disable discovery for a binding.
Maybe we can introduce 3 configurable levels of discovery per binding:
- auto-discover every time the binding starts
- auto-discover only when triggered from UI (+ sign, then selected that binding)
- do not auto-discover for this binding
That way any user can configure it the way they want.
PS please when building it make sure it’s configurable in the bridge thing including via textual thing config option.
It was reported by myself a year ago as well. Using non-sensical thing ids is not a satisfactory workaround for me, neither is fighting windmills. So I just learned to live with it.