3rd Party Bluetooth Binding. Beta testers needed

vkolotov · January 9, 2018, 7:02pm

That is normal. Some mobile phones do not allow you to keep your phone in “discoverable” state. As you have notice, your iphone stops advertising after 30 secs or so, the same thing happens for some android phones. Not all of the mobile phones stop Bluetooth advertising btw, it really depends on the manufacturer of your phone.

There is a workaround for this, you can install a Beacon emulation app that should force your phone to keep advertising BLE packets. In this case the Bluetooth binding should recognise your phone as a BLE enabled device.

Please let me know if it works for you.

@Confused ^^

vkolotov · January 9, 2018, 7:07pm

Thanks for reporting this, this is normal for now and should appear for everyone.

Celaeno1 · January 9, 2018, 7:26pm

@vkolotov Thanks for Information. I ordered a BLED112 today. It will arrive on Friday. Then I can test it.

vkolotov · January 9, 2018, 7:56pm

Yeah, there is definitely something wrong with your Bluez. The upgrading process for Bluez is quite cumbersome and error prone. Could you please double check what version is running on your RPi?

sudo systemctl status bluetooth

The output should be something like that:

pi@raspberrypi:~ $ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2018-01-09 13:36:26 NZDT; 19h ago
     Docs: man:bluetoothd(8)
 Main PID: 18131 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─18131 /usr/libexec/bluetooth/bluetoothd

Jan 09 13:36:26 raspberrypi bluetoothd[18131]: Bluetooth daemon 5.47
Jan 09 13:36:26 raspberrypi systemd[1]: Started Bluetooth service.
Jan 09 13:36:26 raspberrypi bluetoothd[18131]: Starting SDP server
Jan 09 13:36:26 raspberrypi bluetoothd[18131]: Bluetooth management interface 1.14 initialized

Or you can use bluetoothctl utility. In general, this utility is actually very useful for debugging.

pi@raspberrypi:~ $ bluetoothctl
[Adapter]# version

This should print:

Version 5.47

Please let me know how it goes. Thanks.

kubawolanin · January 9, 2018, 7:59pm

Hey @vkolotov,

[20:58:35] pi@home:~$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2018-01-09 18:35:49 CET; 2h 22min ago
     Docs: man:bluetoothd(8)
 Main PID: 24888 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─24888 /usr/libexec/bluetooth/bluetoothd

Jan 09 18:35:49 home bluetoothd[24888]: Bluetooth daemon 5.47
Jan 09 18:35:49 home bluetoothd[24888]: Starting SDP server
Jan 09 18:35:49 home bluetoothd[24888]: Bluetooth management interface 1.14 initialized
Jan 09 18:35:49 home systemd[1]: Started Bluetooth service.

[20:58:36] pi@home:~$ bluetoothctl
[bluetooth]# version
Version 5.47

Thanks!

vkolotov · January 9, 2018, 8:31pm

Right… I see now. Looks like the “openhab” user does not have permissions to access Bluez DBus interface.
Have you done 8 to 11 points from here?
https://github.com/sputnikdev/bluetooth-manager-tinyb#building-bluez-from-sources

Edit Bluez DBus config to add a permission to access Bluez for the bluetooth group (/etc/dbus-1/system.d/bluetooth.conf):
<busconfig>
  <policy user="root">
    ...
  </policy>
  <policy group="bluetooth">
    <allow send_destination="org.bluez"/>
  </policy>
  ...
</busconfig>

Add openhab user to the bluetooth group:
sudo usermod -a -G bluetooth openhab

Reload service definitions:
sudo systemctl daemon-reload

Restart bluez:
sudo systemctl restart bluetooth

Simsal · January 9, 2018, 8:32pm

Hi!

congratulation for reaching this state!

I tried installing your binding, getting following errors:

    2018-01-09 21:21:08.565 [WARN ] [ace.internal.BindingExtensionHandler] - Installed bundle, but failed to start it: Could not resolve module: org.sputnikdev.org.eclipse.smarthome.binding.bluetooth.transport.bluegiga [239]
      Unresolved requirement: Import-Package: org.sputnikdev.bluetooth

    2018-01-09 21:21:10.341 [WARN ] [ace.internal.BindingExtensionHandler] - Installed bundle, but failed to start it: Could not resolve module: org.sputnikdev.org.eclipse.smarthome.binding.bluetooth.transport.tinyb [240]
      Unresolved requirement: Import-Package: org.sputnikdev.bluetooth

    2018-01-09 21:21:30.395 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "DFU Control Point" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:30.425 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "DFU Packet" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:30.965 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Bond Management Control Point" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Conditional]) write ([Conditional]).
    2018-01-09 21:21:31.117 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "CGM Measurement" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C3]) write ([C3, C1, C2]).
    2018-01-09 21:21:31.136 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "CGM Session Run Time" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C1]) write ([C1]).
    2018-01-09 21:21:31.155 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "CGM Session Start Time" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C1]) write ([C1]).
    2018-01-09 21:21:31.195 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "CGM Specific Ops Control Point" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C1]) write ([C1]).
    2018-01-09 21:21:31.213 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "CGM Status" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C1]) write ([C1]).
    2018-01-09 21:21:31.302 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Cycling Power Control Point" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional, C1, C2]) write ([Optional, C1, C2]).
    2018-01-09 21:21:31.381 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Cycling Power Measurement" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C3, C4, C5, Optional, C1, C2]) write ([C3, C4, C5, Optional, C1, C2]).
    2018-01-09 21:21:31.416 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Cycling Power Vector" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional, C1, C2]) write ([Optional, C1, C2]).
    2018-01-09 21:21:31.535 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Descriptor Value Changed" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.333 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "LN Control Point" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional, C1, C2]) write ([Optional, C1, C2]).
    2018-01-09 21:21:32.427 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Location and Speed Characteristic" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional, C1]) write ([Optional, C1]).
    2018-01-09 21:21:32.582 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Navigation" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional]) write ([Optional]).
    2018-01-09 21:21:32.612 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Object Action Control Point" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.626 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Object Changed" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.681 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Object List Control Point" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.693 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Object List Filter" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.721 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Object Properties" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.762 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "OTS Feature" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:32.919 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "Position Quality" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([Optional]) write ([Optional]).
    2018-01-09 21:21:33.127 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "SC Control Point" is not valid neither for read nor for write operation due to unfulfilled requirements: read ([C3, C1, C2]) write ([C3, C1, C2]).
    2018-01-09 21:21:33.266 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "TDS Control Point" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:33.570 [WARN ] [pec.BluetoothGattSpecificationReader] - Characteristic "User Control Point" does not have either Value or Fields tags, therefore reading the such characteristic will not be possible.
    2018-01-09 21:21:37.052 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'bluetooth:adapter:B827EB9DF87C' to inbox.
    2018-01-09 21:22:07.907 [WARN ] [.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
    2018-01-09 21:22:08.039 [WARN ] [impl.AbstractBluetoothObjectGovernor] - Could not update governor state.
    org.sputnikdev.bluetooth.manager.NotReadyException: Could not power adapter
            at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.updatePowered(AdapterGovernorImpl.java:218) ~[?:?]
            at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.update(AdapterGovernorImpl.java:65) ~[?:?]
            at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.update(AdapterGovernorImpl.java:42) ~[?:?]
            at org.sputnikdev.bluetooth.manager.impl.AbstractBluetoothObjectGovernor.update(AbstractBluetoothObjectGovernor.java:160) ~[?:?]
            at org.sputnikdev.bluetooth.manager.impl.AbstractBluetoothObjectGovernor.init(AbstractBluetoothObjectGovernor.java:150) ~[?:?]
at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.lambda$null$4(BluetoothManagerImpl.java:236) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]


sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2018-01-09 21:19:58 CET; 4min 19s ago
     Docs: man:bluetoothd(8)
 Main PID: 6856 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─6856 /usr/libexec/bluetooth/bluetoothd

Jan 09 21:19:58 openHABianPi bluetoothd[6856]: Bluetooth daemon 5.47
Jan 09 21:19:58 openHABianPi systemd[1]: Started Bluetooth service.
Jan 09 21:19:58 openHABianPi bluetoothd[6856]: Starting SDP server
Jan 09 21:19:58 openHABianPi bluetoothd[6856]: Bluetooth management interface 1.14 initialized

vkolotov · January 9, 2018, 8:54pm

Thanks.

