August Smart lock pro 3rd gen zwave and IQ4 panel

So this lock is officially on the approved list. But doesn’t work.

It comes up with S2 access and S0 options both checked during enroll. Once enrolled, the panel displays the lock screen, but no status on the battery, and some error message when you try to operate it. Lock does not move.
So, let’s iterate:
S2 access only: same error. lock doesn’t move. (S2 i guess is the encrypted mode)
S0 only: battery level DOES work. Panel lock screen changes locked/unlocked. But actual lock does not move. Hand operating the lock does not create change of status at the panel either.

So, it does enroll, but it’s useless.

It doesn’t look like you have activated your Alarm.com account yet so I cannot view any diagnostics or troubleshoot from our end.

A quick thing that trips up a lot of installs: when pairing, the lock must be within about 6 feet of the panel.

Move the lock to the panel or the panel to the lock, either is fine, but within 6 feet is necessary to be sure pairing can be 100% successful. This is the case for all Z-wave locks.

If it is not within that proximity the device may be found and added, may appear successful, but full secure enrollment fails and many functions can be affected.

Can you confirm that it is being paired in close proximity to the panel?

No, zwave is supposed to be enrolled where they live.
But, ok, I’ll try it basically touching the IQ4 panel.

These are the results (same for S2access mode, but S0 unsecured does now work after being enrolled closely)

S2access & S0


then the device properties show NOTHING


Going to JUST S2access mode during enroll gives pretty much the same thing. same error screen as before, with these properties (lock still does not operate):

Then there is the S0 option. Here’s the stuff:







So that appears to actually load stuff up, and it actually now operates the lock at it’s install location.
But it is in unencrypted mode.
So not fully supported. And the error screen even said that. I did add the DSK key each time when it was enrolling in S2access and S2access+S0 modes, without issue.
So I think it is a panel software problem.

Thank you for the testing and follow up. I will send this info to Qolsys so they can test and confirm compatibility.

No, zwave is supposed to be enrolled where they live.

Only devices supporting NWI can do this, only when enough NWI repeating devices are between it and the panel, and in general, locks are not included in this category.

Lock and thermostat transmissions require a lot of data transmission up front, and lock range is generally very poor compared to all other devices.

The instruction for adding Z-wave locks to panels has always been to add within 6 feet. You can disregard this if you do not wish to do it, but it is exceedingly likely to cause failures.

Btw, just to be 100% sure, what is the exact model number for that lock?

The one listed as compatible in their current guide is the AUG-SL-CON-S03

I did enroll it at 2" away.
Here’s the box info. Just ordered it from August this month. It’s a combo set of lock and wifi hub, so the p/n may not be exactly the same. It is the last version they made with integrated zwave.
PXL_20211228_183911664

Thank you, it is possible that this is simply a newer version of the lock which is not compatible. Qolsys specifically calls out the model number AUG-SL-CON-S03

You can use with S0 for now if that works, I have sent this info to Qolsys for review. Hopefully they can confirm quick what the issue is.

It looks like this model is in fact different and not compatible with the panel. In addition, as the manufacturer has discontinued support for Z-wave models, I have found a compatibility notice that Alarm.com has ended support for new August Smart lock installations as of June 21, 2021.

Hmmm, well great.

Although, I do think it is the same model. Decoding their part number,
AUG=August of course
SL= smart lock
CON= connect, their optional wifi plugin module
S03= this is the actual lock. S is for silver, G is for gray, and 03 is for the 3rd generation lock, which is the last generation, which is the last one with zwave.

So while they no longer make the lock, I see no reason why Qolsys should not support existing (legacy - if you can call May 2020 legacy) products that they say are/were compatible. I would not expect “new features” whatever that would mean with a zwave lock, but Qolsys’s base code should continue to function with “compatible” products.

Well, I guess that saves me $3/mo in subscription fees…