Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the accelerated-mobile-pages domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-includes\functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-sitemap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-includes\functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-sitemap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-includes\functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-includes\functions.php on line 6121

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 14

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 19

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 24

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 29

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 34

Deprecated: Return type of GuzzleHttp\Ring\Future\CompletedFutureArray::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\CompletedFutureArray.php on line 39

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 11

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 16

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 21

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 26

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 31

Deprecated: Return type of GuzzleHttp\Ring\Future\FutureArray::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in C:\inetpub\wwwroot\Staging.GuardianProtection.com\wp-content\plugins\swiftype-search\vendor\guzzlehttp\ringphp\src\Future\FutureArray.php on line 36
Clear Your Panel's Red Notification Badge | Guardian Protection

Return to Support

How to Clear the Red Notification Badge Over the Guardian Logo on Your Panel

To clear your system of alerts or trouble notifications, follow these steps:

1. Tap the Guardian Protection logo in the top right corner.

2. Tap ALERTS/ALARMS.

3. Scroll through the messages to review the history of the system. If you see problems listed in your history that haven’t been fixed, please follow the instructions in your panel manual (you can find it by logging into your Guardian account.)

4. Tap Acknowledge All.

5. Tap “OK” on the message that states “Acknowledging the selected messages will delete them from your message center. Are you sure you want to proceed?”

6. The alerts will clear. If the device has not been fixed, the red notification badge will reappear in the top right in a few hours.

Still having trouble? Just give us a call at 1.800.PROTECT (1.800.776.8328).