Yeah i have tryed the LXC way,but the problem is that if you using it remotely with https, you will not see frigate…Have you tryed to access HASS remotely? not on local LAN?
I have not exposed any services or ports to the outside world. If remote access is desired, I’ll use my VPN. This will give me “local” access.
It would be way nicer to have everything integrated into homeassistant, but I guess our use case is somewhat rare. Perhaps I should investigate how to run homeassistant in an LXC.
If you dont expose it remotely only VPN, then you should try this. Worked for me and should for you.
please can you explain how to create a docker i proxmox?
i have a vm in proxmox with home assistant, gpu passtrough and usb passthrough for google coral.
but frigate isn’t stable and i have always Detection appears to be stuck. Restarting detection process
so missed a lot of detection and clips
Or i use the entire machine to home assistant and use frigate addon, or i can use frigate in docker, but i’m newbie for that.
Please can you help me?
I wrote to a docker thread, as i abandoned the docker solution because you cant connect remotely and see freegate on your phone/computer if you are not on local LAN. That was a problem for me.
This thread that i made is working perfectly on my 2 servers with proxmox. I am able to assist you on regards as my settings and my tutorial. As this is a problem with a specific machine compatibility from what i can see (github)
First if you cant use proxmox+hassos+frigade addon then the last solution would be to use whole hass system :-/
Have you tryed this thread?
Its frigate thread
I use wireguard in my rpi and i have always connected my phone in vpn. I prefer this solution.
The entire machine is a solution but a nuc have a lot of power that are useless with only Home Assistant, and if I can use nuc also for other machine, is better.
I don’t understand how to create a docker lxc in proxmox about frigate.
I don’t know where or how to, i’m a complete newbie in this way.
If i can create a lxc with frigate, maybe i can solve this issue.
For now i use proxmox+hassos+frigate+coral+gpu pass+google coral usb pass, and in this way frigate have this error Detection appears to be stuck. Restarting detection process…
so restart every time and lost a lot of detection and clips.
If i learn how to create a frigate docker, where i click, how to config, maybe i can fix it.
Give me a link to github issue.
Have you wrote to frigate thread here?
I have read all, yeah thats hard situation… i have 11cameras on each server proxmox, working perfectly…
I see, but your proxmox is like mine?
Nuc
Proxmox
HASS os into a vm
frigate addon into HASS os vm?
Google coral usb passthrough into HASS os vm ?
Because if is the same, isn’t possible that you didn’t have any trouble like me.
https://groups.google.com/g/linux.kernel/c/_HnJnBL--8k
This issue is correlated in google groups, and seems that there is a kernel fix, but where is this fix? and how can we applied it ?
intel cpu,asus motherboard small TX factor like nuc
Proxmox
HASS os into a vm
frigate addon into HASS os vm
Google coral pci passthrough + GPU passthrough into HASS os vm
What nuc you have? what proxmox version you have?
Give me output of this command
dmesg | grep -i blue
I have NUC8I3BEH
root@NUC-i3:~# dmesg | grep -i blue
[ 4.582061] Bluetooth: Core ver 2.22
[ 4.582097] Bluetooth: HCI device and connection manager initialized
[ 4.582100] Bluetooth: HCI socket layer initialized
[ 4.582102] Bluetooth: L2CAP socket layer initialized
[ 4.582106] Bluetooth: SCO socket layer initialized
[ 4.714971] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 4.715983] Bluetooth: hci0: Device revision is 2
[ 4.715985] Bluetooth: hci0: Secure boot is enabled
[ 4.715986] Bluetooth: hci0: OTP lock is enabled
[ 4.715987] Bluetooth: hci0: API lock is enabled
[ 4.715987] Bluetooth: hci0: Debug lock is disabled
[ 4.715988] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 4.716180] bluetooth hci0: Direct firmware load for intel/ibt-17-16-1.sfi failed with error -2
[ 4.716184] Bluetooth: hci0: Failed to load Intel firmware file (-2)
But i guess isn’t the output that you have expected
pve-manager/7.0-8/b1dbf562 (running kernel: 5.11.22-1-pve)
You use pci passthrough, so you can get maybe a passthrough different than usb, because i can’t pass the entire controller, there is only one.
You see bluetooth, fix that first.
If your nuc is server only,then you can pass whole USB controller. Otherwise, one of other option to buy PCI<>USB adapter and then passthrough USB to the PCI.
But beware, it’s a bit hard. As you need to use commands to split IMMOU groups to be able to seperate the PCI controller.Or just sell the USB and get PCI. The PCI is a bit hard i needed to sacrifice some stuff because of group seperation to passthrough. Nevertheless try to figure out the bluetooth and get back to me 
Or maybe try to figure out how to turn off bluetooth module during boot
Bluetooth is failing because ibt-17-16-1.sfi is not present.
The fix for this is:
cd /lib/firmware/intel/
wget wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel/ibt-17-16-1.ddc
wget wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel/ibt-17-16-1.sfi
hciconfig hci0 up
Now it works :-)
OR
wget http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20190114-2_all.deb
dpkg -x firmware-iwlwifi_20190114-2_all.deb /
About bluetooth i don’t understand why is important, anyway i’ll do that:
wget http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20190114-2_all.deb
dpkg -x firmware-iwlwifi_20190114-2_all.deb /
and now i have a terrible error:
In putty i can’t get ssh, say that pass is wrong. 
About my nuc, I use it only with proxmox, my goal is use it with some VMs, like:
Vm with Home Assistant
Vm with Pi-hole
Vm with Ubuntu test
Vm with Raspbian
Vm with Win10
In the past I have tried to install Kodi in a Vm, especially Libreelec, but was without a GPU passthrough, so 4k movies beat cpu, then I maked passthrough about gpu for the kodi vm and worked. Then there was audio problem, because was mute. Then i see the iommu groups and i discovered that audio is inside a group where is also ethernet and other stuff.
Infact when I have tried to pass also audio, i get on kodi audio, but i lost ethernet, so no internet, in kodi and also in host proxmox.The result was Kodi with audio and video, also in hdmi!, but no internet connection, no proxmox gui, no connection in other proxmox vm, a disaster, and infact if I make a frigate docker that works, maybe i can try to make also a kodi docker or lxc i don’t know, and maybe i can get a kodi that works without trouble, but this is another story and isn’t necessary for now, the priority is home assistant and frigate, that I use it for home security.
I see long way you have there.
After setting up the third proxmox server i finaly realise why its a problem with this IMMOU groups and why are some things grouped together. If i would bought a correct motherboard and CPU i would not have similar problems like you. But i figured it out and addapted (made NVME host OS through PCIx1) sacrifice.Nevertheless if i new that i need to buy a motherboard with a maximum count of PCI lanes and CPU that can handle it,then it would worked out of the box. And just FIY you can make a IMMOU group seperation. There is a command on proxmox forum. But you never know how it will seperate, its like a rulete 
no matter for other things, home assistant is my priority for now, but proxmox dead with this bluetooth firmware.
Why is important this ?
edit. for now i use hassos in another nuc, without proxmox, and of course, works, but a nuc i7 for home assistant is useless, so i’m looking for a solution with proxmox.
https://groups.google.com/g/linux.kernel/c/_HnJnBL--8k
This is the fix for this error, but how can we use it?