Core: Problems installing gatttlib for Bluetooth LE tracker

[open-homeautomation]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.27

Component/platform: device_tracker/bluetooth_le_tracker

Description of problem: Libraries can't be installed automatically

Additional info: https://community.home-assistant.io/t/new-ha-0-27-and-bluetooth-le-tracker/3336/2

[open-homeautomation]

gattlib that is used to to a bluetooth LE scan. However, gattlib seems to be incompatible with Python 3.5

Instead using gattlib, we could just directly call "hcitool lescan", which would make the installation much easier for users. As the overall philosophy is to use libraries for all external dependencies, it is not clear to me, if this would be acceptable.
Any comments on this?

[holger-dunst]

I'm using this little python script for bluetooth le scanning. Please have a look at this

[danielperna84]

Alternatively, the documentation could mention the additionally required modules. They already mention the requirement for the modules the regular BT-scanner requires. for BTLE I just had to install

• libboost-python-dev
• libboost-thread-dev

then, everything went through.

[open-homeautomation]

According to the forum post, installing gattlib on Python 3.5 is a bit more tricky and might be too complicated for inexperienced users.

[shift]

I personally think this is a problem with upstream package. Specifically Ubuntu, Arch Linux works. I originally thought this to be a missing package for ARCH arm64. I'll submit a documentation MR with the details to download and install boost 1.61.0 if it ever finishes compiled on my ODROID-C2 ;)

[open-homeautomation]

It is a problem wit the upstream package. The question is: How to deal with it. Always using external libraries might bring more and more problems like this in the future as not every library is actively supported on all available platforms.

[dv8ed]

I've updated to v0.27.2, removed bluetooth packages, restarted, re-installed packages, restarted but still getting 16-09-04 09:03:40 homeassistant.bootstrap: Not initializing device_tracker.bluetooth_le_tracker because could not install dependency gattlib==0.20150805

I'm using RPi AIO.

[fanaticDavid]

I got the Bluetooth LE tracker to work by using the commands I collected in my own post here, and then running the command provided in the post here.

This was done on a Raspberry Pi 3 running Raspbian Jessie Lite, and with HASS installed using the AiO installer. This solution may not be how it was intended but it works. That, or the docs are missing alot of information.

[kolossboss]

Has anyone bluetooth LE on the Pi3 run, without incredibly slow HA UI???
After setting up root rights so "Python3" HA gets very very slow. Switches need often 10 seconds...

Are there any news to this?

[fanaticDavid]

@kolossboss I am having the same issue, to the point that I'm not using the BLE tracker. A few others have reported to have the issue as well. Have a look at this topic on the forum.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[jladefoged]

Still don't work for me in 0.40.1 (Docker on Synology NAS)

[homeassistant.setup] Not initializing device_tracker.bluetooth_le_tracker because could not install dependency gattlib==0.20150805

[homeassistant.setup] Unable to prepare setup for platform device_tracker.bluetooth_le_tracker: Could not install all requirements.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[elsbrock]

duplicate of #7851, about to be fixed with #7868

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