yayitazale Posted July 26, 2023 Author Share Posted July 26, 2023 37 minutes ago, MothyTim said: Hi, thanks for all that. I've changed the things that you've suggested, but unfortunatly it doesn't work? Here is the log and new config. text error warn system array login Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 36, in get_single_node document = self.compose_document() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 55, in compose_document node = self.compose_node(None, None) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 133, in compose_mapping_node item_value = self.compose_node(node, item_key) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node while not self.check_event(MappingEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 428, in parse_block_mapping_key if self.check_token(KeyToken): File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 116, in check_token self.fetch_more_tokens() File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 223, in fetch_more_tokens return self.fetch_value() File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 577, in fetch_value raise ScannerError(None, None, yaml.scanner.ScannerError: mapping values are not allowed here in "<unicode string>", line 180, column 15: input_args: preset-rtsp-restream-low-latency ^ s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service frigate-log successfully stopped s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped 2023-07-26 12:15:22.225758077 File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node 2023-07-26 12:15:22.225759078 node = self.compose_mapping_node(anchor) 2023-07-26 12:15:22.225760116 File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node 2023-07-26 12:15:22.225761077 while not self.check_event(MappingEndEvent): 2023-07-26 12:15:22.225762094 File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event 2023-07-26 12:15:22.225762944 self.current_event = self.state() 2023-07-26 12:15:22.225763977 File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 428, in parse_block_mapping_key 2023-07-26 12:15:22.225781265 if self.check_token(KeyToken): 2023-07-26 12:15:22.225782421 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 116, in check_token 2023-07-26 12:15:22.225783244 self.fetch_more_tokens() 2023-07-26 12:15:22.225784245 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 223, in fetch_more_tokens 2023-07-26 12:15:22.225785210 return self.fetch_value() 2023-07-26 12:15:22.225786212 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 577, in fetch_value 2023-07-26 12:15:22.225787070 raise ScannerError(None, None, 2023-07-26 12:15:22.225788017 yaml.scanner.ScannerError: mapping values are not allowed here 2023-07-26 12:15:22.225788879 in "<unicode string>", line 180, column 15: 2023-07-26 12:15:22.225789793 input_args: preset-rtsp-restream-low-latency 2023-07-26 12:15:22.225790624 ^ 2023-07-26 12:15:22.225791363 2023-07-26 12:15:22.225792311 ************************************************************* 2023-07-26 12:15:22.225807173 *** End Config Validation Errors *** 2023-07-26 12:15:22.225808212 ************************************************************* 2023-07-26 12:15:22.233284544 2023/07/26 12:15:22 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.19.64.2, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "10.19.64.2:5000" 2023-07-26 12:15:22.233334360 10.19.64.2 - - [26/Jul/2023:12:15:22 +0100] "GET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 12:15:22.527162273 [INFO] Preparing go2rtc config... 2023-07-26 12:15:22.727177322 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-07-26 12:15:23.348278290 [INFO] Service Frigate exited with code 1 (by signal 0) 2023-07-26 12:15:23.360410949 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) 2023-07-26 12:15:23.395323650 [INFO] Service NGINX exited with code 0 (by signal 0) config.yml 8.16 kB · 0 downloads You have a incorrect nesting: ffmpeg: hwaccel_args: preset-intel-qsv-h264 input_args: preset-rtsp-restream-low-latency output_args: record: preset-record-generic-audio-copy Also, you are defining as the generla input arg the "preset-rtsp-restream-low-latency" but then you define "preset-rtsp-restream" at the camera level. You can delete the one on the camera: cameras: garden: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/garden_camera input_args: preset-rtsp-restream roles: - record - detect 1 Quote Link to comment
MothyTim Posted July 26, 2023 Share Posted July 26, 2023 13 minutes ago, yayitazale said: You have a incorrect nesting: ffmpeg: hwaccel_args: preset-intel-qsv-h264 input_args: preset-rtsp-restream-low-latency output_args: record: preset-record-generic-audio-copy Also, you are defining as the generla input arg the "preset-rtsp-restream-low-latency" but then you define "preset-rtsp-restream" at the camera level. You can delete the one on the camera: cameras: garden: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/garden_camera input_args: preset-rtsp-restream roles: - record - detect Ok thanks, it seems to start now but no video? text error warn system array login s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service frigate-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started 2023-07-26 14:04:37.237186960 [2023-07-26 14:04:37] frigate.events INFO : Exiting event processor... 2023-07-26 14:04:37.237336666 [2023-07-26 14:04:37] peewee.sqliteq INFO : writer received shutdown request, exiting. 2023-07-26 14:04:37.363424991 [2023-07-26 14:04:37] watchdog.garden INFO : Terminating the existing ffmpeg process... 2023-07-26 14:04:37.363606904 [2023-07-26 14:04:37] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:04:38.106242071 [2023-07-26 14:04:38] frigate.video INFO : garden: exiting subprocess 2023-07-26 14:04:38.610580154 [2023-07-26 14:04:38] frigate.output INFO : exiting output process... 2023-07-26 14:04:39.772871076 [INFO] Service Frigate exited with code 0 (by signal 0) 2023-07-26 14:04:39.774703307 exit OK 2023-07-26 14:04:39.779776206 [INFO] The go2rtc service exited with code 0 (by signal 0) 2023-07-26 14:04:44.391396692 [INFO] Preparing go2rtc config... 2023-07-26 14:04:44.391695179 [INFO] Starting Frigate... 2023-07-26 14:04:44.392108765 [INFO] Starting NGINX... 2023-07-26 14:04:44.573084091 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2023-07-26 14:04:44.602014979 [INFO] Starting go2rtc... 2023-07-26 14:04:44.691108723 14:04:44.691 INF go2rtc version 1.2.0 linux/amd64 2023-07-26 14:04:44.691318689 14:04:44.691 INF [api] listen addr=:1984 2023-07-26 14:04:44.691553194 14:04:44.691 INF [rtsp] listen addr=:8554 2023-07-26 14:04:44.691721525 14:04:44.691 INF [srtp] listen addr=:8443 2023-07-26 14:04:44.691897569 14:04:44.691 INF [webrtc] listen addr=:8555 2023-07-26 14:04:45.234227247 2023/07/26 14:04:45 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.19.64.2, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "10.19.64.2:5000" 2023-07-26 14:04:45.234284155 10.19.64.2 - - [26/Jul/2023:14:04:45 +0100] "GET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:45.236579481 [2023-07-26 14:04:45] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-07-26 14:04:45.261038558 [2023-07-26 14:04:45] peewee_migrate INFO : Starting migrations 2023-07-26 14:04:45.264231849 [2023-07-26 14:04:45] peewee_migrate INFO : There is nothing to migrate 2023-07-26 14:04:45.281407489 [2023-07-26 14:04:45] detector.coral INFO : Starting detection process: 578 2023-07-26 14:04:47.895672929 [2023-07-26 14:04:45] frigate.app INFO : Output process started: 580 2023-07-26 14:04:47.895748882 [2023-07-26 14:04:45] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-07-26 14:04:47.895844847 [2023-07-26 14:04:45] frigate.app INFO : Camera processor started for garden: 587 2023-07-26 14:04:47.895891692 [2023-07-26 14:04:45] frigate.app INFO : Capture process started for garden: 588 2023-07-26 14:04:47.898251146 [2023-07-26 14:04:47] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-07-26 14:04:50.247608605 [2023-07-26 14:04:50] frigate.util ERROR : Unable to poll intel GPU stats: Failed to initialize PMU! (Operation not permitted) 2023-07-26 14:04:50.247612478 2023-07-26 14:04:53.432538517 10.19.64.2 - - [26/Jul/2023:14:04:53 +0100] "GET /api/stats HTTP/1.1" 200 2350 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:54.391625798 [INFO] Starting go2rtc healthcheck service... 2023-07-26 14:05:01.419456965 10.19.64.2 - - [26/Jul/2023:14:05:01 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:05.321489373 [2023-07-26 14:05:05] watchdog.garden INFO : No frames received from garden in 20 seconds. Exiting ffmpeg... 2023-07-26 14:05:05.321561589 [2023-07-26 14:05:05] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:05:05.361204284 [2023-07-26 14:05:05] frigate.video ERROR : garden: Unable to read frames from ffmpeg process. 2023-07-26 14:05:05.361255931 [2023-07-26 14:05:05] frigate.video ERROR : garden: ffmpeg process is not running. exiting capture thread... 2023-07-26 14:05:09.463968091 10.19.64.2 - - [26/Jul/2023:14:05:09 +0100] "GET /api/stats HTTP/1.1" 200 2320 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:15.362735085 [2023-07-26 14:05:15] watchdog.garden ERROR : Ffmpeg process crashed unexpectedly for garden. 2023-07-26 14:05:15.362816156 [2023-07-26 14:05:15] watchdog.garden ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-07-26 14:05:15.362882375 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] video_get_buffer: image parameters invalid 2023-07-26 14:05:15.362936534 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] get_buffer() failed 2023-07-26 14:05:15.362985810 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Error while decoding stream #0:0: Invalid argument 2023-07-26 14:05:15.363027753 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Finishing stream 1:0 without any data written to it. 2023-07-26 14:05:17.419589443 10.19.64.2 - - [26/Jul/2023:14:05:17 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:25.427323740 10.19.64.2 - - [26/Jul/2023:14:05:25 +0100] "GET /api/stats HTTP/1.1" 200 2383 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" config.yml Quote Link to comment
dopeytree Posted July 26, 2023 Share Posted July 26, 2023 (edited) Anyone got a wyze camera? I've picked up a few and am trying to get them working but I need to change something in the config. I have rtsp working via a 'wyze docker bridge' but I think maybe it need some slightly different camera settings to my other wansview cameras. Any ideas? the wyze camera is the bottom 'garden' camera mqtt: enabled: false host: 192.168.22.212 port: 1883 # Optional: topic prefix (default: shown below) # WARNING: must be unique if you are running multiple instances topic_prefix: frigate # Optional: client id (default: shown below) # WARNING: must be unique if you are running multiple instances client_id: frigate # Optional: user user: homeassistant # Optional: password # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}. # eg. password: '{FRIGATE_MQTT_PASSWORD}' password: x # Optional: interval in seconds for publishing stats (default: shown below) stats_interval: 60 go2rtc: streams: barn_inside: - rtsp://pSrUq7TZ:[email protected]:554/live/ch0 house_front_door: - rtsp://EWLHSHKY:[email protected]:554/live/ch0 barn: - rtsp://MPG7QbYQ:[email protected]:554/live/ch0 ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: - -hwaccel - qsv - -qsv_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p detectors: coral: type: edgetpu device: usb cameras: house_front_door: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://EWLHSHKY:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/house_front_door?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 40 motion: mask: - 768,432,735,322,655,310,605,308,579,269,548,218,414,233,368,337,257,432 - 141,330,201,432,0,432,0,335,0,282,0,170,55,123,121,195,114,282 - 496,0,528,71,460,107,387,122,332,87,294,47,335,0 objects: track: - person - car - dog - cat - bird - bicycle - motorcycle - cell phone - backpack - suitcase - horse - skateboard - pizza filters: car: threshold: 0.7 min_area: 2000 max_area: 100000 person: threshold: 0.8 min_area: 2000 max_area: 100000 record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects barn_inside: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://pSrUq7TZ:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/barn_inside?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich filters: # masks sink wine glass: mask: - 768,432,517,432,492,54,634,46 cup: mask: - 768,432,517,432,492,54,634,46 plate: mask: - 768,432,517,432,492,54,634,46 fork: mask: - 768,432,517,432,492,54,634,46 knife: mask: - 768,432,517,432,492,54,634,46 spoon: mask: - 768,432,517,432,492,54,634,46 bowl: mask: - 768,432,517,432,492,54,634,46 record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects barn: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://MPG7QbYQ:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/barn?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects garden: # cam name snapshots: enabled: true ffmpeg: input_args: - -avoid_negative_ts - make_zero inputs: - path: rtsp://192.168.22.3:8554/wyze-cam-pan-v3 # SD Link input_args: preset-rtsp roles: - detect - path: rtsp://192.168.22.3:8554/wyze-cam-pan-v3 # HD Link input_args: preset-rtsp roles: - record detect: width: 1920 height: 1088 fps: 20 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects Edited July 26, 2023 by dopeytree Quote Link to comment
MothyTim Posted July 26, 2023 Share Posted July 26, 2023 8 hours ago, MothyTim said: Ok thanks, it seems to start now but no video? text error warn system array login s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service frigate-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started 2023-07-26 14:04:37.237186960 [2023-07-26 14:04:37] frigate.events INFO : Exiting event processor... 2023-07-26 14:04:37.237336666 [2023-07-26 14:04:37] peewee.sqliteq INFO : writer received shutdown request, exiting. 2023-07-26 14:04:37.363424991 [2023-07-26 14:04:37] watchdog.garden INFO : Terminating the existing ffmpeg process... 2023-07-26 14:04:37.363606904 [2023-07-26 14:04:37] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:04:38.106242071 [2023-07-26 14:04:38] frigate.video INFO : garden: exiting subprocess 2023-07-26 14:04:38.610580154 [2023-07-26 14:04:38] frigate.output INFO : exiting output process... 2023-07-26 14:04:39.772871076 [INFO] Service Frigate exited with code 0 (by signal 0) 2023-07-26 14:04:39.774703307 exit OK 2023-07-26 14:04:39.779776206 [INFO] The go2rtc service exited with code 0 (by signal 0) 2023-07-26 14:04:44.391396692 [INFO] Preparing go2rtc config... 2023-07-26 14:04:44.391695179 [INFO] Starting Frigate... 2023-07-26 14:04:44.392108765 [INFO] Starting NGINX... 2023-07-26 14:04:44.573084091 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2023-07-26 14:04:44.602014979 [INFO] Starting go2rtc... 2023-07-26 14:04:44.691108723 14:04:44.691 INF go2rtc version 1.2.0 linux/amd64 2023-07-26 14:04:44.691318689 14:04:44.691 INF [api] listen addr=:1984 2023-07-26 14:04:44.691553194 14:04:44.691 INF [rtsp] listen addr=:8554 2023-07-26 14:04:44.691721525 14:04:44.691 INF [srtp] listen addr=:8443 2023-07-26 14:04:44.691897569 14:04:44.691 INF [webrtc] listen addr=:8555 2023-07-26 14:04:45.234227247 2023/07/26 14:04:45 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.19.64.2, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "10.19.64.2:5000" 2023-07-26 14:04:45.234284155 10.19.64.2 - - [26/Jul/2023:14:04:45 +0100] "GET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:45.236579481 [2023-07-26 14:04:45] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-07-26 14:04:45.261038558 [2023-07-26 14:04:45] peewee_migrate INFO : Starting migrations 2023-07-26 14:04:45.264231849 [2023-07-26 14:04:45] peewee_migrate INFO : There is nothing to migrate 2023-07-26 14:04:45.281407489 [2023-07-26 14:04:45] detector.coral INFO : Starting detection process: 578 2023-07-26 14:04:47.895672929 [2023-07-26 14:04:45] frigate.app INFO : Output process started: 580 2023-07-26 14:04:47.895748882 [2023-07-26 14:04:45] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-07-26 14:04:47.895844847 [2023-07-26 14:04:45] frigate.app INFO : Camera processor started for garden: 587 2023-07-26 14:04:47.895891692 [2023-07-26 14:04:45] frigate.app INFO : Capture process started for garden: 588 2023-07-26 14:04:47.898251146 [2023-07-26 14:04:47] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-07-26 14:04:50.247608605 [2023-07-26 14:04:50] frigate.util ERROR : Unable to poll intel GPU stats: Failed to initialize PMU! (Operation not permitted) 2023-07-26 14:04:50.247612478 2023-07-26 14:04:53.432538517 10.19.64.2 - - [26/Jul/2023:14:04:53 +0100] "GET /api/stats HTTP/1.1" 200 2350 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:54.391625798 [INFO] Starting go2rtc healthcheck service... 2023-07-26 14:05:01.419456965 10.19.64.2 - - [26/Jul/2023:14:05:01 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:05.321489373 [2023-07-26 14:05:05] watchdog.garden INFO : No frames received from garden in 20 seconds. Exiting ffmpeg... 2023-07-26 14:05:05.321561589 [2023-07-26 14:05:05] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:05:05.361204284 [2023-07-26 14:05:05] frigate.video ERROR : garden: Unable to read frames from ffmpeg process. 2023-07-26 14:05:05.361255931 [2023-07-26 14:05:05] frigate.video ERROR : garden: ffmpeg process is not running. exiting capture thread... 2023-07-26 14:05:09.463968091 10.19.64.2 - - [26/Jul/2023:14:05:09 +0100] "GET /api/stats HTTP/1.1" 200 2320 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:15.362735085 [2023-07-26 14:05:15] watchdog.garden ERROR : Ffmpeg process crashed unexpectedly for garden. 2023-07-26 14:05:15.362816156 [2023-07-26 14:05:15] watchdog.garden ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-07-26 14:05:15.362882375 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] video_get_buffer: image parameters invalid 2023-07-26 14:05:15.362936534 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] get_buffer() failed 2023-07-26 14:05:15.362985810 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Error while decoding stream #0:0: Invalid argument 2023-07-26 14:05:15.363027753 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Finishing stream 1:0 without any data written to it. 2023-07-26 14:05:17.419589443 10.19.64.2 - - [26/Jul/2023:14:05:17 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:25.427323740 10.19.64.2 - - [26/Jul/2023:14:05:25 +0100] "GET /api/stats HTTP/1.1" 200 2383 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" config.yml 8.11 kB · 0 downloads Fixed by changing to preset-vaapi Thanks for your help! 1 Quote Link to comment
Necro Posted July 26, 2023 Share Posted July 26, 2023 Is there anyway outside of setting the container to privileged to get monitoring for iGPU/Intel? The CAP_PERFMON approach doesn't seem to work (per here https://docs.frigate.video/configuration/hardware_acceleration/ ) or I'm doing it wrong adding "--cap-add=CAP_PERFMON" into extra parameters. Quote Link to comment
yayitazale Posted July 27, 2023 Author Share Posted July 27, 2023 16 hours ago, dopeytree said: Anyone got a wyze camera? I've picked up a few and am trying to get them working but I need to change something in the config. I have rtsp working via a 'wyze docker bridge' but I think maybe it need some slightly different camera settings to my other wansview cameras. Any ideas? the wyze camera is the bottom 'garden' camera mqtt: enabled: false host: 192.168.22.212 port: 1883 # Optional: topic prefix (default: shown below) # WARNING: must be unique if you are running multiple instances topic_prefix: frigate # Optional: client id (default: shown below) # WARNING: must be unique if you are running multiple instances client_id: frigate # Optional: user user: homeassistant # Optional: password # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}. # eg. password: '{FRIGATE_MQTT_PASSWORD}' password: x # Optional: interval in seconds for publishing stats (default: shown below) stats_interval: 60 go2rtc: streams: barn_inside: - rtsp://pSrUq7TZ:[email protected]:554/live/ch0 house_front_door: - rtsp://EWLHSHKY:[email protected]:554/live/ch0 barn: - rtsp://MPG7QbYQ:[email protected]:554/live/ch0 ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: - -hwaccel - qsv - -qsv_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p detectors: coral: type: edgetpu device: usb cameras: house_front_door: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://EWLHSHKY:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/house_front_door?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 40 motion: mask: - 768,432,735,322,655,310,605,308,579,269,548,218,414,233,368,337,257,432 - 141,330,201,432,0,432,0,335,0,282,0,170,55,123,121,195,114,282 - 496,0,528,71,460,107,387,122,332,87,294,47,335,0 objects: track: - person - car - dog - cat - bird - bicycle - motorcycle - cell phone - backpack - suitcase - horse - skateboard - pizza filters: car: threshold: 0.7 min_area: 2000 max_area: 100000 person: threshold: 0.8 min_area: 2000 max_area: 100000 record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects barn_inside: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://pSrUq7TZ:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/barn_inside?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich filters: # masks sink wine glass: mask: - 768,432,517,432,492,54,634,46 cup: mask: - 768,432,517,432,492,54,634,46 plate: mask: - 768,432,517,432,492,54,634,46 fork: mask: - 768,432,517,432,492,54,634,46 knife: mask: - 768,432,517,432,492,54,634,46 spoon: mask: - 768,432,517,432,492,54,634,46 bowl: mask: - 768,432,517,432,492,54,634,46 record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects barn: # cam name snapshots: enabled: true ffmpeg: output_args: record: preset-record-generic-audio-aac hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://MPG7QbYQ:[email protected]:554/live/ch1 # SD Link input_args: preset-rtsp-generic roles: - detect - path: rtsp://192.168.22.2:8554/barn?mp4 # HD Link input_args: preset-rtsp-restream roles: - record detect: width: 768 height: 432 fps: 15 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects garden: # cam name snapshots: enabled: true ffmpeg: input_args: - -avoid_negative_ts - make_zero inputs: - path: rtsp://192.168.22.3:8554/wyze-cam-pan-v3 # SD Link input_args: preset-rtsp roles: - detect - path: rtsp://192.168.22.3:8554/wyze-cam-pan-v3 # HD Link input_args: preset-rtsp roles: - record detect: width: 1920 height: 1088 fps: 20 stationary: interval: 0 threshold: 50 objects: track: - person - cat - bird - cell phone - backpack - suitcase - wine glass # masked - cup # masked - plate # masked - fork # masked - knife # masked - spoon # masked - bowl # masked - banana - apple - sandwich record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects I think preset-rstp doesn't exists. You should use preset-rtsp-generic. Quote Link to comment
yayitazale Posted July 27, 2023 Author Share Posted July 27, 2023 7 hours ago, Necro said: Is there anyway outside of setting the container to privileged to get monitoring for iGPU/Intel? The CAP_PERFMON approach doesn't seem to work (per here https://docs.frigate.video/configuration/hardware_acceleration/ ) or I'm doing it wrong adding "--cap-add=CAP_PERFMON" into extra parameters. Maybe @ich777 you can help us here, is this supported by the docker version we have in unraid? Quote Link to comment
ich777 Posted July 27, 2023 Share Posted July 27, 2023 7 hours ago, Necro said: Is there anyway outside of setting the container to privileged to get monitoring for iGPU/Intel? 10 minutes ago, yayitazale said: Maybe @ich777 It should be enough to create a Device entry like this: But I have to say I'm not too sure about that since I don't know how they monitor the device. May I ask for what monitoring is needed? Have you tried yet to issue this command form a Unraid Terminal: echo 2 >/proc/sys/kernel/perf_event_paranoid and then add the cap: --cap-add=CAP_PERFMON to the container? If that doesn't work then try to set it to: echo 1 >/proc/sys/kernel/perf_event_paranoid (but I don't recommend to set it to such a low value) You have to restart the container after you change the values on Unraid itself. 1 Quote Link to comment
mikamap Posted July 29, 2023 Share Posted July 29, 2023 Maybe I'm doing somethin wrong but if it helps someone in the future, I'm posting this. I was trying to install frigate on my unraid but the docker was always failing to start. Something about getting the path . I'm not using Coral or GPU or anything like that for my current setup. But the docker was not able to start. So I blanked all the value that were written "Remove this if your not using it". And still the docker would not start and there was an error like "Cannot find path ." Then I realized that in the command line there was this --device='' --device='' So I started the docker directly from command line (Not sure if it's safe) without these --device and it worked. Quote Link to comment
mikamap Posted July 29, 2023 Share Posted July 29, 2023 Also, frigate expose endpoints to export video from specific time when you record 24/7 Like : http://FRIGATE_IP:5000/api/CAMERA/start/1690529400/end/1690533000/clip.mp4 But the /tmp/cache was never too big to generate the videos. So in my manual command line, I removed the tmpfs mount and added a volume to /tmp/cache and it now works fine. Thanks Quote Link to comment
DrSpaldo Posted July 31, 2023 Share Posted July 31, 2023 I've noticed that during my weekly docker/appdata backup it looks like Unraid cannot stop the Frigate container and/or gives OOM errors. Any ideas of what may lead to this or what I can do to prevent this from happening? Jul 30 11:44:01 SpaldoUnraid kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=f6bd84541f24695692d01c50b3d4f9190ec11f453d2e440fc68c2e13a3192478,mems_allowed=0,global_oom,task_memcg=/docker/f6bd84541f24695692d01c50b3d4f9190ec11f453d2e440fc68c2e13a3192478,task=frigate.capture,pid=378,uid=0 Jul 30 11:44:01 SpaldoUnraid kernel: Out of memory: Killed process 378 (frigate.capture) total-vm:33863704kB, anon-rss:31910812kB, file-rss:0kB, shmem-rss:504kB, UID:0 pgtables:62780kB oom_score_adj:0 Jul 30 11:44:02 SpaldoUnraid kernel: oom_reaper: reaped process 378 (frigate.capture), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB The above is some extracts from the syslog around the time that the machine was coming back to life after being frozen for a few hours. Of note, I could not connect to the Unraid machine via webgui or SSH. However, the MPV stream I have running from Frigate continued to work, regardless of issues I was having with connecting to Unraid itself... Quote Link to comment
yayitazale Posted August 1, 2023 Author Share Posted August 1, 2023 On 7/29/2023 at 4:07 AM, mikamap said: Maybe I'm doing somethin wrong but if it helps someone in the future, I'm posting this. I was trying to install frigate on my unraid but the docker was always failing to start. Something about getting the path . I'm not using Coral or GPU or anything like that for my current setup. But the docker was not able to start. So I blanked all the value that were written "Remove this if your not using it". And still the docker would not start and there was an error like "Cannot find path ." Then I realized that in the command line there was this --device='' --device='' So I started the docker directly from command line (Not sure if it's safe) without these --device and it worked. Remove means remove, not blank it. You should delete the entries using the "REMOVE" button. Quote Link to comment
yayitazale Posted August 1, 2023 Author Share Posted August 1, 2023 On 7/29/2023 at 4:09 AM, mikamap said: Also, frigate expose endpoints to export video from specific time when you record 24/7 Like : http://FRIGATE_IP:5000/api/CAMERA/start/1690529400/end/1690533000/clip.mp4 But the /tmp/cache was never too big to generate the videos. So in my manual command line, I removed the tmpfs mount and added a volume to /tmp/cache and it now works fine. Thanks You can change the size just changing the value of the tmpfs size: - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear target: /tmp/cache tmpfs: size: 1000000000 You have the explanation here: https://docs.frigate.video/frigate/installation#storage Quote Link to comment
yayitazale Posted August 1, 2023 Author Share Posted August 1, 2023 22 hours ago, DrSpaldo said: I've noticed that during my weekly docker/appdata backup it looks like Unraid cannot stop the Frigate container and/or gives OOM errors. Any ideas of what may lead to this or what I can do to prevent this from happening? Jul 30 11:44:01 SpaldoUnraid kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=f6bd84541f24695692d01c50b3d4f9190ec11f453d2e440fc68c2e13a3192478,mems_allowed=0,global_oom,task_memcg=/docker/f6bd84541f24695692d01c50b3d4f9190ec11f453d2e440fc68c2e13a3192478,task=frigate.capture,pid=378,uid=0 Jul 30 11:44:01 SpaldoUnraid kernel: Out of memory: Killed process 378 (frigate.capture) total-vm:33863704kB, anon-rss:31910812kB, file-rss:0kB, shmem-rss:504kB, UID:0 pgtables:62780kB oom_score_adj:0 Jul 30 11:44:02 SpaldoUnraid kernel: oom_reaper: reaped process 378 (frigate.capture), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB The above is some extracts from the syslog around the time that the machine was coming back to life after being frozen for a few hours. Of note, I could not connect to the Unraid machine via webgui or SSH. However, the MPV stream I have running from Frigate continued to work, regardless of issues I was having with connecting to Unraid itself... This are separated things. An OOM errors means you are out of memory. This issue is something happening since july to some people: https://github.com/blakeblackshear/frigate/issues/6731 https://github.com/blakeblackshear/frigate/issues/7018 https://github.com/blakeblackshear/frigate/issues/6560 There is a topic opened already as it looks something related to docker engine or hardware itself: Some possible fixes here: https://github.com/blakeblackshear/frigate/issues/6731#issuecomment-1583071981 1 Quote Link to comment
DrSpaldo Posted August 2, 2023 Share Posted August 2, 2023 13 hours ago, yayitazale said: This are separated things. An OOM errors means you are out of memory. This issue is something happening since july to some people: Some possible fixes here: https://github.com/blakeblackshear/frigate/issues/6731#issuecomment-1583071981 Thanks for the reply @yayitazale. I will try some of these changes on my system and see if it makes a difference. Quote Link to comment
NewDisplayName Posted August 9, 2023 Share Posted August 9, 2023 (edited) Hmm, im a bit lost. I saw the standard guide, but this doenst really apply to unraid?! Isnt there a guide for unraid + frigate? Do i need to install mqtt? Why isnt that included in the docker? I just want to have one camera rtsp which should only record when moving. I tried this: mqtt: enabled: false cameras: back: ffmpeg: inputs: - path: rtsp://XXX:[email protected]:1338/11/ roles: - detect detect: width: 1280 height: 720 and it keeps constant crashing Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 39, in get_single_node 2023-08-09 20:51:31.897105168 [INFO] Starting NGINX... if not self.check_event(StreamEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 171, in parse_document_start raise ParserError(None, None, yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>' in "<unicode string>", line 3, column 1: cameras: ^ It sounds like "cameras" is the problem, but thats literally the first example for a config file on their page...? Edited August 9, 2023 by nuhll Quote Link to comment
DarkKnight Posted August 9, 2023 Share Posted August 9, 2023 (edited) On 5/3/2023 at 9:47 AM, yayitazale said: No, you are not. In red all the ones you are not filling and they are still there: docker run -d --name='frigate' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="frigate" -e 'FRIGATE_RTSP_PASSWORD'='XXXXXX -e 'PLUS_API_KEY'='' -e 'LIBVA_DRIVER_NAME'='' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'NVIDIA_DRIVER_CAPABILITIES'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://192.168.0.2:5000/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png' -p '5000:5000/tcp' -p '8554:8554/tcp' -p '8555:8555/tcp' -p '8555:8555/udp' -p ':1984/tcp' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/frigate_data/':'/media/frigate':'rw' -v '':'/trt-models':'ro' -v '/etc/localtime':'/etc/localtime':'rw' --device='' --device='' --shm-size=5000mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' docker: bad format for path: . Can you show a screenshot of the template before launching it? It's not clear from the template instructions that you mean to literally 'REMOVE' those variables from the template instead of just removing the pre-populated value. That's not typical, at all, of being a requirement for a template to function. Wouldn't it make more sense just the leave the variables entirely out of the template and put in the instructions to add them if needed? At least then it would launch/run without giving some vague error message that leads to 30 minutes of looking for answers. At a bare minimum the instructions should be explicit that the entire variable needs to be removed from the template. Edited August 9, 2023 by DarkKnight Quote Link to comment
yayitazale Posted August 10, 2023 Author Share Posted August 10, 2023 20 hours ago, nuhll said: Hmm, im a bit lost. I saw the standard guide, but this doenst really apply to unraid?! Isnt there a guide for unraid + frigate? Do i need to install mqtt? Why isnt that included in the docker? I just want to have one camera rtsp which should only record when moving. I tried this: mqtt: enabled: false cameras: back: ffmpeg: inputs: - path: rtsp://XXX:[email protected]:1338/11/ roles: - detect detect: width: 1280 height: 720 and it keeps constant crashing Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 39, in get_single_node 2023-08-09 20:51:31.897105168 [INFO] Starting NGINX... if not self.check_event(StreamEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 171, in parse_document_start raise ParserError(None, None, yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>' in "<unicode string>", line 3, column 1: cameras: ^ It sounds like "cameras" is the problem, but thats literally the first example for a config file on their page...? The config docs apply to unraid. MQTT is not mandatory, you don't need it and it is not included as it is standard service that can be used to any other communication purposes so if you want to use it, you must install it separatelly. As you can read in the error log: yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>' in "<unicode string>", line 3, column 1: cameras: ^ In YAML lenguage the padding must be the correct one to work. You have a error in the padding at line 3. You can test any YAML code here, for example the first config of frigate to startup for the first time, then you shoul use the frigate internal config editor witch will tell you if you have any spelling/padding error before saving. Your config file shoul look like this, in the same way it is defined in the getting started doc: mqtt: enabled: false cameras: back: ffmpeg: inputs: - path: rtsp://XXX:[email protected]:1338/11/ roles: - detect detect: width: 1280 height: 720 The rest of the configuration docs applies to unraid as it is indepentant of the host OS. Quote Link to comment
yayitazale Posted August 10, 2023 Author Share Posted August 10, 2023 16 hours ago, DarkKnight said: It's not clear from the template instructions that you mean to literally 'REMOVE' those variables from the template instead of just removing the pre-populated value. That's not typical, at all, of being a requirement for a template to function. Wouldn't it make more sense just the leave the variables entirely out of the template and put in the instructions to add them if needed? At least then it would launch/run without giving some vague error message that leads to 30 minutes of looking for answers. At a bare minimum the instructions should be explicit that the entire variable needs to be removed from the template. I tried to make the easiest and more complete template to fits everybodys needs and thats for sure is not something easy. 2 years ago I had the template only with the minimal entries and I can assure that it was much more confusing and much more people asked for help. Anyway, you can create your own template and publish it following the unraids community template creation guide and maintaining it by yourself. Quote Link to comment
NewDisplayName Posted August 10, 2023 Share Posted August 10, 2023 (edited) 1 hour ago, yayitazale said: I tried to make the easiest and more complete template to fits everybodys needs I found that straight forward because you explizit wrote "REMOVE THIS IF NOT NEEDED". Was clear to me, even as non english speaker. Quote In YAML lenguage the padding must be the correct one to work. You have a error in the padding at line 3. Its directly copied from the original config, and only edited with notepad++ who ever thought that padding would be a good idea........... And still, even with your config, errors... 2023-08-10 19:45:10.035521192 1 validation error for FrigateConfig 2023-08-10 19:45:10.035523378 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.035843523 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037033664 Traceback (most recent call last): 2023-08-10 19:45:10.037036489 File "/opt/frigate/frigate/app.py", line 351, in start 2023-08-10 19:45:10.037038031 self.init_config() 2023-08-10 19:45:10.037041198 File "/opt/frigate/frigate/app.py", line 80, in init_config 2023-08-10 19:45:10.037043098 user_config = FrigateConfig.parse_file(config_file) 2023-08-10 19:45:10.037044866 File "/opt/frigate/frigate/config.py", line 1078, in parse_file 2023-08-10 19:45:10.037057005 return cls.parse_obj(config) 2023-08-10 19:45:10.037058333 File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj 2023-08-10 19:45:10.037060270 File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__ 2023-08-10 19:45:10.037062454 pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig 2023-08-10 19:45:10.037063890 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.037065265 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037902506 2023-08-10 19:45:10.038198131 ************************************************************* 2023-08-10 19:45:10.038475954 *** End Config Validation Errors *** I have no problem googling problems and searching for myself, but oh god why he not just create a standard config, whcih you can fill via GUI... i even googled "extra fields not permitted" but no usefull results... Edited August 10, 2023 by nuhll Quote Link to comment
yayitazale Posted August 11, 2023 Author Share Posted August 11, 2023 21 hours ago, nuhll said: I found that straight forward because you explizit wrote "REMOVE THIS IF NOT NEEDED". Was clear to me, even as non english speaker. Its directly copied from the original config, and only edited with notepad++ who ever thought that padding would be a good idea........... And still, even with your config, errors... 2023-08-10 19:45:10.035521192 1 validation error for FrigateConfig 2023-08-10 19:45:10.035523378 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.035843523 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037033664 Traceback (most recent call last): 2023-08-10 19:45:10.037036489 File "/opt/frigate/frigate/app.py", line 351, in start 2023-08-10 19:45:10.037038031 self.init_config() 2023-08-10 19:45:10.037041198 File "/opt/frigate/frigate/app.py", line 80, in init_config 2023-08-10 19:45:10.037043098 user_config = FrigateConfig.parse_file(config_file) 2023-08-10 19:45:10.037044866 File "/opt/frigate/frigate/config.py", line 1078, in parse_file 2023-08-10 19:45:10.037057005 return cls.parse_obj(config) 2023-08-10 19:45:10.037058333 File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj 2023-08-10 19:45:10.037060270 File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__ 2023-08-10 19:45:10.037062454 pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig 2023-08-10 19:45:10.037063890 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.037065265 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037902506 2023-08-10 19:45:10.038198131 ************************************************************* 2023-08-10 19:45:10.038475954 *** End Config Validation Errors *** I have no problem googling problems and searching for myself, but oh god why he not just create a standard config, whcih you can fill via GUI... i even googled "extra fields not permitted" but no usefull results... Sorry my bad. Pasting here is not the best way so there you have attached the file. Hope you can at least startup frigate for the first time but as you can see, this is not a easy software to config and make running. I'm not a developer, I just maintain the unraid template so don't blame me.I'm not the main dev, I just maintain the unraid template so don't blame me. config.yml Quote Link to comment
NewDisplayName Posted August 13, 2023 Share Posted August 13, 2023 (edited) I know! Im not talking to you, just getting it off my mind, because i cant understand such devs. It still doesnt want to startup... I dont get it. Just to be sure, my TRT folder is empty, is that normal? My file is called config.yml, is that right? -08-13 12:27:27.525611633 ************************************************************* 2023-08-13 12:27:27.525722961 *** Your config file is not valid! *** -snip- I fixed it... There were 2 empty spaces missing infront of "back". This whole configuration marathon is unbelievable (useless) complicated. Im currently tryin to get my NVIDIA in it, lets see how that goes. Edited August 13, 2023 by nuhll Quote Link to comment
yayitazale Posted August 13, 2023 Author Share Posted August 13, 2023 1 hour ago, nuhll said: I know! Im not talking to you, just getting it off my mind, because i cant understand such devs. It still doesnt want to startup... I dont get it. Just to be sure, my TRT folder is empty, is that normal? My file is called config.yml, is that right? -08-13 12:27:27.525611633 ************************************************************* 2023-08-13 12:27:27.525722961 *** Your config file is not valid! *** -snip- I fixed it... There were 2 empty spaces missing infront of "back". This whole configuration marathon is unbelievable (useless) complicated. Im currently tryin to get my NVIDIA in it, lets see how that goes. Sorry for sure I'm not doing it on purpose, I also made a mistake in the padding LOL. Here ou have again the file. config.yml Quote Link to comment
NewDisplayName Posted August 13, 2023 Share Posted August 13, 2023 (edited) Im good, thanks to your starting help i was able to figure it out, even got detection working and recording... not sure about the retention but ill see how it goes and change it like i need to. Something very important was missing tho, ive selected frigate and nvidia docker, but it was missing --runtime=nvidia, which should be set, when you selecting the docker with the nvidia. But im not sure if you can change that in the template, but atleast i would add it somewhere in help so others dont have problems with it. Later ill post my config for others to use. Edited August 13, 2023 by nuhll Quote Link to comment
yayitazale Posted August 13, 2023 Author Share Posted August 13, 2023 7 minutes ago, nuhll said: Im good, thanks to your starting help i was able to figure it out, even got detection working and recording... not sure about the retention but ill see how it goes and change it like i need to. Something very important was missing tho, ive selected frigate and nvidia docker, but it was missing --runtime=nvidia, which should be set, when you selecting the docker with the nvidia. But im not sure if you can change that in the template, but atleast i would add it somewhere in help so others dont have problems with it. Later ill post my config for others to use. The template is the same for both versions, it just changes the tag of the dockers build. It is already in the installing instructions of the template. Quote Link to comment
Recommended Posts
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.