This is the issue at hand I suspect.
Zwave devices are third party, and always a pain regarding compatibility (its not ADC or 2GIG hardware).
Your locks are brand new (manufactured June 2014, to the zwave 3.2 version most likely). Manufactures usually release zwave gear to the current version (some do not, and some manufactures do not adhere to the zwave specs at all, and some are backwards compatible for all zwave versions).
Schlage is one of those. They like to make their locks work with their own interface (Nexia). So what happens is ADC/2GIG have to play catch up with every new hardware release (especially Schlage), and that usually happens with new firmware releases. 2GIG currently uses zwave 2.78 version.
I suspect your zwave devices/locks will require a firmware update.
I love Schlage, but I don’t use the zwave locks at all. If you are gonna go with Schlage it is best to go with “supported” ones. That means those manufactured in 2012/2013 or earlier. They must support zwave version 2.78, and/or have support for the locks added to the panel.
In your case, the ADC empower/zwave commands work, but locally the panel can’t properly communicate when lock is engaged, or disengaged insofar as arming/disarming goes.
Thus…firmware update is required to resolve the compatibility issue(s).
And if you are wondering why 2GIG hasn’t updated the supported zwave firmware from 2.78 to 3.2. I haven’t a clue…
The solution is simple…
Wait for a firmware update for your locks, (and have SuretyCAM send 2GIG a support ticket regarding the new Schlage zwave locks), or return them and get compatible/supported Schlage locks (like the Camelot).
Dont count on 2GIG adding the Schlage support for the locks till 2015 though.