No, I have not (nor will) tie an unlock event to disarming the system. But I don’t see why it wouldn’t work. ADC has no issues in the past several months now that my Kwikset has been added to the primary ST with GC2 secondary. And ADC indeed has a “Security System” event rule to Disarm from User Code. But locks cannot send WHICH user code was entered so ANY legit code would disarm your system and regardless of any code schedule rules - hence that very warning that ADC tells you there in the rule and why I absolutely would never do that
Now, as for GC2 sensors and ST - Read these earlier threads carefully:
- The ST itself cannot control Arm/Disarm state of the GC2 - if you were hoping for much more complex alarm rules/conditions that ST affords or were hoping to ditch ADC’s emPower subscription upgrade, you can’t if you want rules around alarm actions around Z-wave devices like this
- The GC2 “sensors” like window contacts, motion, image, and anything else not Z-wave are proprietary to 2gig alarming and cannot (directly) change any complex state or invoke actions/rules on the ST hub. There are tricks to ST polling a certain Z-wave device’s state to take action, but still deemed too unreliable for an actual alarm call to dispatch
Basically ST and GC2 cannot control much of each other (and understandable that 2gig does NOT want 3rd-party devices that could make them liable for a missed alarm condition). No, basically all of this is so that you can leverage the power and customization of ST on the same Z-wave devices throughout your house that you’ll also need ADC to simultaneously control.