Open Silkjaer opened 2 months ago
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!
(message by CodeOwnersMention)
yalexs_ble documentation yalexs_ble source (message by IssueLinks)
This isn't a regression in yalexs_ble
since there aren't changes there for 2024.9.x. I removed the milestone
The Linux L2 isn't tested with this integration https://www.home-assistant.io/integrations/yalexs_ble so it may not work.
However most of the problem are usually due to the Bluetooth Adapter.
These locks seem to work best with this ESPHome Bluetooth proxy option: https://www.olimex.com/Products/IoT/ESP32/ESP32-POE-ISO-EA/open-source-hardware https://www.olimex.com/Products/IoT/ESP32/BOX-ESP32-POE-ISO/
The problem
The lock is stuck in 'initializing'.
It works great with the Yale Home (new in 2024.9.0b) and August Yale Home integration, and the Yale Access Bluetooth integration picked up the lock on bluetooth quickly, imported Offline_keys from the August integration and created new entities as it should.
But the lock continues a loop of 'initializing'.
It looks like the RSSI is -61, and the bluetooth integration doesn't appear to complain about connectivity?
Is it simply because this lock is not (yet) supported?
Logs from the yalexs_ble log:
From bluetooth debug log:
What version of Home Assistant Core has the issue?
core-2024.9.0b2
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
yalexs_ble
Link to integration documentation on our website
https://www.home-assistant.io/integrations/yalexs_ble
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response