Hendrik6073

okay, thanks !

i feel stupid now.......... where can i see the docke settings and... where is this tools option ? on my debian machine ? sorry........😞 edit: this is my LSUSB, it shows Google, and Frigate says also it sees it. Maybe it is normal to get much higer processor times just because the camera's are also be seen /active in my Home Assistant (dashboard) and only the AI component of de images (looking for objects) is offloaded ? Would it be better to run the camera's on a dedicated NUC to not interere with Home Assistant?

yes it was broken and replaced, now i got a active led and stick is found; frigate.mqtt INFO : MQTT connected detector. coral INFO : Starting detection process: 38 frigate.app INFO : Camera processor started for voordeur: 41 frigate.edgetpu INFO : Attempting to load TPU as usb frigate.app INFO : Camera processor started for inrit: 43 frigate.app INFO : Camera processor started for achtertuin: 45 frigate.app INFO : Capture process started for voordeur: 46 frigate.app INFO : Capture process started for inrit: 51 frigate.app INFO : Capture process started for achtertuin: 52 frigate.edgetpu INFO : TPU found my config per camera looks like this; # Name of your camera voordeur: ffmpeg: inputs: - path: rtsp://192.168.2.242:554/user=admin_password=kznXUeBx_channel=1 roles: - detect - rtmp - clips - record objects: track: - person - cat # Optional: save clips configuration width: 2592 height: 1944 fps: 5 TPU part: detectors: coral: type: edgetpu device: usb I run Home Asistant on a Nuc with Intel I3, i was aspecting average load dropping with installing the Coral stick, it stays above quit high above 3. Stopping Frigate drops load down to 0.3.... is there a way to check if offloading works as it should? or is my config not correct? thanks agian!

thanks for checking, going to send it back, hope next oe works!

installed de drivers on a Ubuntu (only USB2) also not detected, nothing in LSUSB. I think it is dead

Thanks! i could have thought of that (the datasheet) myself 🥴. Anyway, reading this: 4.2 LED behavior The USB Accelerator includes an LED that indicates the current system state. The following table describes the behavior of the LED. Table 2. USB Accelerator LED behavior and meaning System state LED behavior Edge TPU initialized - Edge TPU initialized On (solid) Edge TPU running - Edge TPU running Pulse (breathe) Gives me the impression it might not lit at all when not loaded/initialized. The Windows machine i have is my tool for work, so have to be carefull installing this just for testing. have to find me another to test it on Windows

Okay! Where is it located and when does it lit? Always when connected to a USB (3.x) plug ? Or only when the drivers are loaded?. Yes i use the cable that did come with the package. Thanks!

thanks for the answer, does it not have a LED ? How big is the change to get a DOA ?

Hello, i like to ask a question about the Coral USB, because the Frigate doc's send me here i give it a try. It might be a bit off-topic, hope you dont mind... I bought a Coral USB to run Frigate on a NUC. Working toghetter with Home Assistant. I followed the instructions to set it up, log keeps telling me that the edgeTPU is not detected. Also do not see it with lsusb command (Linux Debian 10 / 64, USB 3 port). Plugged it into my Windows 10 and that also does not see a device. Is there a way to find out if the stick is healthy? There are no LED's or something ? thanks!