Dear all
I have been following several threads on the topic of BlueZ as I suppose to have the same issue but not on a Raspi board. In my case I’m working on MacMini with Debian installed on. bluetoothd sees the controller and present it’s details.
[bluetooth]# show 90:27:E4:F1:01:50
Controller 90:27:E4:F1:01:50
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x00000000
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052F
Discovering: no
The Binding parts are active
openhab> bundle:list | grep -i blue
283 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: Bluetooth Binding
284 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: Airthings Bluetooth Adapter
285 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: AM43 Bluetooth Adapter
286 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: BlueGiga Bluetooth Adapter
287 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: BlueZ Bluetooth Adapter
288 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: Blukii Bluetooth Adapter
289 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: DaikinMadoka Bluetooth Adapter
290 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: RuuviTag Bluetooth Adapter
and and states the Unsatisfied Link Error as discussed on github
There was also a PR with the goal to fix the issue.
The binding documentation states, it supports (ARM… only??)
Anyway, I tried to build BlueZ myself (5.4.7) and compiled tinyB stuff as well. the files (libtinyb.so and libjavatinyb.so) are available in my java paths but still no success.
–
Meanwhile I managed that openHAB reads the native libs created from the build of tinyB. However this only drives to the next error:
Native library is out of date. Please update the native library.
I’ve got the same results when I use the current release binding, the earlier variant of @vkolotov or @cpmeister 's approach. A further research pointed me to Vlad’s comment on
But even this didn’t help me to resolve the issue.
I’ve read also the PR on github
Which from my point of view seems to be refering to the root cause of error. But @Kai when this was merged back in 2019, why do I still see an issue here with v2.5.8 ??
Cheers
Stefan