eclipse-smarthome-bluetooth-binding
eclipse-smarthome-bluetooth-binding copied to clipboard
OH 2.5 breaks binding (dependencies issue?)
Till now, I successfully used the binding in OH 2.4. I use it on a Raspberry Pi 3b+, both with the native BT adapter and with an external one (Kinivo BTD-400). Tested and working using both modules, with Xiaomi BT temperature and humidity sensors, which is the main reason why I am using this binding.
I just did a fresh new OH 2.5 install, I had the Bluetooth daemon 5.50, which I downgraded successfully to 5.47.
I installed the 3 packages using PaperUI, but the binding doesn't appear in the bindings list (Paper UI: Configuration > Bindings). Digging via the console, with bundle:list command, I see the 3 bundles are listed as "installed", they are not "acitve" like the other bundles in the list.
If i try to activate the bundles (bundle:start
Unresolved requirement: Import-Package: org.apache.commons.collections
In my (very limited) understanding, this has to do with some dependencies missing. I also read that the newer bnd system does not handle multiple versions of jars like the old system did. I tried to deactivate the other bindings in my system, to see if there was a conflict, but with no success.
See: https://github.com/openhab/openhab2-addons/pull/6467 A similar issue that has ben solved for another binding: https://community.openhab.org/t/ipcamera-new-ip-camera-binding/42771/1162
Is there a way to solve this, or at least can you help providing some instructions/commands to activate the dependencies manually?
Thank you :)
?
Did someone solve this problem?
In my understanding this binding is basically abandoned or with a very limited maintenance. Personally I gave up and moved to a different non-bluetooth device.
It seems that a dependency of the add-on that has previously been included in OpenHAB was removed. Just download the JAR file of the Apache Commons Collections library to your OpenHAB installation's addons directory (which is /usr/share/openhab2/addons
when installed via the Debian packages) and it should work immediately.