Man this looks great! Good luck with the progress on this.
Happy to pay for access when it’s ready!
Just tested,
And any restart of the UTM VM loses the USB. e.g. every Home Assistant update.
Trying to mount the USB via the GUI provides this error which is really frustrating.
Hey @noobey thanks for the positive feedback! I have made a good chunk of progress lately, albeit some delay where I had to take a business trip.
I don’t have much to share in terms of screenshots as the work is all behind the scenes stuff. I had some issues with the python GUI library ‘Tkinter,’ used for constructing the main menu. I have since completely re-written the code for the main menu using the ‘Qt’ library and am very pleased with the result so far. This was a fairly big job as the library is completely different so I basically had to start the GUI module again from scratch.
It looks much the same as it did before, however what you can’t see in a stationary screenshot is that the menu works much more smoothly now, without any graphical glitches. The prior Tkinter example would sometimes fail to load the tab contents upon clicking the menu item. Now it is working perfectly 
Once I finish the menu, i’ll create a seperate thread here about HASS Manager for anyone who might be interested in the project. Would be good to gather a few folks who might want to test the early versions and also any feature requests.
Also, for anyone else running Windows or Linux systems who might be interested in this, I am writing it in Python specifically so I have the option to eventually port it to those operating systems, so this is not a Mac-only endeavour!
2 Likes
@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
2 Likes
Hi, did you find any solution to your second problem (keeping using wifi)? I have the same issue
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.
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
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"
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!
Can confirm it works on my MacBook M1 (2020)
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
1 Like
Im running HA now on a Dell mini PC. Best choice ever!!
1 Like
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?
1 Like
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.
I ran through this, following instructions multiple times, but I end up with “Display output is not active” every time. Any ideas?
1 Like
same error here!
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.
Set the emulated display card to virtio-gpu-pci
2 Likes