Shelly 3.4 Adds Firmware Updates to the Arch Linux Graphical Package Manager
Shelly, the graphical package manager for Arch Linux and Arch-based distributions, has reached version 3.4. The headline feature is an optional Firmware page that updates UEFI/BIOS and peripheral firmware through fwupd and the Linux Vendor Firmware Service, without leaving the app. Here is how it works, what safeguards it adds and what else changed.

fwupd on demand and adds safety prompts, including a recovery-key acknowledgement for disks protected by full-disk encryption. The release also brings customizable package table columns, Pearl theme fixes in light and dark modes, redesigned Settings and Flatpak pages, and a fix for building split packages from the AUR.What Is Shelly?
Shelly is a graphical package manager for Arch Linux and Arch-based distributions. It sits on top of the usual package tooling and adds a desktop interface for installing, updating and removing software, including Flatpak applications and packages from the Arch User Repository (AUR). Version 3.4 arrived only hours after Shelly 3.3.1, which improved AppImage updates.
The New Firmware Page
The main addition in 3.4 is an optional Firmware page for managing firmware on supported hardware, including UEFI/BIOS and peripheral devices, directly from Shelly’s interface. It uses the Linux Vendor Firmware Service (LVFS) as the source of firmware releases and supports three actions: updates, downgrades and reinstalls.
Enable it on the initial welcome screen, or later in Settings.
If fwupd is not installed, Shelly installs it when needed.
The fwupd daemon uses D-Bus activation, so you do not enable a separate system service manually.
The page lists supported devices and puts those with available updates first. Selecting a device shows its current and latest firmware versions, vendor and the available releases.
Safety Checks Before Flashing
Firmware flashing is riskier than a normal package update, so Shelly adds several safeguards:
- Explicit confirmation. A dialog names the device and firmware version, shows the download size and estimated installation time, and warns that the device may become temporarily unavailable.
- Recovery key acknowledgement. For devices protected by full-disk encryption, you must confirm you have your recovery keys before the update proceeds.
- Checksum-verified downloads. Firmware downloads are verified before installation.
- Live progress. Installation progress is shown in real time.
- Restart choice. If an update needs a reboot, you can restart immediately or later.
The integration also monitors connected devices and battery conditions, handles interruptions in the fwupd daemon, and offers a manual option to refresh firmware metadata.
Interface Improvements
| Area | Change in Shelly 3.4 |
|---|---|
| Package tables | Columns can be shown, hidden or reordered by dragging. Preferences are saved per table and restored when the app restarts |
| Pearl theme | Fixes in light and dark modes for rounded list backgrounds, table headers, button borders and spacing inconsistencies |
| Settings and Flatpak pages | Redesigned |
| Toolbars and other elements | Refined for a more consistent look |
AUR Split-Package Fix
Shelly 3.4 also fixes a bug in building split packages from the AUR. A split package is one build that produces several installable packages. Previously, installing just one package from such a set could fail because later package() functions ran from an incorrect working directory.
Shelly now builds the complete split-package set in a single pass, the way makepkg does, but installs only the packages you asked for.
Using Firmware Updates Safely
The list below is my own general advice, not part of the release notes:
- Back up first. Back up important data before flashing UEFI/BIOS or storage-related firmware.
- Use reliable power. On a laptop, plug in the charger and keep the battery charged. On a desktop, avoid updating during unstable power.
- Know your recovery key. If the disk is encrypted, locate the recovery key before you start.
- Update one device at a time, and read the release details Shelly shows before you confirm.
- Do not interrupt the process, and restart only when the update asks for it.
If you prefer the command line, fwupd also ships its own tool. These are standard fwupd commands, shown here as an alternative to the graphical page:
sudo pacman -S fwupd
fwupdmgr refresh
fwupdmgr get-updates
fwupdmgr update
For more Linux guides, see VMoreCloud .
Frequently Asked Questions
What is new in Shelly 3.4?
An optional Firmware page powered by fwupd and LVFS, customizable package table columns, Pearl theme fixes, redesigned Settings and Flatpak pages and a fix for AUR split-package builds.
Is the firmware feature enabled by default?
No. You can enable it during the initial welcome screen or later in Settings.
Do I need to install fwupd first?
No. If fwupd is not installed, Shelly installs it when needed. The daemon uses D-Bus activation, so no separate service needs to be enabled by hand.
Can Shelly downgrade firmware?
Yes. The Firmware page supports updates, downgrades and reinstalls.
Why does Shelly ask about my recovery key?
For devices protected by full-disk encryption, Shelly requires you to acknowledge that you have your recovery keys before the update proceeds.
Where can I read the full changelog?
On the project’s GitHub release page for v3.4.0, linked in the sources below.
Sources and Further Reading
- Shelly v3.4.0 release notes (GitHub)
- Linuxiac: Shelly 3.4 Arch Linux Package Manager Adds Firmware Update Support
- Linuxiac: Shelly 3.3.1 Arch Linux Package Manager Improves AppImage Updates
Details in this article are based on Linuxiac’s coverage of the Shelly 3.4 release. Confirm behavior in the official changelog before using firmware updates on important systems.
