August Lock Pro Gen3 connects and disconnects Yale BLE using Bluetooth proxy #132018
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) yalexs_ble documentation |
|
I've had the best luck with esp-idf 4.4.8 with my Gen3 |
|
I'm using a GLi s10. YAML below in case it helps substitutions:
name: "entryclosetgliproxy"
friendly_name: entryclosetgliproxy
esphome:
name: ${name}
friendly_name: ${friendly_name}
project:
name: esphome.bluetooth-proxy
version: "1.0"
# turn on Power LED when esphome boots
on_boot:
then:
- output.turn_on: power_led
esp32:
board: esp32doit-devkit-v1
framework:
type: esp-idf
# Configuration fo V2.3 hardware revision
ethernet:
type: IP101
mdc_pin: GPIO23
mdio_pin: GPIO18
clk_mode: GPIO0_IN
phy_addr: 1
power_pin: GPIO5
# Comment the above and use this instead for V1.0 revision of the hardware
# ethernet:
# type: LAN8720
# mdc_pin: GPIO23
# mdio_pin: GPIO18
# clk_mode: GPIO17_OUT
# phy_addr: 1
api:
logger:
ota:
platform: esphome
dashboard_import:
package_import_url: github://esphome/bluetooth-proxies/gl-s10.yaml@main
esp32_ble_tracker:
scan_parameters:
active: false
# Bluetooth LED blinks when receiving Bluetooth advertising
# on_ble_advertise:
# then:
# - output.turn_on: bluetooth_led
# - delay: 0.5s
# - output.turn_off: bluetooth_led
bluetooth_proxy:
active: true
button:
- platform: safe_mode
name: Safe Mode Boot
entity_category: diagnostic
## DEVICE SPECIFIC CONFIGURATION
# network LED (white one) configured as status led
status_led:
pin:
number: GPIO32
inverted: true
# button on the side labeled RESET
binary_sensor:
- platform: gpio
pin:
number: GPIO33
inverted: true
name: "Reset Button"
# output settings for LED's marked Power and Bluetooth
# power LED use: see code line 12
# bluetooth LED use: see code line 41
output:
- platform: gpio
pin: GPIO14
inverted: true
id: power_led
- platform: gpio
pin: GPIO12
inverted: true
id: bluetooth_led
# since these pins are broken out inside and labeled as I2C pins they're configured here
i2c:
sda: 15
scl: 13
scan: true |
|
I tried, but I can't even get it to connect at all when I use esp-idf, even if I use 4.4.8. At least with the arduino framework, it actually connects, and I can get it to carry out commands, albeit with the hiccup of becoming unavailable first. Any other thoughts? Again, I used both of my August Pro Gen3 for a long time with Yale BLE + bluetooth proxy without issues, and even currently my Yale Assure Lock 2 works well. |
|
One more detail. When I control the lock using the August app the lock disconnects from the proxy and becomes unavailable in home assistant momentarily but reconnects after a few seconds/minutes showing the correct state. |
The problem
I've have two August Lock Pro Gen3 for a very long time, and used them with Yale BLE and bluetooth proxies without issues. I used the Lilygo-tdongle-s3 as my proxies and used them with the arduino platform. A few months ago they stopped connecting, but it took me a while to realize it as one of them was close enough to my NUC that it continued to work without issues. So I'm not really sure when the problem started. Based on some ready I'm suspect it may have been around 2024.4, but I'm unsure.
Since I realized they weren't connecting, I've started to troubleshoot them and have used a number of different configurations, all without success. The configuration that comes closest to working is the following.
With the above configuration the locks connect, but immediately disconnect when I send the lock or unlock command, and the reconnect, at which point I can retry the command and most of the times it works. If I wait a minute and try the command again, the behavior repeats.
I've also tried using esp-idf, with the following configuration, as well as leaving the version and platform_version to their defaults:
But the lock doesn't even connnect at all with these, it keeps disconnecting and reconnecting. See logs below.
As far as the esp_ble and bluetooth proxy I've used the following, but have also tried leaving the interval and window to the defaults.
Last bit of detail is a I have a Yale Assure Lock 2 that is working great, with the proxy, and with both arduino and esp-idf configurations, so this seems to be related to the August locks only.
What version of Home Assistant Core has the issue?
2024.11.3
What was the last working version of Home Assistant Core?
cannot remember
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Yale Bluetooth
Link to integration documentation on our website
https://www.home-assistant.io/integrations/yalexs_ble/
Diagnostics information
Logs when using esp-idf. The lock MAC is 78:9C:85:05:1C:DE
Logs when using the arduino platform. This is what happens when I send a commend to the lock.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: