Just chiming in the report the same issue here on a brand new August lock pro installed a few days ago and updated to firmware 1.59.0-1.13.2 as part of the set up process. Glad I came across this thread as the Z-wave functionality was the main driver for purchasing this lock (“upgraded” from the 2nd gen HomeKit version) to work within my SmartThings ecosystem, along with ActionTiles as my main user interface on a wall mounted tablet and phone.
I was just in the process of scouting for a Z-wave repeater on Amazon as part of a troubleshooting step before stumbling on this thread. I concluded after throughly reading through this thread that it appears to be isolated to a FW bug on the August side (not definitive, but just IMO). I also agree with a previous poster, that August should have caught this bug during code review and testing before deployment.
I’ll be reaching out to August to also report and to further amplify the issue.Thank you all for your input on this. I’ll continue monitoring this thread and hope August provides a bug fix for this ASAP. As it stands currently, the Pro version is no different in core functionality than my previous 2nd Gen HomeKit August lock
Factory reset didn’t fix the issue for me, even temporarily. I did push back on August support for better answers and they have sent firmware version 1.59.0-1.8.15 to my lock and asked me to let them know if it resolves the issue for me. Just installed it and will test later tonight and post an update here.
Will be interesting to hear how the new firmware works.
For another data point, i have 2 of these locks that i have had for over a year and am not having any of these troubles (I am using a custom dth and have both locks connected to ST v2 hub, as well as the August connect and keypad).
While i understand the frustration (you should have seen the original firmware in these things; i think i reported 5 or 6 z-wave bugs myself), and the desire to have manufacturers thoroughly test before release, some issues are just not detectable until they get into the real world.
I’m also very interested to see what the results here are. Would be great to have this issue put to bed. It’s very disconcerting to have only partial and partially reliable control over the primary means of securing my home.
So far so good. And I was able to easily and consistently reproduce the issue prior after waiting just an hour with the other firmware. I believe the firmware that is pushed to me now was the prior released version before this last update, can anyone confirm that? I’ll let it sit idle overnight and re-test in the am.
Just found this thread as having same issue. CURLing the smartthings api to lock/unlock. Doesn’t work unless I’ve recently used the August app on the lock.
1.59.0-1.8.15 firmware pushed through August support is working without issue for me. I’ve reported that to them, and asking for more information on the development of a fix for future releases. If they share anything useful, I’ll let you all know.
Thanks. I emailed them too and got the same update. It’s been a few hours and things seem to be back to normal. But as they suggest I’m going to keep testing over the next few days and let them know how it’s behaving. I recommend others with this issue ask for an update. It’s pretty painless. They push the update then when you connect to it over BLE it starts the update. Then you reboot your lock and your connect bridge (if you have one).
Judging by their version numbering I do think this is the previous version of their firmware.
I’m having the same issue. Just bought the locks and thought I was going crazy. Thanks to everyone else reporting it, I am doing the same. Hopefully they have a fix soon. My firmware is 2.2.1 on the connect and 1.59.0-1.13.2 on the lock
The email address, and even a phone number, are posted near the beginning of this thread. When you email them I’d describe what you’re seeing in your own words. Then link to this forum. I’m not sure if they’ll send you a firmware push immediately based on that but I’d at least wait until their first reply before asking for a downgrade.
As an aside, I tested this morning after a good 12 hours of inactivity from the August app and the commands from my SmartThings app and button+routine I have set up worked without issue.
I had an ongoing ticket w/ August. I asked in the latest reply to downgrade to 1.59.0-1.8.15; they responded in about 8 hours with instructions to reconnect via the App + BT to get the code downloaded to the lock.
Also, I just noticed that the batteries seem to be running down much quicker since the last firmware. I changed my batteries right around the time the last new firmware came out and now I’m already getting notified that my batteries are critically low. It’s only been about a month.
Update Also reached out to August support via phone call Jul 23 to request a firmware rollback to be pushed out to my account. I’m now on 1.59.0-1.8.15 for the last 2 days (initialized Jul 23) and happy to report Z-wave functionality using SmartThings has been restored (tested both in house and remotely). I’d also encourage all affected users to contact August support to have them push this FW version out to your account in the interim, until a permanent fix is released.
In my case, an email notification from August was received a few hours following the approved request. Once in bluetooth range, you’ll be prompted to update your firmware. Once updated, August is advising to reboot your Z-wave hub e.g. SmartThings hub, as well as your August lock.
Just received notice for my ticket with them that the rollback is available. They asked for some info on my SmartThings system, so I’m not convinced they know the problem is on their side.
Just updating for future visitors. I contacted August support yesterday and sent them this:
Date: Wed, 24 Jul 2019 10:36:46 -0700
Subject: August SmarLlock Pro & Z-Wave not working reliably.
To: support@august.com
Hi.
My two August SmartLock Pros are not functioning correctly.
Specifically, they’re not responding to z-wave commands from my SmartThings hub.
The issue is best described here:
Both of my locks are running firmware 1.59.0-1.13.2.
In the thread, people are reporting that downgrading to 1.59.0-1.8.15 fixes the issue.
I’d like to downgrade if possible. How can I arrange for the older
firmware to be pushed to my devices until a better solution is implemented?
They got back to me the same day, and pushed 1.59.0-1.8.15 to my locks (first they only did one, and I poked them back to get the second one finished). It has only been a day, but so far I cannot repro the issue any more. Seems good. I’ll report back if my problems come back, so if you don’t hear back from me, then assume it is working.
Based on how easy it was, and how quickly they were able to do it, and the success that others are seeing, I strongly recommend other people seeing this issue send a similar message to them.
