Fedora IoT and Home Assistant

As announced is Fedora IoT still pretty close to Fedora Atomic but I was curious how it “looks and feels”. Ok, more “feels” than there is not much see beside the prompt. My encounters with different ARM hardware and Fedora in the past where not always successful, thus I decided to take a Raspberry Pi Model B instead of one out of the Orange Pi family.

First step is to get a nightly image build Fedora IoT as described in the Getting started documentation.

Just a side note: With the ARM installer, which is available in Rawhide, the Error: mount /dev/mmcblk0p4 /tmp/root failed  error is gone. It might be that the same applies to Fedora 28 as well but was present in Fedora 27.

Let the ARM installer create the SD card.

After booting the Raspberry Pi up, create a new user. Now you are able to use SSH to log in. The current build of Fedora IoT allows you to use a recent kernel.

Of course is the deployment up-to-date. One advantage of nightly build if you are using one the next morning 😉 .

Instead of Docker is podman  used to deal with all container-related tasks. To get the Home Assistant images run the command below:

As you can see it’s pretty much the same as using the  docker command-line tool.

Create a directory to store the configuration.

And start the Home Assistant after you have adjusted the host’s firewall to match your needs.

Et voilà, http://IP_ADDRESS_FEDORA_IOT_HOST:8123 is serving the Home Assistant frontend.

I will skip the autostart part as this is already covered in the blog post about Project Atomic and Home Assistant. No much news in this blog post beside podman. Pulling images are problematic at first because often the download stopped somewhere over 95 % (no, never at 20 % or 60 % ) in my case a local registry solved the issue for now.

This entry was posted in Fedora, General. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.