-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Unreliable Bluetooth performance with August Smart Lock with Orica BTA-403 #100275
Comments
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) bluetooth documentation |
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 |
Bluetooth Error Updating
with August Smart Lock
Some more info, it periodically becomes unavailable: Attached relevant logs for when it disconnects between 20:00:58 and 20:03:25 I'm actually seeing this for other bluetooth devices too. This is an Eve door sensor on the same door for example |
How far away is your lock from your Bluetooth adapter ? |
I used a laser measurer, so 3.491m from the Bluetooth adapter with direct line of sight. |
Thats a bit far since the stated range on the lock is 20ft. From my experience the range isn't great on these. You might have better luck if you add a bluetooth proxy https://esphome.github.io/bluetooth-proxies/ or https://www.aliexpress.us/item/2255799901392975.html |
That's only 11ft away with direct line of sight 🤔 . I'm getting similar with the Eve door sensor on the same door. I've just ordered some esp32 but it wouldn't be that much closer/wouldn't have line of sight |
lol, I read that wrong :). Yeah 11ft should be ok |
I expect the Esp32 will be much better, but you could try turning on always connected in the options flow in the mean time. |
@alexandrechoske Please provide logs. Do they show the same issue as the op? |
@Samywamy10 Can you also try watching |
I'll also add some more logging to |
Will give it a better try tomorrow as it seems to be paired at the moment and I can't see it showing up in all the other devices that are
IIUC |
Hi bdraco, here it is, the logs around the time I detected it was unavaiable. Those are the only two logs that appeard.
Now by the time I write this post, the lock is working fine and connection is ok. |
Thanks. Looks like a completely different issue but the net effect is the same |
Ok got my ESP32s. I realise this is a bit unrelated to the original thread, happy to start a new issue but want to confirm where the problem lies... This is with a Bluetooth proxy about ~1.5m from the door but through a wall. You can see it takes ~4 seconds to unlock when I first trigger, but 1 second when I go to lock it. Relevant logs: home-assistant_yalexs_ble_2023-09-16T01-12-49.427Z.log In an earlier test it took 8 seconds but didn't have debug logging enabled: |
4s isn't that bad considering it has to make the connection and best case each transaction is ~100ms and you'll take at least 3 to exchange the key let alone the unlock commands. It's much faster once it's already connected. After you do a transaction it stays connected for 10-15s so once it's connected it's faster Enable always connected mode if you need it to be faster. https://www.home-assistant.io/integrations/yalexs_ble/#options Make sure you have flashed with esp-idf framework to ensure caching services works |
Also if you did the Wi-Fi based esp32s they have to share radio time between the Bluetooth and WiFi since they use the same radio. The Ethernet connected ones don't have this issue so they will be faster |
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. |
The problem
Intermittently the August Smart Lock via the Yale Bluetooth integration doesn't respond instantly, and can take up to a few minutes to respond. I've included some errors I've found in the logs, and also a debug log of when the issue actually happened.
I'm using the Orica BTA-403 which I specifically purchased as it was on the high performance adapters list. The lock is 3.491m from the Bluetooth adapter with direct line of sight
Given I ran into this issue I suspect perhaps it's something to do with the Bluetooth adapter itself being reset.
What version of Home Assistant Core has the issue?
core-2023.9.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Yale Access Bluetooth
Link to integration documentation on our website
https://www.home-assistant.io/integrations/yalexs_ble/
Diagnostics information
This captures me unlocking from Homekit at 18:43:39, which takes to 18:43:48 to actually respond, and then locking it again, which happens instantly.
home-assistant_yalexs_ble_2023-09-13T08-43-55.898Z.pruned.log
This logbook is a screenshot of what was happening. Basically I hit unlock (6:43:39 PM) , and then you can see the Lock actually responds at 6:43:48 PM, a delay of 9 seconds. I also don't know why there are duplicated events. I only hit lock and unlock once, and the lock only locked and unlocked once.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
I've also seen both of these errors:
Additional information
No response
The text was updated successfully, but these errors were encountered: