# Sonoff iHost + Home Assistant

**URL:** <https://forum.ewelink.cc/t/sonoff-ihost-home-assistant/206859>\
**Category:** eWeLink CUBE\
**Created:** [December 9, 2025, 9:14pm UTC](https://forum.ewelink.cc/t/sonoff-ihost-home-assistant/206859 "2025-12-09T21:14:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![el404](https://avatars.discourse-cdn.com/v4/letter/e/898d66/32.png) [@el404](https://forum.ewelink.cc/u/el404)\
**Post date:** [December 9, 2025, 9:14pm UTC](https://forum.ewelink.cc/t/sonoff-ihost-home-assistant/206859/1 "2025-12-09T21:14:39Z")

</div>

Dear Sonoff iHost owners, this information is for Home Assistant users in Docker.

Nabu Casa, the developer of Home Assistant, has discontinued support for 32-bit processors and removed the repository for them!

Therefore, if you try to restore a backup of your iHost (note: the iHost backup does not contain the entire Docker container, only its configuration), the iHost will not find this container during restoration and will suggest skipping the step. To avoid a situation where you lose all your data, you need to migrate to a “new” Docker container.

The solution: I have created my own repository with the last working version of Home Assistant - 2025.11.3.  
You can find it on Docker Hub: el404/homeassistant-for-ihost  
As well as the last working version of filebrowser: el404/filebrowser-for-ihost

* * *

**Migration instructions:**

1. Manually create a backup of Home Assistant and download it to your computer.
2. Stop the current Home Assistant Docker container!
3. Create a new volume, for example: `HomeAssistant2`
4. Pull the image: `el404/homeassistant-for-ihost`
5. Launch the container with the following settings: Network - `host` , Volume - `HomeAssistant2` mounted to `/config` .  
 ![11111](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/7/7318d5fd690481cf614a19daab1357fe8520cc4a.png)
6. Start the new Home Assistant (access it at ihost.local:8123) and restore it from your backup.
