I also see this behavior, but since the lock actually does the command issued, I usually don’t care.
I chalk it up to zwave stack latency and hope the new integration makes things far more faster.
I also see this behavior, but since the lock actually does the command issued, I usually don’t care.
I chalk it up to zwave stack latency and hope the new integration makes things far more faster.