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
All About Smart Door Lock Batteries | Guardian Protection

Return to Support

All About Smart Door Lock Batteries

Battery Replacement | Equipment

Wondering how to keep your smart door lock powered and reliable? This guide covers everything you need to know about smart lock batteries, from lifespan to replacement tips.

Why isn’t my door lock’s battery state updating?

If you’ve changed the batteries for your smart door lock and the battery status isn’t updating, there could be a few different reasons:

First, verify you’re using the recommended batteries. Guardian recommends name brand such as Energizer, Duracell, or Panasonic alkaline batteries.
Ensure the batteries have not reached their expiration date.
Lock and unlock your door manually. This will force an update to the system and our interactive services.

If the above steps are not resolving your issue, please contact us at 1.800.PROTECT (1.800.776.8328).

Why do my smart lock batteries drain so quickly?

If your door lock’s batteries drain too quickly, there could be a few different reasons:

First, verify you’re using the recommended batteries. Guardian recommends name brand such as Energizer, Duracell, or Panasonic alkaline batteries.
Ensure the batteries have not reached their expiration date.
The door lock motor may be overworked. To verify:

1. Open the door and lock the door lock. The dead bolt should fully extend with little resistance. Unlock the mechanism and close the door tightly.

2. Lock the door again. Check to ensure the lock mechanism is in the same orientation as earlier. You should not have resistance when locking the door here. If you encounter resistance, the door lock motor is being overworked and causing the batteries to drain faster. Contact us at 1.800.PROTECT (1.800.776.8328) to schedule a technician to assist with adjusting your lock.

What is the battery life of a smart door lock?

Several factors play into how long your batteries will last, including environment, temperature, and weather stripping. Typically, battery life ranges from 6 months to 1 year.

How do I change the batteries in my smart door lock?

To change the batteries in your smart door lock, check out this quick instructional video.