I also already raised the question but no one answered. It is also not understandable for me why this disfunctional binding (for years already) is still listed as one of the number one featured bindings onthe webpage:
For those that are not aware, there is currently a lot of work being done to fix the official bluetooth bindings. I’ve detailed current progress and expected future developments on my post. You can also download the latest 2.5.x bluetooth snapshot jars to try out if you are using OH 2.5.
Hello everyone, I’ve been actively developing this binding for a few years, but had to slow down as priorities have changed in my life. Sorry for that. I was hoping someone could pick up my work and help to maintain the project, but unfortunately nobody did not show any will.
As I understand correctly, apache-commons is no longer included into OH by default hence the binding is not working out of the box. I’ll try to find some time on the weekend to remove the dependency. Unfortunately OH framework does not allow 3rd party bindings to specify dependencies as you would normally do in OSGi so that they automatically get installed.
Let me know if there are some other critical issues that need to be fixed.
I created this issue ticket, for the reported problem. I’m having the issue as well:
Really sucks that I spent an entire day trying to get Bluetooth to work with no success. It shouldnt be that hard. I know this thread is only a workaround for the official binding, but I failed trying to get that to work as well… As well as other things too. Sigh. Btw I have Pi4 on openhab 2.5+.
I don’t own MiFlora sensors, so can’t test myself, but I think you can use MQTT to communicate with them using the native bluetooth integration + python script in daemon mode, as shown in the post linked by @NCO, and also discussed here: