Mark Herwege

@andrewfg I don’t think there is anything specific in the code that would restrict the finders to binding add-ons. In fact, it correct discovers the Neeo transport in my network....

> The UI already show suggestions for transports. I may not have included persistence (need to check) as I assumed they were not discoverable with the logic so far. I...

@holgerfriedrich Here is how it looks for me:

@holgerfriedrich I found out what the issue in the UI is. I will provide a fix in the 'other' tab. As indicated, I would keep making them more prominent in...

> @mherwege I am a bit confused; can you please clarify what you mean by "3rd party add-ons" versus "market place add-ons"? If you look in OH under settings, in...

> We don't have a good way of providing metadata there and rely on the subject only. I thought that would be the issue. Could it be an option to...

In the same context, when developing the finder service, we struggled with the separation between the Addon class and AddonInfo class. It felt a bit complex, ad often the info...

> With all the finders in place, just one question regarding manually installed add-ons.... Would it make sense to suppress suggestions for add-ons installed manually? Just got KNX suggested -...

> I just wanted to make sure that users do not get suggestions for stuff that they already have. And right now, it shows them in the add-on store suggestions,...

> I don't think this is a good idea. IMO ALL default persistence should be removed, because it does cause a lot of confusion, e.g. RRD files (or tables in...