Closed TheQue42 closed 4 years ago
A bit of a python/docker n00b, but shouldnt the install try to use the binary versions from https://wheels.home-assistant.io/alpine-3.10/amd64/ ?
It might be obvious, but at least I seem to be able to solve the issue temporarily, by downloading the PyBluez-0.22-cp37-none-any.whl from the wheels above, and then manually pip-installing.
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 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I just added mine and I'm still getting this. Seems rather old. Hasn't this been fixed?
A bit of a python/docker n00b, but shouldnt the install try to use the binary versions from https://wheels.home-assistant.io/alpine-3.10/amd64/ ?
It might be obvious, but at least I seem to be able to solve the issue temporarily, by downloading the PyBluez-0.22-cp37-none-any.whl from the wheels above, and then manually pip-installing.
Could you explain how you're doing this please. I'm having the same issue running a script
Home Assistant release with the issue:
Home Assistant 0.104.2
Last working Home Assistant release (if known): Home Assistant 0.103.-something
Operating environment (Hass.io/Docker/Windows/etc.):
Docker image: homeassistant/intel-nuc-homeassistant:stable, on opensuse.
Integration:
https://www.home-assistant.io/integrations/bluetooth_tracker/
Description of problem: On start of HA, or when validating konfiguration, HA tries to install the pybluez lib, and fails.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: