I normally don't write a review as fast as this (I got my lock and installed it yesterday), but there are some important facts that I didn't realize when I bought it. This is for all my HomeKit people, I am a 100% pure Siri operated house. My requirement is that everything I buy and install must be HomeKit compatible. I don't want to deal with multiple electronic personalities in my home, it is already crazy enough as it is. I came across this lock initially because Amazon listed the older gen version on sale for under $100 (Used-Like New). I started researching to see the differences between that one and this one. The old one required a plug-in bridge in order for the lock to gain WiFi Access, whereas this one has WiFi built in. And this one is sleeker, newer, better, etc..... I am one of those who operates on the policy that if it costs more, its better, so I buy it (no judgement please). Anyway, here is the little nugget that is hidden away in the August help articles. Well, maybe it isn't that hidden, but I certainly didn't realize it. If you are using HomeKit, then the lock MUST be within BLE (Bluetooth Low Energy) range of your home hub. For me, I use Apple TV 4K as my hub. Which is in my living room. Which is about 80' or so away from the detached garage where I installed this lock. But fret not, there is a very simple work-around (which I'll get to in a minute). Install of the lock, mechanically at least, was super easy. Connecting to WiFi and getting the app set up was a bit of a pain. Now, to be fair, I use a Netgear Orbi mesh system, and my satellites were in need of an update, so its possible that played a role. But I had to reset the lock twice before I could get the thing reliably online. First few attempts, wouldn't connect. Then, it connected, but wouldn't give me a signal. Finally, I got it all squared away and the lock was good to go. Or so I thought. Then came the HomeKit part. So, you have to setup HomeKit through the August App. But, at the time, I wasn't tracking the BLE range for it to work. So I kept having problems. I ended up deleting the lock from my home through the Home app. But, when I did, even though it was gone, the lock was still registered, so I couldn't re-add it. I did some internet searching, found a help article that had the answer. I actually had to remove the lock portion (not hard, two little black clips that open out), then hold a red button on the back of the unit for 7 seconds to reset the lock. After that, I was able to get it back into Apple Home. But I still spent the next 30 minutes trying to figure out the "No Response" problem in Home. Which led me to the inter-webs, which led me to the help articles, which eventually led to the knowledge that, despite the fact that it is a WiFi enabled app.....it uses BLE for HomeKit. Seems dumb, but is what it is. Now the workaround, when you have a device setup as a hub for Home (iPad, TV, Homepod), it acts as a BLE hub as well (if you are home smart-er than me, don't judge my terminology, I'm new here and learning as a go). Anyways, when you add hub devices, they automatically act as BLE extenders. So, for example, in my home, I've got an Apple TV in the living room, which is my main hub. I then have a few HomePod Minis through the house for Siri control and ease of access. The HomePod Minis passively act as BLE range extenders (Apple never ceases to amaze). The WiFi lock on the shop no-worky, but when I move one of the HomePod Minis out to the detached garage, it acts as the BLE extender, and bam, lock works. All in all, I love that this lock only replaces the back thumb plate, that it is very discreet and no indication of a smart lock from the outdoors. It is sleek looking, makes cool robot noises, and very smooth in operation. Armed with the knowledge I have now about HomeKit operation, I can comfortably move forward with swapping the rest of the locks on my property. But, to be fair, this is a day one review. I may be back after a month of operations with some more accurate feedback. But hopefully, you the reader can be saved the time and effort it took for me to get to this point, and just skip straight to the "yay, it works!" part.
