For those of you who were reluctant to use UTM due to it not having an option to start on booting Mac OS, it is actually rather simple to get UTM to launch the Home Assistant VM on boot, there is a section that explains how to do this in the aforementioned article.
If anyone is looking to run Home Assistant Core natively on Mac OS using venv, I covered it in one of my older tutorials that you can check out here and can confirm it works on M1 Mac. However in almost all cases I would recommend the UTM approach, as running Core without supervisor will be lacking some features, such as the add-ons store.
Questions or comments on any of those articles is of course welcome, and thanks guys for the earlier posts, some valuable information in this thread!
New Drive > IDE > Import: select the āhaos_ova-8.5.qcow2ā image file previously extracted
Save
Start the VM
Viola, you have a fully functional HassOS that will start up and configure itself.
Note, it will restart a few times while setting itself up and once running and you connect to the http:// address, it will take a long time to āPrepareā itself. It says up to 20 mins but I think mine took longer.
Iāve been running this for over a month now and it has taken itself through a number of HA version upgrades and one OS upgrade.
The one thing Iāve noticed lacking is Bluetooth from the Macās motherboard. However, I suspect a USB bluetooth dongle would work with the UTM USB passthrough.
Absolutely brilliant @JurajNyiri. I had searched but had not found an ARM build workable on UTM, but it was there all along and works blazingly fast. I did a backup and restore and now have it running on a native ARM VM.
One question though, how did you do the resize of the qcow2 image to 64GB? After all the steps, my image is sitting at 5.2GB. My previous install ended up with a 15GB disk image, but 64GB would be much better.
Amazing guide but the only part is I canāt load the UI. I try to enter the urls provided once the VM loads successfully, but none of them resolve. Anyone know what my issue might be? (I followed the guide to a T).
Edit: I found other tutorials and the error Iām seeing is due to IP not being assigned. āYour Network is probably not using the DHCP protocolā? My router definitely uses DHCP. Iām using wireless and havenāt tried wired yet. I tried assigning a static IP using the MAC address but still nothing.
Did you get this going?
It sounds like a cause could be the network is not bridged to the correct Mac interface. Usually this is en0, but depending on your Macās network connection this could be something else.
In terminal type āifconfigā. This will list the interfaces on your Mac. Find the one containing inet xxx.xxx.xxx.xxx where xx is your Macās LAN IP address.
Then in UTM go to the āNetworkā page, select āBridged (Advanced)ā, in the āBridged interfaceā input field, enter the interface you found above.
Restart the VM and note the IPv4 address on the VM screen as below. It should be the same subnet as your Mac. Use that IP address in your browser with :8123 on the end.
This totally kick arse @HJM@JurajNyiri , I have using my Synology NAs which is so slow, and then UTM on the mac mini (using emulation), still slow! Then found this guide, startup went from at least 3-5 mins to under 30 seconds! Just Awesome!
Any idea how to get copy paste working? I noted that in the startup logs I get
[FAILED] Failed to start QEMU Guest Agent.
See āsystemctI status gemu-guest.serviceā for details.
I could just SSH it and get copy-paste working, but when troubleshooting on the VM, itās just nice to have.
Note I had the same issue using UTM when using emulation.
That decision is more based on what you want to achieve, a whole vm in UTM or Parallels will allow you to run HassOS or Supervisor, a docker container will be a single item, so will be only Core.
A VM (which will then run docker inside it) will use more resource than a single container.
I did, thanks. Funny enough, I ran into a different problem when I replaced my routers. Apparently Tp-Link Decos donāt work with virtual machines unless you hard wire them. Otherwise, it could appear in the app which prevents you from port forwarding properly.
Hello, Iāve gotten HA running on Mac Mini M1 using UMT by restoring from a rp4 backup. For the life of me I canāt seem to figure out how to get the Aeotec Z-Wave stick to be seen. Iāve selected the right USB option on the running virtual machine (when I plug in the Aeotec stick it prompts me new USB device detecte, Iām using an USB hub since the Aeotec stick is too bulkly and lack of USB ports on the Mac Mini). Could it be the backup of the rp4 causing this issue and I just need to restart from scratch, (would like to retain what I already have running on rp4) though if possible. The reason Iām moving over to Mac Mini M1 is because HA on rp4 keeps stalling after few days of operation and I have to restart rp4 to get it back to operating. If someone knows how to prevent the stalling issue on rp4 please advise, Iām thinking its mostly related to the SD card from my online search for this issue. HA does seem to run much more quicker on the Mac using UTM compared to the rp4. Thanks in advance!
Are you using Debian on UTM or HASS OS? How are you validating that the USB isnāt being seen in the VM? I use Parallels personally which shows me if it thinks the Aeotec is connected to the VM, then in Z-Wave JS UI it shows on this serial port - /dev/serial/by-id/usb-0658_0200-if00 - which I can validate by checking for it in Terminal/SSH.
Iām using Debian on UTM, when going over to the left sidebar of HA and clicking on Z-Wave JS Iām seeing this in red background āDriver: Failed to open the serial port: Error: No such file or directory, cannot open /devā. Also on the Z-Wave JS intergration Iām getting āRetrying setup: Noneā. Sorry Iām novice when it comes to HA, everything Iāve done so far is from guides that others with more knowledge have created.
I would look in that directory and see what serial port it is on (/dev/serial/by-id), and then validate that you are configured to use the correct port. It may have changed from RP4 to UTM, since that is not managed by HA. Sorry I canāt guide more, but it should be configured by the add-on you are using, as I said before Z-Wave JS UI
Thanks for the additional information, now to research and find out how to locate that directory and see what it holds. Thanks again for all the assistance so far!
