That is my plan also. I’m leaning towards HAOS for one VM to collect all the data in the house and another VM for the NVR.
More august members of the forum have gotten Frigate to work in a docker container, so I will try a few more times. But if I continue to struggle, a VM it is.
Life is too short to spend hours upon hours to chase down the YAML error that makes Frigate throw its hands up and nuke the config file you were trying to submit in the app setup page.
@Constantin I too have struggled ( a lot!) with setting up Frigate using the official App but I have finally succeeded and I have found Frigate to be brilliant!
The approach I used was to set up the app thus:
The host path approach means I can find where the config.yaml lives:
so when I get stuck with a config which is ruined, I can manually delete/edit etc. at that location.
I have attempted it via TN and dockge/docker compose instead of the app but I made some mistakes and I haven’t had time to try again. On a separate machine, the “docker compose” approach worked well.
I agree on the DB point.
In fact it is just now in reading this thread that I now know why my DB changed to Postgres. I previously ran HA on a local system but hadn’t used it in a couple of years.
When I started getting back into it also coincided with installing it on TN Scale.
The first time I went to do some DB querys, I realized it was a new DB type.
I just assumed this was a change in HA during the time I was away.
I do agree that using HA on TN has been really quite simple and works pretty well. I have the config directory mounted as a share and can easily edit the config, etc. that way.
Now that TN is about to release the new version, I may try HA in a VM there. Otherwise, it’s back to a stand alone server for me.
Yeah, that’s why I roll my own YAML. I use Mariadb, mainly because I’ve used it since MySQL 4 or so, and, I have a lot of things that use Mariadb already, no need for Postgresd thusly. But I use a separate container for Mariadb since I want one place to manage it.
Just so you are aware, you’ll have to manually edit your configuration.yaml to remove the entries enabling post-gres before you can restore a backup to another Home Assistant instance. I’ve seen this come up time and time again time in the HA forums because users expect their backup to work as advertised but do not know or understand the use of 3rd party DB and think the backup / restore mechanism is broken, and then they blame Home Assistant for being a bad product and losing their entire configuration. The opinionated nature of this “app” with zero explanation has repeatedly made Home Assisatnt look bad to new users who start here and later try to move away.
i have upgraded my turenas instance to fangtooth and recreated all my dockers. Now i am trying to recreate the VM using Zvol for HA and i am having no luck. the vm won’t boot.
I haven’t gone back and tested on the release but there were no issues during the beta and RC. I assume you had HAOS running in electric eel?
Are you trying to use the existing zvol or start from scratch with a new one?
i tried both, none works
i rolled back to EE, from fangtooth and recreated my Zvol.
i made a mistake of moving my zvol. in fangtooth so reddit.
Did you see any error messages when HAOS failed to boot? Or did it boot to the UEFI shelf?
Maybe some of these troubleshooting tips could help?
I know a few people have successfully created a HAOS VM in fangtooth, so should work.
I did a quick test, and it seems to work as expected. Here are a few things I’ve seen people get hung up on in Fangtooth so far…
When I imported my zvol, I used the clone option. The following window popped up. Before hitting select, confirm your zvol is showing a Size of at least 32 GiB
Under the Network section, I uncheck Use default network settings and then select the bridge I had created on TrueNAS
After I finished creating the VM, it started automagically.
I quickly pressed the Serial Console under Tools and was able to watch the VM boot up. There was a long pause at the line Installing SP2000 support, but the message Welcome to Home Assistant eventually appeared.
At this point, I closed the Instance Console and clicked Shell
In the Instance Shell, I typed ha banner then looked under System Information and was able to verify the VM has a valid IP address.
For this example, I enter 10.10.1.67:8123 into my web browser and reach the HA login screen
Hopefully, some of that helps get you going, or at least helps to figure out what is wrong
