HAOS install on Nano Pi R2S/R4S/R5C with separated networks?

To be honest, I do like the native install (non-Docker) on my Raspi but I dislike the Raspi more and more. Also I would like to set up a dedicated network for all my HA devices and have just one dedicated bridge towards the internet that just pulls the necessary data like e.g. weather forecast or bus schedule.

So I came across the NanoPi devices that have two GbE ports and are generally more optimized for data transfer. There is e.g. the NanoPi R2S R2S but there is plenty of other models with different ports, WLAN, etc. So generally my idea is to have a native HA install to the Nano Pi, one port is facing the HA network and the other port is facing the internet.

Are there experiences with a setup of this kind? Good idea, bad idea or very bad idea?

As long as devices are local controlled this should not be an issue

Thanks - how would I actually install HA especially if it is a model with integrated eMMC like the NanoPi R5C ? Until now I just followed the instructions to pull the Hass.io image on SD and everything was working. Would Hass.io run on the Nano Pi or would I have to install another OS as basis? If yes, would this have the same effect like using the HA Docker version?

You say you want

And yet

  1. There are 4 methods of ha installation: HAOS, container, supervised and core. “Native” is unhelpful.

  2. 3 of the 4 methods use docker - core is the only one that doesn’t.

So it may be helpful to reframe your questions.

1 Like

Good point - I went with the first option on Raspberry Pi - Home Assistant installation guide and therefore I have haos_rpi4-64-9.5.img.xz
What I like is that I can install any Add-On I like e.g. Visual Studio which is to my understanding not available for Docker-Installs. The technical basis is not the problem for me, this is no religion and actually I use Docker a lot. I simply would like to have the full choice of Add-Ons.

So you want Home Assistant Operating System. There, not hard to say is it.

1 Like

The supported images are here

The generic aarch64 may work.

1 Like

Many thanks, I corrected the title.

So next step would be to load haos_generic-aarch64-9.5.img.xz to my eMMC and see what happens?

Feedback from FriendlyElec: They haven’t run HAOS on R5C and there is a lot of work expected to make it work on R5C.

Another option would be that I see some nanopi run debian bullseye, which may leave you able to run a supervised install.

1 Like

Good idea - so first flash Bullseye to the eMMC like this NanoPi R5S - FriendlyELEC WiKi and then install this GitHub - home-assistant/supervised-installer: Installer for a generic Linux system like this Install Home Assistant (Supervised) on Debian - Matheson Steplock or is there a better guide to install HA supervised?

The supervised install instructions are here Linux - Home Assistant

There is a good guide here. Installing Home Assistant Supervised on Debian 11

Having said all this, have you spent money on the nanopi yet? You may be better on a x86-64 machine with 2 nics.


I got the Nano Pi R5C working with HA Supervised / Supervisor.
It didn’t work with the Bullseye Image from FriendlyElec.

With the Bullseye image from DietPi,
the installation went through without any problems and now it works.

This is very interesting - you did Supervised, not Core? Which install manual did you follow?

I used this guide GitHub - home-assistant/supervised-installer: Installer for a generic Linux system
In detail I used these commands:

HA Supervised for NanoPi R5C (aarch64 cpu):
apt-get install \
apparmor \
jq \
wget \
curl \
udisks2 \
libglib2.0-bin \
network-manager \
dbus \
lsb-release \
systemd-journal-remote -y

#Step 2:
curl -fsSL get.docker.com | sh

cd /home

#Step 4:
sudo wget https://github.com/home-assistant/os-agent/releases/download/1.5.1/os-agent_1.5.1_linux_aarch64.deb

#Step 5:
sudo dpkg -i os-agent_1.5.1_linux_aarch64.deb

#Step 6:
wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb

#Step 7:
dpkg -i homeassistant-supervised.deb

#In Step 7 select odroid-n2

With this Steps it works for me Supervised Intallation on NanoPi R5C.

1 Like

OK - do you get those errors?

If no, did you start the installation from the latest DietPi release that got some optimizations for NanoPi?

If yes, what do you do with those errors? Just ignore?

Both of those errors have links which give you more info.

Both links I have checked and spent many hours on trying to fix them. Unfortunately without success.

Those two errors originate from the combination of hardware and OS. As drdigital has same hardware and OS it would be really interesting if he is facing the same errors and/or how he is dealing with them. At least when I followed the instructions I was not successful.

yes i have the same error.
So far I haven’t noticed any limitations in functionality.
That’s why I just hidden the errors and didn’t pay any further attention to them.

1 Like

More options to consider (I don’t trust the provided images from the google drive download):

I am still figuring out how to install them to the eMMC