Input masking behavior on Mercury alarm panels

This information applies to alarm input masking based on a schedule (i.e. timezone). After downloading the database, the configuration works as expected. The input is masked as long as the download completed while the timezone is active. However, if you later modify the alarm input, it will lose the masking configuration if the modification occurred while the timezone was active. An Input Unmasked alarm will occur and the input is no longer masked.

This behavior is by design.

If this becomes an issue, there are a few ways to work around this:

1. Perform a database download.
2. Create a local I/O for Activate/Deactivate Timezone will  for the timezone used to mask the Input. You can then select this local I/O from Alarm Monitoring and execute it to begin masking the timezone.