Closed AutomationD closed 6 years ago
There might be another BLE operation already running. This can result in all kind of error messages on gatttool.
My "No route to host (113)" issues were caused by another bluetooth device suddenly recognised after a dist-upgrade and taking the position of hci0.
@jmtatsch how were you able to localize this error? I'm still haveng same issue.
@kireevco I couldn't get a manual connection with hci0 anymore because my stray bluetooth adapter didn't support BLE. Thats when i realised that the device behind hci0 must have changed.
@kireevco How far are your Bluetooth dongle and the Xiaomi sensor apart? I had the experience if the distance is larger than 5 meters or if there are obstacles in the way (concrete wall, furniture, TV, ...) there are quire frequent and unpredictable connection issues.
No progress since July --> closing it. If the problem still exists, please re-open.
Hi, I'm trying to reproduce this error, and here's what I've been able to do so far. Please give me some hint of the direction to continue troubleshooting, if possible. Thanks.
It almost feels like there is some 'read mode' that is not enabled properly. But after scanning again I can query the data.
Any thoughts?
Cross bug filed to home-assistant until we understand the nature of the problem https://github.com/home-assistant/home-assistant/issues/5918