Bluetooth not elsewhere usable when flicd is running?

[jschildgen]

I want to use my Raspberry Pi 3's Bluetooth adapter not only for flicd but also for another tool to control my window shades.

https://bitbucket.org/jeremynoel476/smartblinds-diy/overview

Isn't it possible to work with other Bluetooth devices when flicd is running?

# hcitool lescan
Enable scan failed: Connection timed out

# python control.py -t TH:EE:MA:CC:AD:DR:ES -c move_target -a 80
Can't down device hci0: Device or resource busy (16)

[frog32]

Having the same issue here. What happened with the bluez friendly version of flicd?

[Emill]

Hi. We still have https://github.com/50ButtonsEach/fliclib-linux-dist. What other Bluetooth devices would you like to connect to?

[frog32]

My intention is to use this together with https://github.com/home-assistant/home-assistant where I use other BLE devices like the XIAOMI MI Flora sensor for example. Will have a look at https://github.com/50ButtonsEach/fliclib-linux-dist

[reefbarman]

So this is an issue for me as well, I'm using this to interface with my Flics but I also want to connect a bluetooth speaker and I currently can't do both

[fabianbergmark]

We might have a look at bluez again to see if it's possible to use it instead of HCI. Until then you have to get two BT adapters.

[lrucker1]

I've got two BT adaptors but I'm still having problems

I'd been using homebridge and noble on a raspberry pi before installing flic. I added a USB dongle for flic, but I'm still getting disconnects. By default noble uses hci0; the flicd should be using hci1 homebridge.err.txt

hci1: Type: BR/EDR Bus: UART BD Address: B8:27:EB:7B:CE:2E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1916 acl:0 sco:0 events:42 errors:0 TX bytes:2274 acl:0 sco:0 commands:169 errors:0

hci0: Type: BR/EDR Bus: USB BD Address: 5C:F3:70:85:2F:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:978 acl:0 sco:0 events:52 errors:0 TX bytes:2455 acl:0 sco:0 commands:52 errors:0

this is my flicd.service [Unit] Description=flicd Service

[Service] TimeoutStartSec=0 ExecStart=/home/pi/fliclib-linux-hci/bin/armv6l/flicd -f /home/pi/fliclib-linux-hci/bin/armv6l/flic.sqlite3 -s 0.0.0.0 -h hci1 Restart=always RestartSec=3

[Install] WantedBy=multi-user.target

[Emill]

Could you be more detailed exactly what's wrong? Is it Flic that's failing or your other software?

[lrucker1]

The other software works fine when Flic isn’t installed. It keeps cycling through HCI socket errors which apparently causes it to disconnect and restart scanning. This is the behavior I got before I realized I needed the second adaptor, but now they should each have their own so they shouldn’t conflict:

Sat, 16 Sep 2017 04:55:55 GMT hci set event mask - writing: 01010c08fffffbff07f8bf3d Sat, 16 Sep 2017 04:55:55 GMT hci onSocketError: Network is down Sat, 16 Sep 2017 04:55:55 GMT hci set le event mask - writing: 010120081f00000000000000 Sat, 16 Sep 2017 04:55:55 GMT hci onSocketError: Network is down Sat, 16 Sep 2017 04:55:55 GMT hci read local version - writing: 01011000 Sat, 16 Sep 2017 04:55:55 GMT hci onSocketError: Network is down Sat, 16 Sep 2017 04:55:55 GMT hci read bd addr - writing: 01091000 Sat, 16 Sep 2017 04:55:55 GMT hci onSocketError: Network is down Sat, 16 Sep 2017 04:55:56 GMT noble stateChange poweredOff Sat, 16 Sep 2017 04:55:56 GMT hci set scan enabled - writing: 010c20020001

On Sep 16, 2017, at 2:43 AM, Emill notifications@github.com wrote:

Could you be more detailed exactly what's wrong? Is it Flic that's failing or your other software?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/50ButtonsEach/fliclib-linux-hci/issues/49#issuecomment-329958150, or mute the thread https://github.com/notifications/unsubscribe-auth/ASToZkepT8o69H0U5BQWr6U4pprwy1wTks5si5hSgaJpZM4MRoH3.

[aptonline]

I too have the same issue. Have the flicd running as a docker container (thanks to https://hub.docker.com/r/pschmitt/flicd/ ) and this seems to take control over the adapter so home assistant Bluetooth tracking (also running in a docker container) can no longer access the device.

Any planned fix?

[Emill]

Hi. Our only current solution is that you use our old BlueZ library: https://github.com/50ButtonsEach/fliclib-linux-dist.

[aptonline]

Thanks for posting, what other potential solutions may be in the horizon? Is it down to how the library’s work?

[fabianbergmark]

We don't have another solution right now. We initially wanted to use BlueZ but it was then to buggy and lacked features we need. The HCI library lets us control everything but unfortunately takes over the adapter. You can buy a second adapter.

[mapeje]

I have the same issue trying to use the great Ruuvi ble tags together with Flic buttons in Node-Red. When I start flicd, the Ruuvi tags dissapear... As more ble sensors and devices becomes available, it would be great to have them run together.

[Emill]

Unfortunately BlueZ which is otherwise the commonly used Bluetooth stack on Linux didn't provide the stability, features and responsiveness that we would like for Flic. That's why we made our own direct implementation. It will use one HCI device, so if you want to use Bluetooth for something else you can add an extra dongle. If you want to share one Bluetooth controller you can always implement the Flic 2 protocol yourself for your chosen Bluetooth stack, according to our protocol at https://github.com/50ButtonsEach/flic2-documentation/wiki/Flic-2-Protocol-Specification.

[mapeje]

Thanks, I see. Too bad.