Thank you, @soxfan82 ~ I haven’t logged in for quite a while and didn’t expect this thread to get so much attention. I also just realized you sent me a DM, I’m really sorry for not getting back to you sooner. Thank you so much for your contributions to this topic!
I applied your suggestion (using pkg install udocker instead of ./install_udocker.sh) and it’s awesome! It runs perfectly on my Galaxy Tab S6 Lite (Android 13). I haven’t run into other problems you experienced yet.
Also, I just updated matter-server.sh to migrate to the official stable Matter.js Server image, as I heard the Python Matter server is no longer supported.
I updated the Home Assistant Core system on my Vernee M5 phone to the latest release, version 2026.7.2.
It has been running without any issues for about a year now, as far as I can see.
Therefore, it is very well suited for testing and also for getting familiar with Home Assistant.
In the process, it became clear why the Vernee M5 was the most suitable device for this task.
The processor in this phone is 64-bit, and Home Assistant no longer provides updates for 32-bit systems.
Because of this, 32-bit systems can only use the following version with the method mentioned above:
My Samsung phone presents an interesting situation regarding why it didn’t work (although it works now too, with a modification).
The v8l architecture is a kind of hybrid 32-bit and 64-bit setup. If I force the 32-bit version during installation/download, the container starts successfully (armv7).
However, the script is looking for the v8l architecture, which is not available on Dockerhub.
~/HomeAssistant-Termux $ cat home-assistant-core-vernee.sh
#!/data/data/com.termux/files/usr/bin/bash
source "$(dirname "${BASH_SOURCE[0]}")/source_vernee.env"
# The script will find and download the image from Docker Hub, not from GitHub Container Registry
# Example for pinning (only on 64bit systems now):
#IMAGE_NAME="homeassistant/home-assistant:2025.12.2"
# Example for the last 32bit version:
#IMAGE_NAME="homeassistant/home-assistant:2025.11.3"
# Fresh version:
IMAGE_NAME="homeassistant/home-assistant"
CONTAINER_NAME="home-assistant-core"
# Set timezone, eg, Asia/Seoul. Feel free to change.
TZ="Europe/Budapest"
Once you have opened a Termux terminal, follow the steps below.
If you make a mistake in the last step, there is no big problem, because you can create the link yourself; just check what it should point to.
As you can see from the list, the previous HA CORE is still installed as well. The HuyTungst script mentioned in the opening post always pulls down the latest container. If the symbolic link mentioned above exists, it does not download a new one.
This makes updating CORE extremely simple.
If you are afraid of the new version and want to make sure that you can revert to the older version, that requires a few more steps.
If you are not afraid of the new version and simply want to move forward, then these steps are suitable for you:
Welcome to Termux!
Docs: https://termux.dev/docs
Donate: https://termux.dev/donate
Community: https://termux.dev/community
Working with packages:
- Search: pkg search <query>
- Install: pkg install <package>
- Upgrade: pkg upgrade
Subscribing to additional repositories:
- Root: pkg install root-repo
- X11: pkg install x11-repo
For fixing any repository issues,
try 'termux-change-repo' command.
Report issues at https://termux.dev/issues
~ $ cd .udocker/
~/.udocker $ ls -las
total 40
4 drwx------. 8 u0_a70 u0_a70 4096 Dec 10 2025 .
4 drwx------. 12 u0_a70 u0_a70 4096 Aug 25 17:12 ..
4 drwx------. 2 u0_a70 u0_a70 4096 Dec 10 2025 bin
4 drwx------. 4 u0_a70 u0_a70 4096 Jul 13 09:40 containers
4 drwx------. 2 u0_a70 u0_a70 4096 Dec 10 2025 doc
4 drwx------. 2 u0_a70 u0_a70 4096 Jul 13 09:35 layers
8 drwx------. 2 u0_a70 u0_a70 8192 Dec 10 2025 lib
4 drwx------. 4 u0_a70 u0_a70 4096 Dec 10 2025 repos
4 -rw-------. 1 u0_a70 u0_a70 119 Aug 21 15:41 udocker.conf
~/.udocker $ cd containers/
~/.udocker/containers $ ls -las
total 16
4 drwx------. 4 u0_a70 u0_a70 4096 Jul 13 09:40 .
4 drwx------. 8 u0_a70 u0_a70 4096 Dec 10 2025 ..
4 drwx------. 4 u0_a70 u0_a70 4096 Dec 10 2025 09fd677d-7951-3c39-a35b-409fb423a927
4 drwx------. 4 u0_a70 u0_a70 4096 Jul 13 09:40 0f894d98-05ed-3b59-9a8a-a8854dd21582
0 lrwxrwxrwx. 1 u0_a70 u0_a70 36 Jul 13 09:40 home-assistant-core -> 0f894d98-05ed-3b59-9a8a-a8854dd21582
~/.udocker/containers $ rm ./home-assistant-core
And start HomeAssistant:
~/.udocker/containers $ cd
~ $ cd HomeAssistant-Termux/
~/HomeAssistant-Termux $ bash ./home-assistant-core.sh
The phone is 64-bit, so the CORE installation works without any problems using this method. Official Home Assistant containers are no longer built for 32-bit systems, so HuyTungst’s script already gets stuck when downloading the container. The script cannot find a version that is compatible with the system.
The unofficial solution linked at the end of my previous post may help if your phone does have a 32-bit Android system.
~/HomeAssistant-Termux $ uname -a
Linux localhost 3.18.35 #1 SMP PREEMPT Mon Sep 25 19:39:03 CST 2017 aarch64 Android
