New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
August Bluetooth lock constantly disconnecting using yale Bluetooth integration. #116366
Comments
Attaching some more error logs if it helps:
These are 3 example of repeated logs in the last 24 hours |
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) yalexs_ble documentation |
I'm experiencing the same issue. I have 3 locks, two that are quite close together on my main level and one in my basement, which is also where my HA box is. The August locks are the only Bluetooth devices I use with Home Assistant. I have a Sena long range BT adapter on a USB extension as well as an Olimex ESP32 proxy (using POE), though I've been trying to get it to work on a single device (ideally). The behaviours I had:
I did use Edit: Looked it up, and RSSI for the locks are -46, -66, -69 Ideally, I'd be able to configure my adapter to be active scan, but also filter by the devices I specify. I spent a bunch of time digging into BlueZ and Bleak to see what scan options there are, and BlueZ does have a Anyway, I suspect the issue (or at least mine) isn't with the August integration but how HA Bluetooth works. I'm still learning a lot in this area and would love more pointers on how to debug though. I'm a developer by trade, so happy to spend time in code as well (as I have time). |
HAOS 12.3 has BlueZ 5.75 which has some stability fixes that might help I'd also try ESP-IDF 4.4.7 on the Olimex board as there are some known issues with active scan esphome/issues#5119 |
I've just updated and HAOS with no change. I have also tried removing all Bluetooth proxies from my network, with no change |
Did you try only using the Bluetooth proxies after updating them to 4.4.7 and disabling the config entry for the local adapter? esphome yaml:
|
@bdraco I updated mine last night, so far so good, but I'll need a couple of days to be sure. I'll report back here. I'm curious if there's a way to keep tabs on signal strength and connection status of the locks? |
You can enable debug logging and the advertisements and rssi will show up in the log.
|
@bdraco ESP-IDF update seems to have fixed the hanging issue, same with the HAOS update. However, response times seem to be pretty slow at times. Trying a few different combos of adapters/sensors. I have my Olimex up in the front hall now, basically about 5' from the two doors there, and a basic ESP32 proxy (just a generic ESP32) in the basement about 5' from that door, and the BT adapter in the basement. I've tried with various forms of them enabled, i.e. currently running just the proxies and not the adapter to see if having less signal overlap is helpful. Any suggestions? I've also tried working on a custom esp32_ble_tracker component, by sub-classing the main one, with the idea of allowing it to make use of the whitelist feature. I can't seem to get the config to play nicely with the bluetooth proxy component though. I'm still a bit new in developing on the platform though. |
Sorry I don't have any suggestions for making it faster. All of mine are very quick when using the proxies. The local adapters are a bit slower so I dont use them for production |
@bdraco sorry to keep bugging you...there doesn't seem to be a good place to ask more technical questions around the august/esphome stuff (and the docs for building components are very sparse...especially tricky as python/c++ are languages I've worked with really)
I appreciate the help. |
Passive. But I also have HomeKit setup since the HAP spec sends notifications passively. The yalexs-ble library knows how to watch for them. See https://www.home-assistant.io/integrations/yalexs_ble/#push-updates
There is no way to do that currently.
I don't think that is possible.
|
Do you have them in a separate home, or the same? I had tried a separate home previously but it was annoying. Though now that I’ve re-read that section, I mis-interpreted the “can’t use HA HomeKit controller” as meaning that it had to be on a different home. I suppose I could have it in the same home but just hidden with an obscure name. I also just tried setting up my proxies using |
Its the same home. |
So I have now tried this and can confirm it fixed my issue. I also tested using the arduino framework with no version and this also worked. As soon as I enable either of the bluetooth adapters connected to my homeassesistant server, the lock stops responding. Definitely seems like some stability issues on the native bluetooth implementation in HA, noting that I am on the latest version of HAOS (Generic x86-64 12.3) and home assistant (2024.5.3) |
@bdraco FYI, I have a draft PR up to use the ESP-IDF scanner whitelisting...seems to be super snappy so far on my setup. I think it'll be a useful feature for the Yale Bluetooth integration. I can look at updating the docs if/when this PR goes through if you think that would be useful. It also allows me to be specific about which proxy is used for which lock so that there's no overlap. |
Originally posted by @bdraco in #100275 (comment)
I saw the above comment in a now closed issue, however I am experiencing exactly this. I have had the August bluetooth lock for a few months now, and at first it integrated with HA well, with the occasional drops here and there. Lately however the lock is constantly unavailable with the yale bluetooth integration constantly in a state of initializing or Failed to connect.
The logs reported in the HA UI are very similar to the ones listed in the refernced issue, and when I check the bluetoothctl logs, I see the following constatnly:
I have tried factory resetting the device, powering it off for some time, moving it closer to the Bluetooth dongle (is it usually 3 meters away in direct line of sight) enabling and disabling the internal and external Bluetooth adapters (I am running HAOS on a trigkey G4 mini PC, with a usb Bluetooth external dongle from the HA supported list - on a USB extension cable) but nothing seems to bring it back.
The lock connects fine to the august mobile app, but i am running out of ideas on how to get it back into HA. Please let me know if there is anything I have forgotten to mention, and thank you for any help.
The text was updated successfully, but these errors were encountered: