August Pro Z-Wave issue

There's something wrong with the lock (probably the firmware), if you have access to it via its mobile app I would contact their support and request that the firmware be downgraded, multiple users have had issues with the latest firmware version.

3 Likes

Is this still current?

I'm a brand new HE7 owner and trying to set up my first device. Anyone have any experience downgrading the firmware on their locks - what did you ask them to downgrade to?

I am running the most recent firmware on my locks and have had very little problems with the latest 2.2.3 hub firmware on the C7.

Several people have reported problems getting them included, but I didn't have any difficulty.
Here is a recent message I sent on a related thread with my notes from the zwave inclusion process:

Thanks for your message! I was encouraged to hear that it worked smoothly for you. I had a lot of difficulty getting paired, but it ultimately did work for me.

I was able to pair by unchecking the S0 box. I think that I originally tried this and it did not work, but it is working now! I did not get any errors from either the August app or the C7 dashboard by pairing this way, nor did I see any big lags.

One other item of note: The august app said that the locks needed a firmware update before using Z-wave, but as best as I can tell this update never installed.

My 3rd gen. August Pro looses its connection and is unable to be controlled from Hubitat. After using the August app to lock/unlock the device I can control it via Hubitat again.

Should I switch to the ‘Generic Z-Wave Lock’ driver or try something else?

If you have the connect, I would strongly consider using the wifi integration which has better stability compared to the z-wave in my experience:
[[Release] Alpha version of August Home (wifi door lock)]

I have/had the same problem. The August Pro is the only device I have issues with (after 2.2.4), which includes 36 Z-wave devices of various manufacturers. I could get the lock to pair, and work well for short periods of time, then things would go crazy with severe battery drain and unresponsiveness. I didn't have issues with my Smartthings, which I migrated from.

I didn't want to purchase the wifi bridge from August, so I dusted off my Smartthings, paired it to the August lock, and then installed Hubconnect. So now, I control the August lock from Hubitat, which communicates to Smartthings, which then communicates with the lock. Very kludgy, but it works and is reliable without battery drain. This experience makes me think there is still an issue with the Hubitat driver for the Pro. I didn't have any luck with the Generic Z-Wave lock either.

The ‘Generic Z-Wave Lock’ driver doesn't work any better.

Appreciate the workaround suggestions but I'd prefer to get this working as it should.

Manually changing the lock's state appears to 'reconnect' it with HE which can then, for the time being, control the lock.

Should I turn on 'Hub Mesh enabled'? I don't know what this does.

Although I have both 'debug logging' and 'descriptive Text logging' enabled,

when I click 'Lock' on the device page, no logs are generated.

@mike.maxwell Does the absence of HE logs indicate there is an issue with the driver?

The opposite actually, if there are no logs when executing commands from the driver or when activating the device physically then it's an issue with the device and or mesh...

@Busthead What firmware version is your lock on? I had the same issues and after a lot of back and forth with August, they downgraded my firmware to 1.59.0-1.8.15. That was a year and a half ago and my lock has functioned perfectly since (even moving it from a C3 to a C7 paired with S2 security).

1.59.0-2.0.1

I've submitted a request to August to downgrade my firmware to 1.59.0-1.8.15 or upgrade to a beta version if there is a fix for this known issue. Will report back.

2 Likes

Strangeness.

I requested a firmware downgrade (or upgrade to beta firmware that addresses the Z-Wave connectivity issue) and August told me they no longer have that ability.

I requested escalation to the next tier of support. They also stated that they are no longer able to downgrade firmware.

Then my lock started working...

I didn't change any settings or add any new devices; it just started working out-of-the-blue.

I verified via the August iOS app that the lock's firmware had not changed.

1 Like

Weird but positive outcome. I hope it continues to work for you!

My 2 August Pro locks are doing the same things as others. After a period of time they will go offline and only work from Hubitat over zwave if they are manually moved or triggered from the August app. After they start working for a short time. I opened a support ticket with August and after a few days of back and forth they acknowledged the issue and that the older firmware would fix it, but they refused to downgrade the lock because of a security issue. After some more back and forth they told me that because the lock works from the August app that I need to work with Hubitat to fix the issue. That or move to SmartThings and do cloud to cloud. They stopped replying after I called out that they are knowingly selling this lock as zwave compatible and know there are issues with it but refuse to fix it.

What are the chances this can even be fixed by Hubitat? All my other zwave devices are working great. I am still within my 30 day return window. Should I just send them back? I bought these because I am in an apartment and cannot change the locks so this was an easy workaround.

I've been having similar issues with my August Pro as well. It worked great for the first few months but after a firmware upgrade it was all downhill. It would work via Z-wave only intermittently, typically after using the August app or manually controlling the lock, but then it would stop responding to Z-wave commands after a few hours. Battery life deteriorated as well, and it's behavior got worse as the batteries drained. I tried factory resetting and now I wish I hadn't. I can't get hubitat to see anything but the keyWe lock, and functionality is zero. I've tried the excluding, resetting, including cycle several times, using two devices, one for August app and one for hubitat, and the results are always the same. I've been going back and forth with August for the last few days trying to roll back my firmware with no luck, they don't want to budge on that now, despite doing it for others.

I was a longtime August Pro user and I love the lock when it worked. However, between the Z-Wave issues, the mechanical defects and, the straw that broke the camel's back, randomly showing that the lock was in an unlock position but physically hadn't moved from the lock position. The only way to correct that was to remove the battery and put the battery back into the lock. I've had my lock replaced three separate occasions and never had long-term Success With It. The best advice would be used St the handle the August lock (WiFi Integration) and then use Hub connect to control it.

I have switched over to the Alfred lock recently, and so far it's been great. Z-Wave works perfectly and Wi-Fi and Bluetooth are seamless.

how do you connect smart things and Habitat? with regards to the lock?

I used [RELEASE] HubConnect - Share Devices across Multiple Hubs (even SmartThings!) - Developers / Code Share - Hubitat
I have a special drive for the august lock. @Csteele was very helpful get this to work for me.

2 Likes

@jsarcone could you help me out with the custom driver for august lock? pretty please :slight_smile: :slight_smile:

Hi @k2rm , so your August lock is connected to your ST hub via z-wave? And there is no battery drain? But there is battery drain if connected z-wave to hubitat?