I’m glad this has already been raised as I’ve spent quite a bit of time the last couple of nights trying to pinpoint why my OH2 beta/nightlies couldn’t control my milights anymore which I mentioned briefly here in the start up script thread.
Anecdotally I think it’s something to do with the framework/karaf changes rather than the binding, partly because it was working on OH2 alpha and partly because I’m getting similar/same issue with a different binding.
I turned debugging on for the milight binding and noticed it was using the default port with a blank IP. I double checked my milight.cfg and the settings were correct and when scanning the log there was no sign of the milight.cfg file being loaded.
@Kai are there any significant differences between an extension being installed and manually adding the binding jar to the addons folder? I’m wondering if this is maybe something to look at.