I did this for about an hour or so and while I was able to have HASS find the lock and even recognize it’s a lock with the HomeKit logo in my devices.
However, it’s when I go to configure the lock when I have that same error.
I’m never able to get it configured. It sucks cause it’s the only device in my home unable to connect aside from my Secrectlab MAGRGB led light strip.
If someone finds a way to make it work or hopefully a proper integration is built with level please ping me !
how close is your HomeAssistant box or Bluetooth proxy? In my experience, it needs to be very close to complete the pairing process in HA.
They are a few feet apart but my Bluetooth range extender should be more than enough (says it’s good for up to “500 meters” with the antenna I have on it)
You mention a range extender… I think an earlier comment in this thread suggested that you can’t pair properly through a proxy (but can communicate throug them after pairing), and iirc, even suggested turning them all off during pairing so maybe the range extender is the problem. If you have a bluetooth radio directly attached t your HA instance, it might be worth a shot to turn off the range extender and see if you can try to add it then. Continuing that scenario, if it isn’t detected or can’t cmmunicate when the range extender is off, it might be worth a shot to take the lock out of the door and try to pair it while within range of said directly attached radio.
So with a bluetooth proxy extension very close to the lock are you saying that the Level Lock + would work with both Home Assistant AND apple Home Keys?
Uh… “up to” being the key phrase in that scenario. But at a few feet you should be ok.
No. when pairing with HA. HA is the homekit controller. I believe in order for Homekeys to work, it has to paired with your Apple Home.
Thanks for everybody chiming in here! I think I may have gotten my setup figured out… fingers crossed. I’ve been working on it for two weeks. The lock initally paired to HA easily, but I found very similar results to many here, especially @PalmTree. It wasn’t a reliable connection. Once the lock responded, it would work well, but it seemed like it would go to sleep after an undetermined amount of time. I reset the lock several times, adding it alternatively between the Level app and HA, and upgraded the firmware in the process.
At one point I was unable to re-pair it with HA. Tried many, many times. Eventually after I deleted a helper toggle that I had used during a previous pairing it was able to connect.
I initally was using the ASUS USB-BT400. I’m now using the Olimex ESP32-POE-ISO as a proxy. Once I got it re-paired with USB, I plugged in the proxy and disconnected the USB.
I managed to get it paired with HA while maintaining the connection in the Level app. In the Level app, I started the process of connecting with HomeKit, but at the screen where it wants the Homekit Pairing Code I successfully paired it with HA. Then I cancelled the HomeKit setup process. Now the Level app seems to think that HA is HomeKit. (When I lock or unlock from HA, the Level app logs the activity as HomeKit.)
It’s been over 24 hours, and so far the behavior from HA has been great. No delays or unresponsiveness like before. I can still lock or unlock from the Level app, as well. My proxy is about 12 feet away behind a wood stud, sheetrock wall. I am only using the Level Bolt, so I can’t speak to other functionality like NFC, HomeKeys, etc.
If it is still working the same tomorrow morning, I will order another Level Bolt and proxy for the front door. I’ll post results if I get that far.
This still working good?
Yes, the first lock has performed flawlessly ever since my first post. I have it tied to my alarm automation, so when my alarm system enters an armed state, the lock engages automatically. That’s been working great. I also manually lock and unlock it periodically when I’m home and some time has passed. It always responds quickly. The unresponsiveness I saw before seems to be gone.
I have now configured a second lock and it’s also been working great for 24 hours. I started by pairing it with the Level app and upgraded the firmware. I was NOT able to pair it to HA using the proxy board… I had to plug the USB dongle back in AND unplug the proxy altogether. Before I did that I kept getting the GATT error. Once I was only using the dongle, I was able to pair it to HA while maintaining the connection with Level app like I described before… initiated the “Works with HomeKit” on the Level app, but while it was waiting for the pairing code, I set it up on HA. Then I cancelled the setup on the Level app and it shows as paired with HomeKit.
My second lock is not installed in the door yet. It’s sitting on the end table in the living room across the house from the first lock. I have a second BLE proxy plugged in near there and the second lock is working off of it.
Thanks to this forum I was able to integrate my Level Lock - y’all are awesome! I do have one very important question though - is there a way to reset the lock without having to remove my hardware every time?
There’s a lot of talk here about how temperamental these locks can be, and because I’ve had the same experience but got them to work, I’m willing to keep fiddling, but not if it means hardware removal every time. It’s already getting old and I’ve only done it 6 times.
Assuming you can get the lock paired with HA while keeping it paired with the Level app (see my post above), if you “Remove” the lock from the Level app it factory resets the lock when you do it.
I was able to connect it to HomeKit using your pairing suggestion but it will only work for about 2 minutes before becoming completely unresponsive in Home Assistant. I’ve wanted an “invisible” smart lock like this for years, but I’ll have to return it if I can’t keep it connected. All goes gray and I die a little inside every time. 
What are you using for your Bluetooth receiver? My first Level Lock would become unresponsive. I figured out how to pair simultaneously with the Level app, AND I switched from USB dongle to a proxy board from Olimex. Since then… no issues.
Update: Since removing my WLED integration and switching to a Bluetooth dongle w/ antenna (suggested several posts ago) everything seems to be working and the connection with the Level app and HomeKit in Home Assistant is steady thanks to everyone’s suggestions here!
Now I’m just hesitant to reconnect my WLED integration… smh
I was actively typing here that my lock had quit working again, but I just heard it trigger in the other room… 3 minutes after I’d triggered it from HA. I know it takes a few seconds for the Bluetooth to reconnect, but this is extreme. I can’t expect anyone using my system to understand that, and it’s definitely cause for headache.
When it was working great I’d even ordered 3 more for other doors, but now I think I’m returning them all. I’m really upset, too, because this was exactly what I’d been waiting for.
Note these timings are using HA dev / 2023.7.x with ESPHome 2023.6.0 so it will be slower with HA versions before 2023.7.x
Thanks, bdraco! Ordered one of the recommended high performance BT dongles to try before I give up again.
My 2 locks have been struggling through the week, but latency seems to have improved with the latest HA release that contained updates to ESP/Bluetooth. Think I’ll keep them because it can only improve (I hope). That said, today I’m here to ask, how would y’all suggest I handle a disabled Identify button for my newest lock? Somehow that new lock duplicated it’s lock and identify entities, and though I was able to delete the erroneous entities, that lock has since been unavailable in HA but works fine in the Level app. 
Hi all. Has anyone been able to successfully integrate Level Lock + into HA? I have a Bolt which works perfectly in HA. I have also a Level Touch which worked great too in HA, but after upgrading to Lock + I never was able to integrate that one, it seems to be connecting but always errors out.