This is one of a couple different issues I began experiencing immediately upon updating firmware to 2.7.0, as detailed in this this thread.
Jason had previously noted that there have been a few other reports of these, though not all tied to 2.7.0. I understand that we’re waiting on comments from Qolsys on these. By any chance, have you recently performed a firmware upgrade to 2.7.0…?