Keep an older 32-bit Raspberry Pi running a current version of Home Assistant after official 32-bit support ended.
Build a smaller, faster Home Assistant image by including only the integrations you actually use.
Test a Home Assistant backup restore on a Mac or PC before deploying the new image to the actual Pi.
Fall back to the last official 32-bit Home Assistant image if a full custom build is not needed.
| adyoull/ha-armv7 | ateska/rk1-llama-server | nodejs/wasm-builder | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Dockerfile | Dockerfile | Dockerfile |
| Last pushed | — | — | 2026-03-17 |
| Maintenance | — | — | Maintained |
| Setup difficulty | hard | hard | moderate |
| Complexity | 4/5 | 5/5 | 3/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Needs Docker Desktop with at least 8 GB RAM and 40 GB disk, since several components compile from source under emulation over several hours.
HA-ARMv7 is a build kit that lets someone run a current version of Home Assistant, the home automation software, on older 32-bit devices like a Raspberry Pi 2 or 3. Home Assistant's own project stopped officially supporting these 32-bit devices in 2025, with the last official image being version 2025.11.3, so this project cross-compiles a newer version specifically for that older hardware using Docker, working from a Mac or any other 64-bit computer. Using it is meant to be simple on the surface: a single build script can either fetch the latest Home Assistant source and compile it for the older chip, build a specific version, or just download the last official 32-bit image as a fallback if someone does not want to build anything. There is also a more advanced option to include only the specific integrations a person actually uses, which produces a smaller, faster image with fewer moving parts. Building it is a heavy process. Several pieces of software, including FFmpeg, have to be compiled entirely from source because the older chip needs code built specifically for it, and this can take several hours and needs a computer with plenty of memory and disk space set aside for Docker. The project documents a long list of specific technical problems it ran into along the way, such as renamed system libraries, mismatched versions of FFmpeg, and libraries that need to be relinked with the correct compiler, and explains exactly how each one was worked around. The README recommends testing the finished build on the original computer first, by running it in Docker and confirming that an existing backup restores correctly, before copying the image over to the actual Raspberry Pi. It also gives a list of practical gotchas: a missing SSL certificate can bring down several unrelated features at once, one integration no longer supports its older configuration method, and the first startup after restoring a backup can be slow while extra components finish compiling on the Pi itself. The author is upfront that this is an unsupported, unofficial project that Home Assistant will not take issue reports for, describing it as a way to buy time on older hardware rather than a permanent solution. The README does not mention a software license.
HA-ARMv7 is a Docker build kit that compiles a current version of Home Assistant to run on older 32-bit devices like a Raspberry Pi 2 or 3.
Mainly Dockerfile. The stack also includes Dockerfile, Docker Buildx, Home Assistant.
No license is stated in the README, so usage rights are unclear.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.