> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/intercom/configuration/schedule-intercom-firmware-upgrades.md).

# Schedule Intercom Firmware Upgrades

Configure when your intercoms will perform firmware upgrades

Verkada releases regular intercom firmware updates. These updates enhance security and functionality and are included at no additional cost as part of your cloud license.

Firmware updates are pushed automatically. However, you can schedule firmware updates to happen during a configured window.

***

## Schedule firmware updates

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select your intercom.**
{% endstep %}

{% step %}
**At the top, select Settings.**
{% endstep %}

{% step %}
**Under Device, toggle on​ Schedule Firmware Upgrades.**

a. Choose a time when updates should occur\
b. The window must be at least **2 hours long**\
c. Intercoms may **reboot** during this time
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
The update window needs to be a minimum of 2 hours. Intercoms may reboot during this time.
{% endhint %}

***

### What happens during a firmware update?

#### Automatic Failover for Reliability

Verkada intercoms use a dual-partition firmware bank, ensuring updates are reliable and resilient. If an update fails, the intercom automatically rolls back to the previous version and retries the update at a later time.

#### Does the intercom stop recording during updates?

Verkada intercoms are designed for failsafe updates that minimize service interruptions. While the device may briefly go offline during the final stage of the update, this typically occurs during your scheduled maintenance window to reduce disruption.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/intercom/configuration/schedule-intercom-firmware-upgrades.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.