Stuck on syntax -- #1207
Comments
|
You need to add the username and API key generated by the new update to your frigate rtsp address. Your new frigate config should look something like this: Also, make sure your code is properly formatted, frigate is super picky about that, and it's easier to read for everyone here :) on github you can insert a code block by wrapping it with 3 backticks ``` |
|
Dear Mr Arbigator 2024-05-17 16:46:55.894151547 [INFO] Preparing Frigate... |
Looks like you have a typo in your config And to answer your question, no, you should only have to change the address in the go2rtc section, as the ffmpeg stream is coming from frigate's built in go2rtc server. |
|
Dear Mr Arbigator, |
|
@awwbaker please try not to include your API key/id as those are part of your wyze credentials. I know it's a little confusing, but you need to use the random API Key from the bridge if you have WB_AUTH enabled, which you can find on the bottom of your bridge WebUI like this: 
and use that key instead of the api key from wyze: |
|
Still getting the connection refused error. I changed rtsp credentials to match the WB Api key. Any thoughts would be appreciated. Thank you, Anthony 2024-05-20 14:38:32.166506617 [INFO] Starting Frigate...
|
|
The bridge uses port 8544 by default, but I think you have it set to 554: Should be |
|
Mr mrlt8 |
|
Awesome! I'll go ahead and mark this issue as resolved, but feel free to open a new issue if you need any additional help. |
Everything worked great for months and months. I discovered API changes as of 1 May. Reinstalled using webui and setting required key & Id. I can view both of the streams in VLC using the below URLs so making it that far. Inspite of showing green check mark in editor, I am getting the below error. A push in right direction would be appreciated. Gratefully Anthony
2024-05-16 19:05:16.134515651 [2024-05-16 15:05:16] frigate.app INFO : Starting Frigate (0.13.2-6476f8a)
2024-05-16 19:05:16.134657842 [2024-05-16 15:05:16] frigate.app INFO : Creating directory: /tmp/cache
2024-05-16 19:05:16.155333657 *************************************************************
2024-05-16 19:05:16.155337274 *************************************************************
2024-05-16 19:05:16.155341791 *** Your config file is not valid! ***
2024-05-16 19:05:16.155344322 *** Please check the docs at ***
2024-05-16 19:05:16.155345820 *** https://docs.frigate.video/configuration/index ***
2024-05-16 19:05:16.155374952 *************************************************************
2024-05-16 19:05:16.155376506 *************************************************************
2024-05-16 19:05:16.155378367 *** Config Validation Errors ***
2024-05-16 19:05:16.155379837 *************************************************************
2024-05-16 19:05:16.155396901 1 validation error for FrigateConfig
2024-05-16 19:05:16.155398051 snapsots
2024-05-16 19:05:16.155399472 extra fields not permitted (type=value_error.extra)
2024-05-16 19:05:16.156446201 Traceback (most recent call last):
2024-05-16 19:05:16.156450037 File "/opt/frigate/frigate/app.py", line 645, in start
2024-05-16 19:05:16.156451615 self.init_config()
2024-05-16 19:05:16.156453414 File "/opt/frigate/frigate/app.py", line 112, in init_config
2024-05-16 19:05:16.156455166 user_config = FrigateConfig.parse_file(config_file)
2024-05-16 19:05:16.156456991 File "/opt/frigate/frigate/config.py", line 1346, in parse_file
2024-05-16 19:05:16.156458545 return cls.parse_obj(config)
2024-05-16 19:05:16.156460421 File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
2024-05-16 19:05:16.156462284 File "pydantic/main.py", line 341, in pydantic.main.BaseModel.init
2024-05-16 19:05:16.156464244 pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig
2024-05-16 19:05:16.156466680 snapsots
2024-05-16 19:05:16.156468461 extra fields not permitted (type=value_error.extra)
2024-05-16 19:05:16.156518741
2024-05-16 19:05:16.156520931 *************************************************************
2024-05-16 19:05:16.156540490 *** End Config Validation Errors ***
2024-05-16 19:05:16.156542155 *************************************************************
2024-05-16 19:05:17.394285118 [INFO] Service Frigate exited with code 1 (by signal 0)
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
2024-05-16 19:05:17.408039070 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-05-16 19:05:17.428031136 [INFO] Service NGINX exited with code 0 (by signal 0)
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
2024-05-16 19:05:17.431161569 exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-05-16 19:05:17.435882415 [INFO] The go2rtc service exited with code 0 (by signal 0)
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
`mqtt:
host: 192.168.4.23
user: mqtt_user
password: mqtt_user
detectors:
coral:
type: edgetpu
device: usb
go2rtc:
streams:
breezeway:
- rtsp://192.168.4.23:8554/breezeway
garage:
- rtsp://192.168.4.23:8554/garage
snapsots:
enabled: True
clean_copy: True
timestamp: True
Optional: draw bounding box on the snapshots (default: shown below)
bounding_box: True
retain:
# Required: Default retention days (default: shown below)
default: 1
# Optional: Per object retention days
objects:
cat: 1
dog: 1
person: 1
detect:
enabled: True
width: 1280
height: 720
fps: 5
#objects:
#track:
#- person
#- cat
#- bird
#- dog
ffmpeg:
hwaccel_args: preset-vaapi
hwaccel_args: -hwaccel_output_format qsv -c:v h264_qsv
output_args:
preset-record-generic-audio-copy
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # -an
record:
enabled: True
retain:
days: 1
mode: motion
events:
retain:
default: 1
mode: active_objects
cameras:
front_door_main:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_door_main
roles:
- record
- rtmp
front_door_sub:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_door_sub
roles:
- detect
objects:
track:
- cat
- dog
- person
zones:
alienzone:
coordinates: 462,720,972,720,738,535,455,552
breezeway:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/breezeway
roles:
- record
- rtmp
- detect
objects:
track:
- cat
- dog
- person
zones:
deerzone:
coordinates: 407,720,0,720,0,468,412,193,476,191
garage:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/garage
roles:
- record
- rtmp
- detect
objects:
track:
- cat
- dog
- person
`
The text was updated successfully, but these errors were encountered: