Add MD5 Check for Pre-Downloaded RAUCB Files to Skip Full Re-Download During Supervisor Updates

[shisaru292]

Describe the feature

Currently, when Home Assistant Supervisor performs an update, it always needs to download the full RAUCB file directly. In some environments, network conditions make this process slow or unreliable. Users may prefer to manually download the RAUCB file using tools such as curl -x with a proxy for acceleration.

I propose adding an MD5 (or similar checksum) verification function in the update process. If a valid RAUCB file already exists locally and passes the checksum verification, the Supervisor can skip the full re-download and proceed directly with the installation process.

This feature would save time, reduce redundant network usage, and improve update reliability in constrained or proxied environments.

Use cases

• Slow or unstable networks: Users with limited bandwidth or unstable connections can pre-download the RAUCB file once and reuse it instead of retrying multiple failed downloads.
• Proxy-based acceleration: Users who want to use curl -x or other proxy tools to speed up downloading can place the file locally and let Supervisor verify it.

Current workarounds

No response

Anything else?

No response

[shisaru292]

I originally suggested adding an MD5 check for pre-downloaded RAUCb files so the supervisor could skip a full re-download during updates. After looking into it further, I found a straightforward alternative: simply follow the manual update procedure described here: Using Update Bundles. This way the update can be fully applied with a manually downloaded RAUCb file.

And my setup is HAOS on Raspberry Pi 5

---

run in the HAOS shell：

# cd /mnt/data/
# curl -L -O https://github.com/home-assistant/operating-system/releases/download/11.5.rc3/haos_rpi5-64-11.5.rc3.raucb
# rauc install haos_rpi5-64-11.5.rc3.raucb
# systemctl reboot