From the user experience - how many TPUs are needed to run eight full HD cams? 4k cams?
Any ideas why the CPU latency grows over time? Had a fresh install of the forked addon (running on an old c2d processor machine). One camera attached with 640*480@5fps resolution. At first inference speed showed up at 10ms.
After 8 hours of running it’s behind 800ms. Looking at htop - cpu utilisation is below 2%
Thanks! I will give it a try when I get home from work. That sounds similar to what I tried to achieve, but I failed extracting the relevant content from the mqtt-feed. I might come back later with further questions .
You did not specify if you are using a coral and what is your CPU. Read the docs again for Frigate for recommendations and how to run
Without Coral.
Config is as follows
detectors:
cpu1:
type: cpu
cpu2:
type: cpu
detectors:
coral:
type: cpu
device: usb
num_threads: 2
This is my setup for i5.
Getting confused by Hass addons.
Witch Frigate addon is the latest?
NVR Beta or NVR version?
Looking at the tensorflow docs - what is the point of putting in device:usb?
This is expected than, your CPU is not able to handle the 10ms inference time, 800ms is expected.
I concluded that the ‘NVR Beta’ was older/obsolete.
From the docs:
image: 'https://your.public.hass.address.com/api/frigate/notifications/{{trigger.payload_json["after"]["id"]}}/thumbnail.jpg?format=android'
format=android, what does this do and is there an equivalent for iOS?
Thanks
Thanks. Strange this is version numbers.
NVR says 1.6 and NVR Beta says 1.8 …
Will try to install NVR and see what happens.
Beta is always newest version
In this case it’s not .
Just saw this …
NVR Beta:
NVR:
I got my coral from Raspberry store it seems they still have them in stock. They ship to european countries.
Currently no active beta version (it mean that beta is outdated):
i ahve to admit that i have some difficulties followig this app. Configurations are not the same for beta and stable releases and version numbers are weird BUT the app is MORE THAN AWESOM! Now I just need that @blakeblackshear throws an eye on this as there might be a problem with latest supervisor version. Config cannot be saved as described above in my post
this sounds like this addon is no longer working without coral if I am not wrong.:
- Fallback to CPU if the EdgeTPU is not detected has been disabled. It will now keep trying to detect your EdgeTPU.
with supervisor Version:
You should use cpu mode in config in that case.
It’s normal that configuration may changed between major versions.
all right I get this thanks @arkoko I am absolutely NOT complaining I use coral. Now I just wait for a fix to save config.I manually added my config in the frigate container but this does not work at all as i need ingress. Does someone else use latest Suervisor here and has problems with this addon?
I’ve not using HA and Supervisor beta versions, but if I understood correctly today will be expected scheduled release 2021.2.1. Then we’ll see