The very first WARNING messages are normal, that’s when you have installed transport bundles first without installing the Bluetooth binding. So this should de ignored.

The second part is more interesting:

Looks like the binding cannot power up your adapter. Can you please let me know more info about your set up. What adapter you have? Can you also please run the “bluetoothctl” utility and see if that utility can power up your adapter? Something like that:

pi@raspberrypi:~ $ bluetoothctl 
[blahblah]# list
Controller XX:XX:XX:XX:XX:XX AZIO - Entrance hall [default]
Controller XX:XX:XX:XX:XX:XX AZIO - Living area 
Controller XX:XX:XX:XX:XX:XX Internal Adapter - Kitchen 

[blahblah]# select XX:XX:XX:XX:XX:XX -- your adapter MAC here from the result above

[blahblah]# show
Controller XX:XX:XX:XX:XX:XX
	Name: BlueZ 5.47
	Alias: Internal Adapter - Kitchen
	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: yes

Notice this:

Powered: yes

Is it “no” for you?

If so, try to power it up:

[blahblah]# power on
Changing power on succeeded

Let me know how it goes. Normally there should not be any issue in powering it up, the Bluetooth binding should cope with it.

vkolotov · January 9, 2018, 9:02pm

Hi All,

When you start testing it, could you also please report success cases and your setup configuration (hardware, OS etc) just in two words, e.g. if everything goes ok so we know the success rate.
Also, you are welcome to suggest any improvements or even start your contribution. Any contribution would be greatly appreciated.

ei_Gelb_Geek · January 9, 2018, 10:14pm

I wait for my BT Tag… that’s better solution

Hope @Confused can give you the Feedback

Confused · January 10, 2018, 8:04am

Installed an app to broadcast as an iBeacon, and it was detected and it appeared in the Inbox. Once I’d created a couple of Items from the Channels, I got the data expected.

However, being a stupid Huawei phone with its stupid power saving settings, the app gets killed as soon as I turned the screen off. However, it did appear to work each time I then manually started the app again.

So - with a constantly broadcasting beacon, it should work OK.

ei_Gelb_Geek · January 10, 2018, 12:25pm

With the Gigaset G-Tag it works perfectly

The only thing that bothers me is that more Bluetooth adapters are dependent on the range of the RaspberryPi Bluetooth. I guess it’s not possible to use a second Raspberry for example in the cellar.

This would be a solution for once around the world I guess that is not possible to program that purely in your Bluetooth Binding? This would allow expansion without being dependent on the range of the main controller?

vkolotov · January 10, 2018, 6:16pm

It is already implemented. You can use as many bluetooth adapters as possible. The thing that represents your G-Tag will aggregate all data coming from ALL adapters. That’s why it is advisable to have several adapters in your house so that your “thing” stays in range of at leat one of them and therefore stays “online” all the time.

Furthermore, if you set up the adapters properly in each room (or the rooms you want to track) and separate them as much as possible (distance between adapters), the thing will report its location based on estimated distance to the adapters. This is a nice feature - indoor positioning.

Sorry that was not clear from the instructions, I’m going to update the instructions with more info.

ei_Gelb_Geek · January 10, 2018, 6:22pm

Okay … but how communicate the second Raspberry Bluetooth with the Binding / Openhab ?

vkolotov · January 10, 2018, 6:47pm

Not sure I understand why would you need this? Sorry I can’t read German from your article above.

If you think about how would you separate the adapters, you can get some long USB cables. There are some passive and active cables. Passive cables are 5m long maximum. Active cables (extenders) are 30m long maximum. For many applications it would be enough I believe. There are some other USB range extenders like usb over ethernet cables which will give you more range…

http://www.yourcablestore.com/USB-Cable-Length-Limitations-And-How-To-Break-Them_ep_42-1.html

vkolotov · January 10, 2018, 6:59pm

Thank you @Confused for your report. Yes, a lot of mobile phone manufacturers are annoying with their “forced power settings” and bloatware. Surprisingly that a cheap Chinese phone Xiaomi Redmi 3 Pro works perfectly, furthermore it gives a superior range.

Simsal · January 10, 2018, 7:37pm

He @vkolotov,

Yesterday everything seemed to work smothly after few seconds. Today my log gets flooded with the notReadyException
About every 20 seconds i get the error message

2018-01-10 20:31:37.613 [WARN ] [impl.AbstractBluetoothObjectGovernor] - Could not update governor state.
org.sputnikdev.bluetooth.manager.NotReadyException: Could not power adapter
        at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.updatePowered(AdapterGovernorImpl.java:218) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.update(AdapterGovernorImpl.java:65) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.AdapterGovernorImpl.update(AdapterGovernorImpl.java:42) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.AbstractBluetoothObjectGovernor.update(AbstractBluetoothObjectGovernor.java:160) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.update(BluetoothManagerImpl.java:471) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.lambda$scheduleGovernor$19(BluetoothManagerImpl.java:608) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?] 

2018-01-10 20:39:08.381 [WARN ] [impl.AbstractBluetoothObjectGovernor] - Could not update governor state.
tinyb.BluetoothException: Timeout was reached
        at tinyb.BluetoothDevice.connect(Native Method) ~[?:?]
        at org.sputnikdev.bluetooth.manager.transport.tinyb.TinyBDevice.connect(TinyBDevice.java:67) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.updateConnected(DeviceGovernorImpl.java:557) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.update(DeviceGovernorImpl.java:109) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.update(DeviceGovernorImpl.java:57) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.AbstractBluetoothObjectGovernor.update(AbstractBluetoothObjectGovernor.java:160) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.update(BluetoothManagerImpl.java:471) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.lambda$scheduleGovernor$19(BluetoothManagerImpl.java:608) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]
2018-01-10 20:39:18.558 [WARN ] [impl.AbstractBluetoothObjectGovernor] - Could not update governor state.
tinyb.BluetoothException: GDBus.Error:org.bluez.Error.Failed: Operation already in progress
        at tinyb.BluetoothDevice.connect(Native Method) ~[?:?]
        at org.sputnikdev.bluetooth.manager.transport.tinyb.TinyBDevice.connect(TinyBDevice.java:67) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.updateConnected(DeviceGovernorImpl.java:557) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.update(DeviceGovernorImpl.java:109) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.DeviceGovernorImpl.update(DeviceGovernorImpl.java:57) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.AbstractBluetoothObjectGovernor.update(AbstractBluetoothObjectGovernor.java:160) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.update(BluetoothManagerImpl.java:471) ~[?:?]
        at org.sputnikdev.bluetooth.manager.impl.BluetoothManagerImpl.lambda$scheduleGovernor$19(BluetoothManagerImpl.java:608) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]

The error messages with “Could not power adapter” “Timeout reached” and “operation in progress” are alternating

Controller:
Controller B8:27:EB:9D:F8:7C BlueZ 5.47 [default]

[bluetooth]# show

Controller B8:27:EB:9D:F8:7C
	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: yes

Other Setup:
Rpi3 with openhabian ( latest snapshot builds)

Steffen_M · January 10, 2018, 7:41pm

I am runnung openhab 2.2 on Raspberry Pi 3 Jessie, with bluez version 5.47.

I successfully installed the binding and my Samsung S7 was detected. And there are many more Bluetooth devices in the inbox.

vkolotov · January 10, 2018, 8:39pm

Hi @Simsal, thank you for reporting this.

Let’s start from the beginning. Before yesterday you reported “Could not power adapter” error, how did you resolve this? Did you use bluetooth “bluetoothctl” tool to power up your adapter as I suggested earlier?

The errors “Timeout was reached” and “Operation already in progress” show that you have managed to power up the adapter and your are trying to connect to a device. What device is it? How far is it from the adapter? Just bear in mind that, if your device is too far from the adapter, the connection might be unstable. Just in general, if RSSI value is greater than -80 (meaning actually lesser, e.g. -81, -82 etc), then it is not recommended to connect to this device as the connection will be unstable. This is probably should be limited by the Bluetooth binding… it is probably a good idea. What do you guys think?

We could add a global binding setting, like a “RSSI connection threshold” that would prevent connection attempts if the device is too far.

Pease also note that the Binding can be too talkative for the initial phase of betta testing, this is done on purpose for troubleshooting. For example, the errors “Timeout was reached” and “Operation already in progress” will be probably hidden in future.

vkolotov · January 10, 2018, 8:41pm

Hi @Steffen_M, thanks for reporting this. Does your samsung phone allow you to keep Bluetooth always on (discoverable state)? Thanks.