Closed mohannadalsharief closed 4 years ago
Please enable debug logging and show your logs. Did you restart your RPI3 after the update?
yes multiple times
Logger: custom_components.mitemp_bt.sensor Source: custom_components/mitemp_bt/sensor.py:131 Integration: mitemp_bt (documentation) First occurred: 9:10:59 PM (10 occurrences) Last logged: 9:20:01 PM
HCIdump thread: OS error: [Errno 19] error while attempting to bind on interface 0: No such device
could you run the following command in SSH, and give the result
hcitool dev
Also try the following
sudo apt install pi-bluetooth
sudo reboot
it says command not found, am i missing sth?
I think that due to the HassOs update, some bluetooth things are missing.
do you know how I can roll ack or what shall I do
I see some others on the forum have rolled back to 4.13, but I don't have HassOs. But I think it is better if we solve this. It looks like you don't have hcitool. Did you try sudo apt-get install pi-bluetooth
? (perhaps without sudo on HassOs)
sudo command not foun, not sure what is happening
Try without sudo.
apt-get install pi-bluetooth
I though HassOs is not allowing root access
Also try to run this command again, as you would have to do with a new installation, according to the instructions.
setcap 'cap_net_raw,cap_net_admin+eip' `readlink -f \`which python3\``
One of the people on the forum have fixed it by removing the custom component, configuring the built in component, wait till that one starts receiving hci events, and then, install the custom component again.
Thanks for the help, is there clear steps to configure the built in component?
I assume that you have tried the first suggestions and they didn’t work?
Instructions are here.
bluepy and btlewrap can be installed with pip3 install bluepy
and pip3 install btlewrap
. Perhaps try to install these first, and do a reboot.
Now I am stuck waiting blutoothhd to connect ... I guess I will just roll back
On which command are you stuck? Does hcitool lescan work?
no it doesnt and using the built in component didnt work as well
I see an issue has been reported on HassOs repo as well. For now, I think it is better to roll back.
I see an issue has been reported on HassOs repo as well. For now, I think it is better to roll back.
home-assistant/operating-system#910
whats the quick way to roll back to 4.13 ?
You can revert to 4.13 with ha os update --version 4.13
There seems to be an issue with HassOs 4.14 with Bluetooth on Raspberry pi 3, as both the build in mitemp_bt component as well as the Bluetooth tracker do not work anymore after upgrading. I think it will be solved soon when there is a solution for this issue in the Home Assistant OS code. There seems to be a fix on its way, lets wait and see if that will solve this issue as well (I assume it will).
Going back to 4.13 works.
HassOs 4.15 is released, which should solve the issue.
Installed 4.15 and can confirm that it works.
running on RPI 3 and got an update to HassOS 4.14 where all my connections are gone