Still not having any issues with my August lock. I'm running "undefined-1.59.0-113.2" for firmware according to the app.
I deleted the August app from our phones out of fear August would push another update, making my locks useless. So, I can't say if DoorSense would still work for me via the app. The built-in driver exposes the DoorSense sensor, so I was able to mimic the DoorSense logic in RM. I also added an extra contact sensor to each door, just in case. In the year since my downgrade, I've not missed a z-wave command and the sensor has continued to function.
Side note: I'm seeing much better battery life! I just replaced them in my front door, and they were reporting 76% after a year.
Is that the latest? I actually have a lock on that firmware (I just checked all 4 of mine and they're all different 
). Maybe I just need to upgrade them all to that and try again.
Seems to be the latest, yes. I'm not blocking updates.
I just gave up and downgraded them all. Seems to be working fine. Just glad August Support allowed it. I did have to press them on it though.
I haven't forgotten about this thread. I'm currently on "undefined-1.59.0-1.8.4".. of the firmware. They have slowed down the "assistance". However, my frantic efforts I accidentally put device driver to generic z-wave lock and not using the August driver. In my case this worked flawless from a lock and unlock. However, this breaks the contact settings and doesn't pass the august sensor through. I sent them more logs that there are issues back on the 20th. Then I changed the driver it hadn't fail since then. I just set the back and I will let you know. I haven't forgotten either tied up or just not much to report back.
I just get the we cannot help you, good luck, Email from August support. I wanted to check to see if anyone has seen this with when pairing with S2. Has any paired this with S2? Or tried a different driver? Thanks.
I still think there may be an issue with driver and firmware. I got the c7 and this was worse than C5. Pairing was brutal and it took a long time. ( had reset the lock too). Wiping everyone out of the lock. Finally, when I did get the lock added to C7. August DHL didn't work at all. However, Generic Z Wave driver did. But it doesn't pass senor contact through the device. Though, the lock did work at least. I still have my ST and I might us Hubconect overcome all of this. Great on paper but in real world this stinks.
it is a known issue. and will be fixed in next release.
Thank you.
I have two things that have done with very good results. Resetting the lock seem to resolved a lot of issues (do doing all the inclusions again too). Plus, I have setup the hubconnect to ST (WIFI August). So, this looks very promising.
@jsarcone have you tried the latest hubitat firmware? the S2 issue is fixed.
I'm able to control the lock without any issue.
only concerns is that the battery shows 100%, back when I was using ST, it was below 100%, so not sure if it is the driver issue or the lock itself is reporting something fishy.
also since I downgraded my August firmware, door sense stopped working (not even in its own app).
I am guessing you have a C7 hub due to the S2. If so, does the August lock seem to be a lot more dependable on a C7?
so far, it seems fine.
Z-wave was broken for august in ST and they gave up z-wave and rolled out the cloud integration.
I downgraded the august firmware, and with the recent 2.2.3 upgrade, it worked fine so far.
@Chen555 @cjkeenan I haven't tried the C7 again since the update to 2.2.3.119. Once I had issues with the initial platform build, I moved it back to C5. However, in 2.2.3.119 on the C5 seems to be working well too. I'm still on undefined-1.59.0-1.8.4 on the lock. There are some security issues with All August locks and I'm expecting another update to come out. I want to move forward with the firmware. I'm using HubConnect with ST too, now, Basically, Z-Wave to Hub C5, with hubconnect to ST WiFi Bridge connection. Overall, it seems to be working consistently. It gives me a reason to repurpose the ST and if the Z-Wave fails, it gives me another way to get the lock to work.
Note, I do plan on moving this back to C7 with S2. I just haven't gotten there yet.
What is your Firmware build that you are on from August?
Thank you for your comments and reply.
1.59.0-1.8.15
It sounds like you might be on a newer version. I have look into this.
I am on UNDEFINED-1.59.0-1.13.2 and I think my issues were regarding my z-wave mesh and placement of beaming devices.
Any thoughts or optimism for getting August Pro 3rd edition lock connected to Hubitat again? I see the release notes for HE seem to indicate a new driver? I am not having luck. I have it connected to HE, but the lock and unlock don't sync up at all. Seems to be on a long delay (like 30+ seconds for it to update).
I have not reset my August lock though and started all over. I will do that next to see if this helps sync up the timing of the lock status. I also have not let the August lock go to standby mode to see if HE can operate the lock after 20+ minutes.
I have 2 of these that have been working without problems on 2.2.4 (C7).
The biggest issue (other than battery related) seems to be with weak mesh or lack of nearby beaming repeaters.
The inclusion process can be slow and take some time (i didn't time exactly, but seems it was perhaps a few minutes), so i recommend patience here.
If there are problems with messages, i would recommend a repair to ensure it gets the best route. Also, if you mostly use the hub to lock and unlock, sometimes manual lock/unlock can help the network routing.
