Skip to content
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

Yale Doorman stopped working with CSR8510 Bluetooth Dongle #121074

Open
MacL3an opened this issue Jul 3, 2024 · 1 comment
Open

Yale Doorman stopped working with CSR8510 Bluetooth Dongle #121074

MacL3an opened this issue Jul 3, 2024 · 1 comment

Comments

@MacL3an
Copy link

MacL3an commented Jul 3, 2024

The problem

First off thank you for your time working on this integration, truly appreciated! I have donated to the Maui Foodbank.

So I have successfully used my Yale Doorman with my CSR8510 A10 Bluetooth dongle (on a 3m extension cord) for quite some time.

Suddenly, the lock stopped responding. I get an error saying No advertisement received before timeout; Try moving the Bluetooth adapter closer to.... It is within 2 metres with clear sight.

The lock works fine if I try to connect via my phone (it connects via Bluetooth) and if I re-connect the ESPHome I had before it also works. But for some reason it has stopped working via the bluetooth dongle (which I have previously found more reliable than the ESP Home solution).

I have tried downgrading to an older backup of HA Core and also several versions of Home Assistant OS, 10.x, 11.5 and 12.4.

Any ideas how I can debug this further? Is there a way to confirm that nothing is wrong with the Bluetooth adapter?

What version of Home Assistant Core has the issue?

core-2024.6.4

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

I have tried enabling the debug logging for Yale Access Bluetooth, stopped logging, downloaded the file, but I honestly cannot see much of relevance in the logs. I do realise there is a lot of noise in the logs, I haven't been following a no errors in log policy for my home... 😅

The only thing I find when I search for Yale is:
2024-07-03 15:39:03.116 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('yalexs_ble', '639c1e1c57c686edb0dda09afb5822af'): 629.766454457}

Nothing when I search for Bluetooth. I cannot even find the error message I get in the GUI?
No advertisement received before timeout; Try moving the Bluetooth adapter closer to..."

Perhaps I'm doing something wrong when looking in the logs?

home-assistant_yalexs_ble_2024-07-03T14-09-37.017Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jul 3, 2024

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (yalexs_ble) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of yalexs_ble can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign yalexs_ble Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


yalexs_ble documentation
yalexs_ble source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants