I bought this adapter: Long Range Bluetooth Adapter for PC, XDO Class 1 USB Bluetooth Adapter 5.1+EDR, 328FT/100M Wireless Transfer Transmitter Receiver for Bluetooth Mouse Keyboard Speakers Headphones Support Win11/10/8/7
On Arch Linux it was loading the wrong firmware. Normal Bluetooth worked but not the BLE (aka HomeKit). After following these instructions https://ubuntuforums.org/archive/index.php/t-2473662.html my 4x Level Bolt locks were immediately detected. I’m setting them up now.
Anyone seeing disconnect issues? Mine is showing unavailable even after a reboot.
Yeah, I never really got mine to work. It will be detected and then will disappear. It also never was unable to unlock.
I was having disconnect issues which in my case was a weak connection with my adapter. Once I exposed it better I haven’t had disconnect issues and it’s working as expected. Takes up to 20 seconds sometimes on the first lock/unlock, but other than that it’s been solid.
Decided to pick up a long range adapter as my august wasn’t connecting very with the new Bluetooth option.
Had mine reconnected to sidewalk for a little bit. Might try this again.
Mine disconnects as well and can take up to 20 or 30 seconds to respond to a command, but once it responds it responds to future commands within a couple of seconds. I’m keeping an eye on the esp32 bluetooth proxy project. In theory they hope to someday make it where it could work as an extension for homekit stuff, but who knows how long that will take to happen. Until then a Long range usb adapter is the best I can work with.
I’m also having 15-20 second delays on first lock/unlock. I’ve even seen some go beyond that. Has anyone found a solution for that?
Anyone been able to get this working with the new active bluetooth proxy? I was able to discover and pair, but can’t lock/unlock/read state.
Keep us posted! I have the lock but it’s not integrated with HA yet (i’m moving from HK to HA, and this is one of the last and hardest ones). And it does look like the new BLE proxy will be very useful for this integration.
I attempted to setup and ran into similar trouble as amwalters. Discovery works fine, but successfully adding the lock required repeated tries until it eventually accepted the homekit code. This resulted in many errors in the esphome logs and several device restarts. After all was done, none of the lock controls do anything. Seems like most folks with August, Yale, and Level locks are all having issues with the active bluetooth proxy. It does appear to be functioning using a bluetooth dongle directly configured in HA, or so others have reported.
Dolmasi, were you able to get yours working?
No, I have not had any success. I’m hoping they release a Matter update later this year that will provide better connectivity.
How are you getting discovery to work? I have HA running with the HomeKit integration I also have 5 iPod minis one of which is about 3 feet line of sight to the lock. I can connect with the level app just fine, but HA doesn’t discover it.
EDIT: I was able to get discovery to work, but there seems to be a bug in 2022.10.1 of ESPHome which keeps this from being able to pair using bluetooth proxy
It can now work using a bluetooth proxy as of 2022.11
So you can lock and unlock via HA?
Does the HA status get updated when you lock and unlock manually?
Do you have a directly connected BT dongle in addition to the BT Proxy, or just the Proxy?
I too have a level and have been trying to add it via the homekit controller. It shows up as a discovered item and when I try to add it I am asked for the homekit code which I enter. I get a success message that it has created a configuration for it, however the box on the integration dashboard says it failed to set up. Check the logs. This is what the logs have:
2022-11-17 14:38:20.924 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry XXXXXXXXX for homekit_controller
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/__init__.py", line 42, in async_setup_entry
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/connection.py", line 217, in async_setup
Any thoughts would be appreciated. I did notice the lock itself did an upgrade today and the notes said something about a new apple homekit sdk. I just got the lock so can’t say if it worked before that, I can say that it will currently connect to regular Apple Home.
Has anyone been able to add a level lock lately? I have tried it using HomeKit controller with a Bluetooth dongle and a Bluetooth proxy with esphome. Both methods result in the lock being discovered, however after entering the HomeKit code it fails to add to HA.
I’m following this thread in hopes of finding a solution to this. Have the level lock (it’s a great piece of hardware FWIW) and it works great with the native IOS app. I’d really like to integrate it with home assistant using a ESP Bluetooth proxy as well.
I can’t help to wonder if it has something to do with the level lock updating its firmware recently. I saw a message saying updating homekit sdk. (as I mentioned above)
How did you get it to even be seen ? I have two BLE Proxies and its been a week and they havent seen the lock