The Defend-O-Tron supports two separate firmware update paths, each for a different situation:
The Defend-O-Tron also receives routine Debian package updates on the Software updates page. Those keep the underlying operating system patched and are separate from firmware updates. Both are safe to use, alongside each other. When the firmware changes, the Debian updates installed since the last firmware are replaced by the new firmware’s own packages.
Sign in to the web interface and open Firmware under Device in the menu. When the last check found an update, a small arrow icon shows beside Firmware in the menu.
Everyone who can open the page sees the device’s firmware status. Checking for updates, downloading firmware and switching between versions need a role with full firmware access, such as Admin.
The This device card shows what the Defend-O-Tron is running and what it found the last time it checked:
Click Check for updates to ask the firmware server now instead of waiting for the weekly check.

Beside it, the Stage a version card lists the versions on the firmware server, with the newest marked latest. Pick a version to read its release notes. When a version can’t be staged, a short note under the list says why, for example because it is already running or already installed.

On Stage a version, choose the version and click Stage. The version the last check offered is already chosen for you.
When staging finishes, a blue banner says the firmware is staged and a Staged card appears. The new firmware is on the device, but your current firmware is still running. Clean up old firmware files on the next boot comes ticked, and leaving it ticked is recommended.

Click Apply, then Apply again to confirm. A green banner confirms it, Boots next now shows the new version, and the orange line reminds you that a restart is needed.

Restart the Defend-O-Tron at a quiet time, with Restart on the Overview page. Internet traffic through the device stops while it restarts, usually for a few minutes. The page shows that the device is restarting and takes you to the sign-in page when it is back. See the admin interface page.
Sign in and open Firmware again. Running now shows the new version.
The previous firmware stays on the device after you apply a new one. If anything goes wrong, you can switch back to it. See Rolling back firmware below.
Some updates must also change settings that are already on your device, for example to replace an old settings file. These changes are upgrade steps.
If a step fails, the device still starts. What you see depends on how important the step is:
Each step is also in the logs (the service awesome-o-upgrade) and in the audit evidence (the Admin actions tab, Via: The device (upgrade)).

The page shows a banner across the top whenever something important happens:
The Installed images table lists every firmware on the device: the factory image and each version you’ve downloaded, with its kernel, when it was installed, and its status. Default marks the one that boots next, running the one running now, and staged one that is waiting to be applied.
Each one asks you to confirm first. Switching firmware takes effect at the next restart.

Firmware rollback is intended for problems you discover after an update, for example a setting that didn’t carry over cleanly. It’s not a substitute for cabling the device out of your network if you suspect a serious issue.
The Defend-O-Tron asks the firmware server for news once a week, between 3 and 4 AM on Sunday in the device’s time zone. If it was switched off then, it checks soon after it next starts. The check only looks: it never downloads or installs firmware on its own. That always waits for you.
When a check finds an update, the arrow appears beside Firmware in the menu and the version shows under Offered on the page.
If the device cannot be fixed from the web interface, for example it no longer starts, you can run a V100 from an SD card, or reinstall a V200 from a USB installer. See Recovery and Reinstall.