Installation running perfect !

[audministrator]

Hi, just to let you know the HA core runs without issues.
Installed the F-Droid Termux & and termux API.on a Samsung Tab A8 running Android 14 👍.

Next ran the installation script to install HA Core.

Next installed the Marstek integration, and configured a dashboard.

I had to download the integration manually since I could not install HACS in this HA version 😒

Does any one know where and how to get this running on the version of HA Core ?

Ps:
I the same installation on an other tablet running Android 13.
All went fine as well.

Thanks a lot for this valuables installation script !

[audministrator]

Solution for HACS integration:
DO NOT install any manual integration BEFORE installing HACS integration. If so delete all /custom_components !!

Next shut down HA Core.
Login Ubuntu & go to folder the HA home directory:
cd /data/data/com.termux/files/home/hass-config

Next Install HACS see here:
https://www.hacs.xyz/docs/use/download/download/

Run => wget -O - https://get.hacs.xyz/ | bash -

Next restart HA and add the HACS in the Gui using integrations. Next follow these instructions:
https://www.hacs.xyz/docs/use/configuration/basic/

Enjoy !

[pcosway]

What version did it install? I tried this and got 2026.2.3. I don't know if this process will install up-to-date versions. I saw a message indicating the installation method has been deprecated and is no longer supported.

[audministrator]

I got the same version running.
Also read that support stopped in 2025. But eventually all seems to work perfectly 👌

The is a more recent version available as well. Not sure if the current version can be upgraded ?

If some can give the upgrade process a try that would be great 👍

[audministrator]

I made a full series on how to setup Termux on Android and this perfect HA Core installation script of mayukh4

And more on how to install HACS as well as some teaks on how to manage Termux and HA Core to run smoothly...
Still add more to come but you can start here

If you have any questions please send me a message on my blog

Enjoy !!

[mayukh4]

Thanks both — this thread turned into the most useful issue on the repo, and all three points are now handled in the script on main.

HACS is built in now. @audministrator you were right that it has to go first. The script asks up front (before the 30-minute install, not after), runs the official installer in the config directory, and warns you if custom_components/ already has hand-installed integrations sitting in it. Your instruction to delete /custom_components first is now in the README as a warning.

To install it on an existing setup:

proot-distro login ubuntu -- sh -c "cd ~/hass-config && wget -O - https://get.hacs.xyz | bash -"

@pcosway on the version — 2026.2.3 is not a failed install. pip installs the newest release whose requires-python your interpreter satisfies, then stops. Checking each release's metadata on PyPI:

Container Python	Newest Home Assistant you can run
3.12	2025.1.x
3.13.0 – 3.13.1	2025.5.x
3.13.2+	2026.2.x
3.14.2+	2026.3 and later

So 2026.2.3 means your container has Python 3.13.x. HA 2026.3 moved to Python 3.14, and proot-distro install ubuntu tracks a rolling Ubuntu release, which is why people installing at different times end up on different ceilings. The script now prints the container Python next to the HA version and says which ceiling you are on, instead of leaving you to guess.

On the deprecation notice you saw: Core (the Python/venv method) was deprecated upstream in 2025. It still works and still gets releases, it just is not officially supported any more. On a phone it stays the only realistic option — HA OS and HA Container both want Docker or bare metal.

@audministrator on upgrading — yes, and there is a script for it now:

bash ~/upgrade-homeassistant.sh

It stops any running instance, upgrades, and reports before/after. If nothing changes it tells you it is the Python version holding you back rather than silently doing nothing. For getting past that ceiling onto Python 3.14, there is an advanced section in the README using uv to fetch a standalone CPython and build a second venv beside the working one, so you can test before switching. I left that manual on purpose — it replaces the interpreter under a working install.

And thank you for the write-up series — genuinely helpful, and it is good to have a second, more detailed walkthrough out there.

[audministrator]

@mayukh4

Thanks a lot for this fantastic work !

This helps reducing the digital pollution as older Android devices get a new live 👍