[Guide] Home Assistant on Apple Silicon Mac using HA OS AArch64 Image

noobey · October 27, 2023, 9:24am

This looks great, looking forward to it @Siytek!

Siytek · December 3, 2023, 9:34pm

@noobey I have made some great progress in the last week or two

I have opened a dedicated thread for the HASS Manager app, would be great to get some thoughts and feedback, check it out here - An easier way to install and manage Home Assistant on desktop systems! - HASS Manager

liviu_k2 · January 14, 2024, 6:09pm

Hi, did you find any solution to your second problem (keeping using wifi)? I have the same issue

chasut · February 9, 2024, 5:06pm

I just moved my HA instance from Docker Core on a Synology NAS over to a HAOS/Supervised on an M2 Mac Mini w/UTM following this guide. It started as an experiment when I upgraded my NAS, but the results are way better than I expected. I have a fairly complicated setup, but a full restart now only takes about 17 seconds, v. about a 1.5 minutes on my old NAS (DS916+). Bigger surprise was that my cameras (unifi protect) load and are fully live in ~ 1-1.5 seconds v 2-4 seconds.

Very pleased with the results. A big thanks to the OP and all that contributed.

fmon · February 10, 2024, 1:53am

For those that want to pass through bluetooth, I have it working with this dongle. There’s a “software download” for MacOS in the instructions but you don’t need it if you apply this terminal command:

sudo nvram bluetoothHostControllerSwitchBehavior=always

fmon · February 11, 2024, 12:34am

Also: I couldn’t figure out why every time I rebooted the virtual machine HA decided no one was home and then I realized that the USB dongles needs to be reconnected to the VM every time. There’s no setting in UTM to have this happen on boot, but you can script it. Use

utmctl usb list

to get the 8-digit VID:PID and then do this at startup In the host system:

/usr/local/bin/utmctl usb connect "your_vm_name" "1234:1234"

noobey · March 21, 2024, 3:24pm

Hi all,
I have a really weird issue i could use some expert help with.

Background:
I have HA running on a mac in a UTM VM, with 100GB allocated for storage to the VM.
It’s worked great for nearly 2 years, until this month.

From March 15th (5 days ago), it appears something is gobbling up space and I dont know what.

Here’s what I’ve tried so far:

Cleaning the database as described in the user guide.
Deleted all unused addons.
Deleted all my local backups (only had 3), and will rely on my Google Drive backsups until new backups are created.
Found my Nest folder, which had loads of images from my old doorbell. changed permissions in the integration to no longer create snapshots and also deleted that Nest folder.
Deleted the core file which clocked in at 6GB.
Disabled the custom Tesla integration as it stopped working recently due to an API change, and I thought it might be creating a large log file.
There are no log files I can see that are over a few MB.
Today I complete rebuilt UTM, and immediately after restoring from my backup it was at 90% and didn’t have enough free space to even open ESPhome.

All that got me down to 70% free space but somehow within 3 hours I’ve lost 10% and am pretty sure I’ll max out storage again tonight.

When browsing the HA install via samba/smb I can’t see any large files in any of the folders. Nothing looks out of place at all.
Can anyone help me figure this out and point a newbie in which direction to look for what it could be please?

Appreciate any and all help, thanks!

Grawl · April 14, 2024, 1:03pm

Can confirm it works on my MacBook M1 (2020)

smithumble · June 19, 2024, 9:33am

You may not have unzipped the image.

This is an archive
chaos_generic-aarch64-x.x.qcow2.xz

You have to unzip it to get
chaos_generic-aarch64-x.x.qcow2

poudenes · June 19, 2024, 1:07pm

Im running HA now on a Dell mini PC. Best choice ever!!

Jz777 · August 10, 2024, 6:25pm

Thanks for the guide–everything went quickly and HA boots up fine.

However, I can’t access it through port 8123. I can access the observer on port 4357.

The IP shows up on my router and I can ping it. I’ve tried:

http://[ip addy]:8123
I’ve edited my hosts file with the IP:
[ip] homeassistant.local

All 3 of these variations work for port 4357, showing:

Supervisor:	Connected
Supported:	Supported
Healthy:	Healthy

I’ve let HA sit after booting for 30’. Might I need to wait longer?

Any ideas?

Might it be easier to go buy an old laptop?

sonergokdogan · December 2, 2024, 9:18am

Thanks a lot, it works with an M3 Mac Pro (Sequoia). Just had to extract the disk image after the download. Perhaps a small improvement on step 2, to avoid novice people like me to stop trying.

rickybright · December 3, 2024, 6:25pm

I ran through this, following instructions multiple times, but I end up with “Display output is not active” every time. Any ideas?

aakashthakkar · December 5, 2024, 8:12pm

same error here!

diegocj · December 6, 2024, 3:23pm

I am also encountering the “Display output is not active” error, but I found a workaround.

You can add a serial device in “Built-in Terminal” mode and use that terminal to interact with HAOS.

To log in, simply type root. After logging in, you can run the command ha network info to view the IP address you need to connect to.

fmon · December 8, 2024, 9:49pm

Set the emulated display card to virtio-gpu-pci

masterchiefalfa · December 14, 2024, 11:37pm

Hi @Jz777 - were you able to figure out the issue ? I am running into the same problem.

Jz777 · December 15, 2024, 1:37am

Nope, sorry.

I solved it by buying a used NUC on eBay for $35, only to find out my local university surplus had them for less. The NUC is doing fine running HAOS with no containers.

I definitely don’t regret spending the money to avoid problems with containers. It could be the smartest thing with HA that I’ve done to date.

GeoffaatMM · December 20, 2024, 11:00pm

Hi all,

I am completely new to HA and while I can use CLI, I am in no way expert.

I am trying to get HA working on an iMac24. The UTM interfaces have changed a bit but I managed to follow the guide (thanks BTW) and work out what to do and now have the virtual instance running with the CLI prompt of -

ha >

However, I cannot access either port 8123 or 4357. I suspect it is a networking issue from reading the comments. The iMac 24 only ships with a wifi interface. I have an ethernet adapter but I have not found it to be 100% reliable.

When I set up the network I selected bridged but did not select an interface. I left it as Auto assuming it would find the WiFi interface and use it but it does not appear to have done so.

I cannot find a guide to run HA natively on a silicon Mac so UTM seems the best option but only if I can get the WiFi to respond. I stopped the machine, edited the network to be shared and relaunched it.

Port 8123 appears to open correctly (but I have yet to explore it) but Port 4357 runs up to a point but then gives the following repetitive error.

Home Assistant installation. Retrying in 30sec
2024-12-20 22:42:03.421 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
2024-12-20 22:42:03.421 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sece

First question is will using the shared network in lieu of bridged give me issues?

Second question is why is the Supervisor page not completing properly?

Are there logs I should post?

Finally, is this the right place to ask these questions or should I open a new thread?

Thanks in Advance,

Geoff

diegocj · December 22, 2024, 5:03pm

Thank you, fmon! I can confirm that setting virtio-gpu-pci resolves the issue. On a side note, I also updated to HAOS 14.1, though I’m not sure if that update is also necessary.