Looks like this issue has appeared prior to 4.4.2.
Currently there is not a workaround for the issue. It has been reported to Qolsys and may be resolved in an upcoming FW
Looks like this issue has appeared prior to 4.4.2.
Currently there is not a workaround for the issue. It has been reported to Qolsys and may be resolved in an upcoming FW