hcitool not working #314
Comments
|
The logs mention the |
|
Yes sorry for that, my config had also Logs |
|
I'm having the same problem, after it initially working just fine |
|
Same issue here. The previous version did not have the problem. |
|
Do you all still see the issue after completely restarting your machine (e.g. Raspberry Pi)? If so, could you use the SSH add-on to type this into the terminal: |
|
Yes I have this problem also after reboot. I did this a couple of times and although sometimes it works after reboot for 1 hours or so, it false again the adpater crashes. The output of the command sequence: This output was generated while it was working ... |
|
It started to work, altough I think Im missing configuration now. Confis same as above, version: latest |
|
Maybe one thing to add: this seems to be a problem with the Home Assistant Addon. I have two other instances running on RPi0 and RPi4 and both do not have this problem. Only the addon version on my Home Assistant showing this problem. |
|
Mine works after rebooting the host indeed. Unfortunately I didn't output of the commands when it was not working, but I saw for example the name and alias were not listed, also it said |
|
@gadric @Veldkornet Thanks! I'm not quite sure what would cause the adapter to crash, but maybe it would already be a good start if room-assistant would try to recover that situation. This stuff can get really complicated since it goes down to system level, but is also packaged away in a different runtime on Hass.io. @marcinbauer85 That is just a hint that Home Assistant does not support auto discovery of device trackers and they need to be configured manually like shown here if you need them. So nothing to worry about! |
|
Hmm, yes .. I guess so. However, I tried several things, after it crashed:
The only thing worked was reboot. What I find interesting is that this problem did not occured with the old version ... Btw.: I am running my Home Assistant on an Intel NUC10. |
|
@gadric In that case scratch my original idea, if those command did not help I can't think of something else. Thanks for letting me know, saved me some time. At the moment it feels like between v2.10.0 and v2.11.0 something in the system dependencies of the Docker image updated and now causes these issues. Will have to dig a bit deeper though. |
|
Sure, let me know if I can be of assistance ... |
|
Are you all running on HassOS 4.15? Looking at their repo there were some (seemingly minor) Bluetooth changes recently. I would be interested to see if this change is really caused by the add-on update or the OS update. Would be cool if someone could try to downgrade the OS to 4.13 with I double checked the Bluetooth packages used by the add-on - those have not changed at all in-between the versions as far as I can see in the GitHub build log. |
|
So I have the error again: Running your suggested 3 commands I got: |
|
I am just testing something else ... Does it make sense that PowerTOP or Auto Suspend features makes trouble? I have PowerTOP always activated and until now, not problems. But after the last issues, I deactivated PowerTOP and rebooted. Until now, the bluetooth adapter seems to work ... |
|
I can't think of a reason why it would cause these issues, but at the same time I'm not really familiar with that tool. So no clue 🤷♂️ |
|
Yes you are right. It crashed again |
Same here 😭 |
|
I don't think Home Assistant has functionality for downgrading an add-on yet, but you could do this manually in the mean time if you want. Download and copy exactly this folder into your If you end up doing this it would be awesome if you could give status updates if it works or doesn't work. |
|
@mKeRix funny thing: today in the morning I have upgrade to 2.11.1 on all boxes. Until now it is working. However, currently there is only one Phone at home which room assistant is tracking. I am not sure if this has an impact. Do you think this could be the source of the issue? I can test to down upgrade the addon today evening when I got home. |
|
FYI, I noticed that when the Bluetooth crashes, if I restart my zwave add-on, it can't connect to the USB dongle either. I've only been using the room-assistant add-on for the past day or so, and it wasn't happening before (the USB dongles being unavailable). So I'm thinking what ever is causing the Bluetooth to crash, crashes the others too. Why it crashes is of course the question... Seems like if it's not used though (the Bluetooth) everything stays running (that's an assumption since this issue is new to me). |
|
FYI, the bluetooth update in HassOS 4.15 was to upgrade RPi bluez-firmware to 1.2-4+rpt6. |
|
@gadric 2.11.1 generated a fresher image, so if there was something wrong in the build cache it's possible that this fixed it. The code change itself should mostly make a difference for setups that run BT Classic and BLE on the same adapter, that code doesn't really do anything that should crash the adapter regardless. If 2.11.1 fixed the issue for you then there is no need to downgrade I'd say. Keep us updated! @Veldkornet Thanks for checking this. The USB issue is interesting... that's something I don't understand at all. |
|
I have been home for more than 1 hour and it still works. I will report tomorrow in the morning if it is still working. If yes, I guess then the update has fixed the problem. |
|
Still buggered for me, even after the last update. |
|
My Bluetooth device has not crashed until now. But I got the following error on my Home Assistant Add-On: |
|
@gadric That error will be handled better in a future version, in this version it's just a stopgap to prevent multiple queries from being executed in parallel. |
|
FYI, I discovered that I can get it working again by issuing the following command in HassOS:
Quicker than rebooting anyway... |
|
@mKeRix: ok thank you Room Asssitant 2.11.1 has been running through the whole night with 3 devides tracking. It has been not crashing anything. I guess this error is fixed @Veldkornet: that is interesting. I know when my BT crashed i was not able to power it up with |
|
OK, I think this set up is working for me at least. The add-on has been running since yesterday and also with the newest version is working without crashing. This works also with different devices arriving and leaving. What I have done yesterday to make this work:
Since then it is working without any issues. My config: |
|
i used the bluetoothctl power on in HassOS as described above and that fixed the issue for me |
|
I've got this issue on my very unorthodox system, so I'm assuming it's not the fault of either room-assistant or home-assistant. What I did to fix this is I created a script '/usr/bin/check_bluetooth.sh' with this code in it then added this in crontab from user root and execute it every 5 minutes. @mKeRix worth thinking about doing something similar on your side if you get a network down? |
|
Something like this was actually one of my initial ideas, I just shelved it again since somewhere earlier in this thread someone tested the commands and reported back that they didn't work to fix this specific issue. Might still be worth it to integrate this for better error handling though. |
|
After installing the lastest version 2.11.3 this problem appears again. @mKeRix: could some of the compiling went wrong again? Btw.: both |
|
The add-on build looks clean and ok to me. Maybe it could help if you could add information to home-assistant/operating-system#940 by posting the relevant dmesg info, as that would give them experts over there a more detailed look at things. |
|
I got this working again. I have a guess, what is the problem: the start order of the docker containers may cause this problem. It seems that sometimes the add on container starts earlier than the Home Assistant, then it leads to crash after some time. |
|
@gadric Hm, the add-on configuration specifies it as an |
|
Since the linked issue in the Home Assistant OS repo was just closed as fixed I will close this issue here as well. |
|
FYI: I think I have identified the problem. It seems that putting BT Adapter into sleep causes many problems. If I deactivate auto suspend, this problem seems to be gone. |
|
I found that following the steps on this link resolved it for me. It appears there was an issue with a later version of bluez which was choking Bluetooth. |
Describe the bug
Can't get any reading from BTC:
10/25/2020, 11:18:10 AM - error - BluetoothClassicService: Command failed: hcitool -i hci0 cc "88:63:DF:8A:1B:DC" && hcitool -i hci0 rssi "88:63:DF:8A:1B:DC"To reproduce
Installed on latest HassOS 4.15, on a RPI 3B+
Relevant logs
Relevant configuration
Expected behavior
Get reading of the BTC RSSI
Environment
The text was updated successfully, but these errors were encountered: