November 22, 20241 yr Author 3 hours ago, diedrichg said: Unraid 7.0.0-beta4 M.2 Accelerator with Dual Edge TPU Dual Edge TPU Adapter - PCIe x1 Low Profile - installed in the bottom slot (Slot 4 PCI-E 2.0 X4), there is a NVIDIA T400 in the top slot and a RAID controller in the middle slot Supermicro X10SLM-F motherboard Unraid 7 does not mount the Coral TPU, I've watch the bootup sequence and saw the Coral drivers be installed but the device does not show up in the devices list and the Coral plugin page says a Coral device cannot be found. I went into the bios and set the PCI-E slots to UEFI which were set as Legacy assuming that might be the issue since Unraid is loading through UEFI, that did not solve the issue. root@Daedalus:~# lsmod | grep apex apex 20480 0 gasket 102400 1 apex root@Daedalus:~# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:16.1 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #2 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 8 Series Chipset Family Thermal Management Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T400 4GB / T400E] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1) 02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) 03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03) 04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30) 05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) Is there a known issue with loading a M.2 TPU/PCIe Adapter in Unraid 7.0.0.-beta4? No, I have not moved the device to my other Unraid box which is running 6.12.x, I just haven't had time to do that yet and thought I'd ask here first. @ich777 can you help? I don't know much about m.2 tpus.
November 22, 20241 yr 3 hours ago, diedrichg said: Unraid 7 does not mount the Coral TPU Please post your Diagnostics for further troubleshooting. However I don't see the TPU in your PCI devices list, this indicates usually some issue with the Firmware (BIOS).
November 22, 20241 yr 18 hours ago, diedrichg said: Is there a known issue with loading a M.2 TPU/PCIe Adapter in Unraid Are you running active/passive cooling on the Coral. Without cooling it will shutdown pretty quickly if not immediately.
November 23, 20241 yr just trying to understand some things before i install the frigate add on do i need to install the go2rtc app also or is this built into frigate thanks
November 23, 20241 yr Author 1 hour ago, grayman said: just trying to understand some things before i install the frigate add on do i need to install the go2rtc app also or is this built into frigate thanks It is built in
November 23, 20241 yr Hello, recently started using Frigate. Getting below errors, I believe its related to audio recording/playback maybe. [h264 @ 0x14f3a4149c40] SEI type 5 size 2520 truncated at 1936 Audio works fine in live view but when recording is triggered, the error shows up and audio is not recorded. My camera supports only G.711A and G.711U (not AAC).
November 23, 20241 yr On 11/22/2024 at 2:37 AM, ich777 said: Please post your Diagnostics for further troubleshooting. However I don't see the TPU in your PCI devices list, this indicates usually some issue with the Firmware (BIOS). See attached diagnostics. I'm thinking MB BIOS. What would be the general settings? EDIT: I moved the adapter to the Unraid 6.12 box and it isn't showing up there either. I'm marking this issue as stale until I can troubleshoot more with either BIOS settings or trying a new adapter. On 11/22/2024 at 5:14 PM, Bruceflix said: Are you running active/passive cooling on the Coral. Passive. But I do have a 40mm Noctua I could throw on it. Would overheating be the case even if it's not being used. daedalus-diagnostics-20241123-1644.zip Edited November 23, 20241 yr by diedrichg
November 24, 20241 yr 8 hours ago, diedrichg said: See attached diagnostics. I'm thinking MB BIOS. What would be the general settings? I have the exact same hardware as you this PCIe adapter and the Dual Edge TPU. No special settings are needed on my ASUS Z490E GAMING Motherbard, it works right OOB regardless if I set UEFI or Legacy boot, both are just working fine. Either the Adapter or the TPU is defective but I can't tell for sure, do you have consumer hardware too where you could put the adapter in and see if it is recognized?
November 25, 20241 yr I have two reolink cameras, a doorbell camera and the Argus PT, connected to my Reolink Hub. The Hub is hooked in to HA directly and I can see and control both cameras from HA. I've also written some automations to notify me when motion is detected on either camera as well as send a screen shot. I want to set up Frigate but I'm unable to determine how that integrates properly with the home hub and how it would all ultimately integrate with HA.
November 25, 20241 yr Author 8 hours ago, Professor Oak said: I have two reolink cameras, a doorbell camera and the Argus PT, connected to my Reolink Hub. The Hub is hooked in to HA directly and I can see and control both cameras from HA. I've also written some automations to notify me when motion is detected on either camera as well as send a screen shot. I want to set up Frigate but I'm unable to determine how that integrates properly with the home hub and how it would all ultimately integrate with HA. You have specific docs regarding Reolink camera configuration: https://docs.frigate.video/configuration/camera_specific/#reolink-cameras The HA Addon if you want to deploy it like that: https://docs.frigate.video/frigate/installation#home-assistant-addon And the HA integration if you deploy it as a Stand Alone docker: https://docs.frigate.video/integrations/home-assistant
November 25, 20241 yr 5 hours ago, yayitazale said: You have specific docs regarding Reolink camera configuration: https://docs.frigate.video/configuration/camera_specific/#reolink-cameras The HA Addon if you want to deploy it like that: https://docs.frigate.video/frigate/installation#home-assistant-addon And the HA integration if you deploy it as a Stand Alone docker: https://docs.frigate.video/integrations/home-assistant Thanks! So, if I have all of my cameras going through the hub, I'd treat it like the NVR config in the example config?
November 25, 20241 yr Author 1 hour ago, Professor Oak said: Thanks! So, if I have all of my cameras going through the hub, I'd treat it like the NVR config in the example config? I cannot help you, I don't have reolink cameras. I suppose that yes.
November 25, 20241 yr I cannot hear any audio through my iPhone on live view even after enabling audio. Is there some special config setting I need to make? Edited November 25, 20241 yr by bugsysiegals
November 25, 20241 yr On 11/23/2024 at 1:40 PM, yayitazale said: It is built in thanks for the reply. i have another question would LAG something to use with this?
November 26, 20241 yr On 11/23/2024 at 4:19 PM, itlists said: Hello, recently started using Frigate. Getting below errors, I believe its related to audio recording/playback maybe. [h264 @ 0x14f3a4149c40] SEI type 5 size 2520 truncated at 1936 Audio works fine in live view but when recording is triggered, the error shows up and audio is not recorded. My camera supports only G.711A and G.711U (not AAC). Hoping someone can help with this issue. Thanks
November 26, 20241 yr Author 13 hours ago, bugsysiegals said: I cannot hear any audio through my iPhone on live view even after enabling audio. Is there some special config setting I need to make? https://docs.frigate.video/configuration/live
November 26, 20241 yr Author 5 hours ago, itlists said: Hoping someone can help with this issue. Thanks I cannot help you without your config, but you should use built-in Got2rtc restream to change the audio codec: https://docs.frigate.video/configuration/restream
November 26, 20241 yr I managed to hook both Reolink Cameras in to Frigate via the Reolink hub and can view them in the dashboard. One of the cameras is battery powered and will auto-sleep after 5 minutes and kill the RTSP stream. The Reolink documentation (here) states that the RTSP stream will need to be re-requested and may need to have a longer timeout set. Here is my current config: mqtt: enabled: true host: 192.168.1.192 port: 1883 detect: width: 896 height: 672 fps: 5 record: enabled: True retain: days: 3 mode: all events: retain: default: 30 mode: motion cameras: reolink_hub_front_door: ffmpeg: inputs: - path: rtsp://admin:<password>@192.168.1.209/Preview_01_main roles: - record - path: rtsp://admin:<password>@192.168.1.209/Preview_01_sub roles: - detect motion: mask: 0.32,0.012,0.319,0.063,0.665,0.063,0.666,0.004 zones: Front_Door: coordinates: 0.169,0.523,0.176,0.694,0.003,0.791,0.007,0.986,0.99,0.993,0.729,0.733,0.725,0.525 loitering_time: 0 objects: person review: alerts: required_zones: Front_Door reolink_hub_carport: ffmpeg: inputs: - path: rtsp://admin:<password>@192.168.1.209/Preview_02_main roles: - record - path: rtsp://admin:<password>@192.168.1.209/Preview_02_sub roles: - detect motion: mask: 0.24,0.013,0.232,0.099,0.766,0.097,0.748,0.011 zones: Carport: coordinates: 0.014,0.267,0.016,0.991,0.981,0.979,0.937,0.231,0.854,0.149,0.628,0.133,0.227,0.138 loitering_time: 0 review: alerts: required_zones: Carport version: 0.14
November 26, 20241 yr 16 hours ago, yayitazale said: I cannot help you without your config, but you should use built-in Got2rtc restream to change the audio codec: https://docs.frigate.video/configuration/restream Thanks for the link, I just needed to add - ffmpeg:camera#audio=aac to my cameras under go2rtc. But as I look at the camera section in your link, my camera settings look different ... can you confirm I'm benefitting from go2rtc with these settings? # Required cameras: # Required: name of the camera Driveway1: # Optional: Enable/Disable the camera (default: shown below). # If disabled: config is used but no live stream and no capture etc. # Events/Recordings are still viewable. enabled: true # Required: ffmpeg settings for the camera ffmpeg: # Required: A list of input streams for the camera. See documentation for more information. inputs: # Required: the path to the stream # NOTE: path may include environment variables or docker secrets, which must begin with 'FRIGATE_' and be referenced in {} - path: rtsp://liveview:{FRIGATE_RTSP_PASSWORD}@x.x.x.x:554/cam/realmonitor?channel=1&subtype=1 #1/0 ... 1920x1080 ... 1/1 ... 704x480 ... 1/2 ... 1280x720 # Required: list of roles for this stream. valid values are: audio,detect,record # NOTICE: In addition to assigning the audio, detect, and record roles # they must also be enabled in the camera config. roles: # - audio - detect - path: rtsp://liveview:{FRIGATE_RTSP_PASSWORD}@x.x.x.x:554/live roles: - record # Optional: stream specific global args (default: inherit) # global_args: # Optional: stream specific hwaccel args (default: inherit) # hwaccel_args: # Optional: stream specific input args (default: inherit) # input_args: # Optional: camera specific global args (default: inherit) # global_args: # Optional: camera specific hwaccel args (default: inherit) # hwaccel_args: # Optional: camera specific input args (default: inherit) # input_args: # Optional: camera specific output args (default: inherit) # output_args: detect: width: 704 height: 480 live: stream_name: Driveway1 # Optional: timeout for highest scoring image before allowing it # to be replaced by a newer image. (default: shown below) best_image_timeout: 60 # Optional: Configuration for how camera is handled in the GUI. ui: # Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below) # By default the cameras are sorted alphabetically. order: 0 # Optional: Whether or not to show the camera in the Frigate UI (default: shown below) dashboard: true
November 27, 20241 yr Author 18 hours ago, bugsysiegals said: Thanks for the link, I just needed to add - ffmpeg:camera#audio=aac to my cameras under go2rtc. But as I look at the camera section in your link, my camera settings look different ... can you confirm I'm benefitting from go2rtc with these settings? # Required cameras: # Required: name of the camera Driveway1: # Optional: Enable/Disable the camera (default: shown below). # If disabled: config is used but no live stream and no capture etc. # Events/Recordings are still viewable. enabled: true # Required: ffmpeg settings for the camera ffmpeg: # Required: A list of input streams for the camera. See documentation for more information. inputs: # Required: the path to the stream # NOTE: path may include environment variables or docker secrets, which must begin with 'FRIGATE_' and be referenced in {} - path: rtsp://liveview:{FRIGATE_RTSP_PASSWORD}@x.x.x.x:554/cam/realmonitor?channel=1&subtype=1 #1/0 ... 1920x1080 ... 1/1 ... 704x480 ... 1/2 ... 1280x720 # Required: list of roles for this stream. valid values are: audio,detect,record # NOTICE: In addition to assigning the audio, detect, and record roles # they must also be enabled in the camera config. roles: # - audio - detect - path: rtsp://liveview:{FRIGATE_RTSP_PASSWORD}@x.x.x.x:554/live roles: - record # Optional: stream specific global args (default: inherit) # global_args: # Optional: stream specific hwaccel args (default: inherit) # hwaccel_args: # Optional: stream specific input args (default: inherit) # input_args: # Optional: camera specific global args (default: inherit) # global_args: # Optional: camera specific hwaccel args (default: inherit) # hwaccel_args: # Optional: camera specific input args (default: inherit) # input_args: # Optional: camera specific output args (default: inherit) # output_args: detect: width: 704 height: 480 live: stream_name: Driveway1 # Optional: timeout for highest scoring image before allowing it # to be replaced by a newer image. (default: shown below) best_image_timeout: 60 # Optional: Configuration for how camera is handled in the GUI. ui: # Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below) # By default the cameras are sorted alphabetically. order: 0 # Optional: Whether or not to show the camera in the Frigate UI (default: shown below) dashboard: true As the name implies, you have set the restream at the top. Restream means that go2rtc is going to take the feed of the original stream from your camera and restream it, as a new stream, with the codec you specify (for example, changing the audio codec as you want to do). Therefore, in the configuration of the cameras, if you keep using the original feed of the camera, it is useless that you have configured restream. To use the restream, you must use the url with the form that is indicated in the documentation that I pass you with the base rtsp://127.0.0.1:8554/name_your_rtsp_cam Please try to read some more documentation and try it yourself, as there are thousands of frigate users and I can't dedicate my life to help everyone.
November 28, 20241 yr On 11/26/2024 at 1:44 AM, yayitazale said: I cannot help you without your config, but you should use built-in Got2rtc restream to change the audio codec: https://docs.frigate.video/configuration/restream Ah yes, sorry here is the config. I'm using restream but the error is still there go2rtc: streams: cam_front: - rtsp://username:{FRIGATE_CAMERA_PASSWORD}@10.10.!!.!!:554/CH001.sdp - ffmpeg:cam_front#audio=opus cam_front-sub: - rtsp://username:{FRIGATE_CAMERA_PASSWORD}@10.10.!!.!!:554/CH002.sdp - ffmpeg:cam_front-sub#audio=opus cameras: cam_front: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/cam_front input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/cam_front-sub input_args: preset-rtsp-restream roles: - detect - audio
November 29, 20241 yr On 11/13/2024 at 3:15 AM, ConnerVT said: As a follow up, it would be better to make sure the boot flash and Coral TPU are even on different USB controllers. If you go to Tools > System Devices, you can see where things are connected. Here is my server running Frigate: I have confirmed that the Flash USB and the Coral are not on the same bus. That shouldn't really make a difference. I need to know what else to test, what logs to provide, what settings I need to test. I can recreate the problem, I don't know what I need to provide the Dev's / community to resolve this issue. Recap: Within 24 hours of starting the Frigate docker container on my version 6.12.13 of unraid. The server's flash USB will become unavailable. I have to shutdown the server, strip it down, remove the flash drive and do a repair USB drive on a windows PC. Then I can reassemble and restart the server, start a parity check and without the Frigate container started, everything works just fine. I have removed the reference to the Coral USB in the App config but I have retained it in the Docker config. Please refer to post for more details. I have built this system with Frigate in mind. I've invested heavily in the camera recommendations, added a Coral TPU and I'm disappointed in the failing of this app. It could be a simple setting. but I'm at the end of my technical diagnosis knowledge base. Any help will be appreciated.
December 3, 20241 yr Hello I have been using Frigate for a while (CPU detector) and it has been working great for the most part. I have had high CPU usage which is expected and finally took the plunge and bought a coral USB. I plugged in the Coral USB and it was detected by Frigate. I can go to 'System Metrics' and see Coral there however after a minute or so it crashes. with this: frigate.watchdog INFO : Detection appears to have stopped... Exiting Frigate... Some errors other errors I see is the following, but that one is during boot [but frigate still loads after this error], so unsure if it is connected. 2024-12-02 08:08:23frigate.watchdog Detection appears to be stuck. Restarting detection process...info 2024-12-02 08:08:23detector.coral Starting detection process: 614info 2024-12-02 08:08:23frigate.detectors.plugins.edgetpu_tfl Attempting to load TPU as usbinfo 2024-12-02 08:08:25frigate.detectors.plugins.edgetpu_tfl TPU found 0-0bulk USB transfer error 1 [LibUsbDataOutCallback] 2024-12-02 08:08:25unknown Fatal Python error: Aborted I have tried increase the shm size and the tmpfs size. I have tried installing and uninstalling and reinstalling the coral drivers in the community apps. I have turned on privilege mode. I have also reinstalled frigate multiple times. I have also used a powered USB hub and tried various USB ports. I am using a Z68X-UD3H-B3 motherboard with a i5-3570 (unsure if this matters). I have included /dev/usb in my docker config and the detector in my config file I have done a lot searching but no answers/solutions. Currently reverting back to CPU detectors so my cameras are recording and detecting. Thanks in advance mqtt: host: [REDACTED] port: [REDACTED] user: [REDACTED] password: [REDACTED] detectors: coral: type: edgetpu device: usb cameras: yi2: ffmpeg: inputs: - path: [REDACTED] roles: - record record: enabled: true retain: days: 7 mode: all events: retain: default: 7 snapshots: enabled: false timestamp: true bounding_box: true retain: default: 10 detect: enabled: false width: 1920 height: 1080 yi1: zones: road: coordinates: 1920,615,1849,557,310,622,104,638,240,708 ffmpeg: inputs: - path: [REDACTED] roles: - record - detect record: enabled: true retain: days: 7 mode: all events: retain: default: 7 mode: active_objects snapshots: enabled: false timestamp: true bounding_box: true retain: default: 10 required_zones: - road detect: enabled: false width: 1920 height: 1080 review: alerts: required_zones: - road front: motion: mask: - 1876,996,1873,1080,1386,1080,1381,1001 zones: door: coordinates: 1920,0,1920,1080,0,1080,0,875,979,815,1517,810,1509,0 ffmpeg: inputs: - path: [REDACTED] roles: - detect - record record: enabled: true retain: days: 21 mode: all events: retain: default: 14 mode: active_objects snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 required_zones: - door detect: enabled: true width: 1920 height: 1080 review: alerts: required_zones: - door front2: motion: mask: - 1383,1080,1891,1080,1888,995,1375,1000 - 301,1080,0,1080,0,0,931,0,712,31,115,121,142,505 - 1920,1080,1522,1080,1754,634,1863,228,1182,55,374,0,1920,0 zones: door2: coordinates: 1920,132,1920,1080,316,1080,186,626,822,466,1188,370,1290,393,1541,462,1578,229 ffmpeg: inputs: - path: [REDACTED] roles: - detect - record record: enabled: true retain: days: 21 mode: all events: retain: default: 14 mode: active_objects snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 required_zones: - door2 detect: enabled: true width: 1920 height: 1080 fps: 5 objects: track: - person review: alerts: required_zones: - door2 version: 0.14 Edited December 3, 20241 yr by johnnyfive
December 4, 20241 yr Author On 11/28/2024 at 2:42 AM, itlists said: Ah yes, sorry here is the config. I'm using restream but the error is still there go2rtc: streams: cam_front: - rtsp://username:{FRIGATE_CAMERA_PASSWORD}@10.10.!!.!!:554/CH001.sdp - ffmpeg:cam_front#audio=opus cam_front-sub: - rtsp://username:{FRIGATE_CAMERA_PASSWORD}@10.10.!!.!!:554/CH002.sdp - ffmpeg:cam_front-sub#audio=opus cameras: cam_front: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/cam_front input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/cam_front-sub input_args: preset-rtsp-restream roles: - detect - audio I don't know if you are using MSE or WebRTC so check this, I cannot help you much more as this issues are so specific to each camera and configuration: https://docs.frigate.video/configuration/live/#live-view-technologies
December 4, 20241 yr Author On 11/29/2024 at 8:04 PM, Phreaknes said: I have confirmed that the Flash USB and the Coral are not on the same bus. That shouldn't really make a difference. I need to know what else to test, what logs to provide, what settings I need to test. I can recreate the problem, I don't know what I need to provide the Dev's / community to resolve this issue. Recap: Within 24 hours of starting the Frigate docker container on my version 6.12.13 of unraid. The server's flash USB will become unavailable. I have to shutdown the server, strip it down, remove the flash drive and do a repair USB drive on a windows PC. Then I can reassemble and restart the server, start a parity check and without the Frigate container started, everything works just fine. I have removed the reference to the Coral USB in the App config but I have retained it in the Docker config. Please refer to post for more details. I have built this system with Frigate in mind. I've invested heavily in the camera recommendations, added a Coral TPU and I'm disappointed in the failing of this app. It could be a simple setting. but I'm at the end of my technical diagnosis knowledge base. Any help will be appreciated. Please can you open a issue in github?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.