[Config Support]: #13154
-
Describe the problem you are having2024-08-18 04:28:24.683023128 ************************************************************* Version14 Frigate config filemqtt:
host: 192.168.1.253
port: 1883
topic_prefix: frigate
client_id: frigate
user: homeass
password: homeass
stats_interval: 60
#detectors: #
# coral:
# type: edgetpu
# device: usb
detectors:
coral1:
type: edgetpu
device: usb:0
coral2:
type: edgetpu
device: usb:1
######################################################################################################
# Optional: birdseye configuration
birdseye:
# Optional: Enable birdseye view (default: shown below)
enabled: false
# Optional: Width of the output resolution (default: shown below)
width: 1280
# width: 704
# Optional: Height of the output resolution (default: shown below)
height: 720
# height: 576
# Optional: Encoding quality of the mpeg1 feed (default: shown below)
# 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
quality: 15
# Optional: Mode of the view. Available options are: objects, motion, and continuous
# objects - cameras are included if they have had a tracked object within the last 30 seconds
# motion - cameras are included if motion was detected in the last 30 seconds
# continuous - all cameras are included always
mode: continuous
# Optional: birdseye configuration ( this is not in use )
#birdseye:
# Optional: Enable birdseye view (default: shown below)
# enabled: True
# Optional: Width of the output resolution (default: shown below)
# width: 352
# Optional: Height of the output resolution (default: shown below)
# height: 288
# Optional: Encoding quality of the mpeg1 feed (default: shown below)
# 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
# quality: 1
# Optional: Mode of the view. Available options are: objects, motion, and continuous
# objects - cameras are included if they have had a tracked object within the last 30 seconds
# motion - cameras are included if motion was detected in the last 30 seconds
# continuous - all cameras are included always
# mode: continuous
#
#############################################################################################################
#### 002 Front door Camera ####
002_Front_Door:
ffmpeg:
inputs:
# High Resolution Stream
- path: rtsp://admin:[email protected]:554/Streaming/Channels/201
roles:
- record
# Low Resolution Stream
- path: rtsp://admin:[email protected]:554/Streaming/Channels/202
roles:
- detect
detect:
width: 704
height: 576
fps: 6
record:
enabled: true
retain:
days: 1
mode: motion
events:
retain:
default: 1
snapshots:
enabled: true
timestamp: true
bounding_box: true
retain:
default: 1
motion:
mask:
- 400,36,512,41,517,0,0,0,0,159
zones:
zone_Front_Door01:
coordinates:
0,524,0,576,207,576,409,576,525,482,584,337,704,291,704,0,516,57,440,59,175,141,112,147,0,228
# zone_Front_YARD ALL:
# coordinates: 0,524,0,576,207,576,409,576,525,482,584,337,704,291,704,0,454,42,372,59,272,74,85,118,89,198,0,228
objects:
track:
- person
- dog
- cat
filters:
person:
min_area: 5000
max_area: 100000
threshold: 0.75
version: 0.14Relevant log outputs6-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 certsync-log: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
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
2024-08-18 04:14:37.249552445 [INFO] Preparing new go2rtc config...
2024-08-18 04:14:37.267885233 [INFO] Preparing Frigate...
2024-08-18 04:14:37.271322161 [INFO] Starting NGINX...
2024-08-18 04:14:37.303798044 [INFO] No TLS certificate found. Generating a self signed certificate...
2024-08-18 04:14:37.316376062 [INFO] Starting Frigate...
2024-08-18 04:14:37.447894401 [INFO] Got IP address from supervisor: 192.168.1.253
2024-08-18 04:14:37.642717449 [INFO] Got WebRTC port from supervisor: 8555
2024-08-18 04:14:39.082859537 [INFO] Starting go2rtc...
2024-08-18 04:14:39.437910315 12:14:39.436 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-08-18 04:14:39.437920298 12:14:39.437 INF config path=/dev/shm/go2rtc.yaml
2024-08-18 04:14:39.442156746 12:14:39.441 INF [rtsp] listen addr=:8554
2024-08-18 04:14:39.442164711 12:14:39.441 INF [webrtc] listen addr=:8555/tcp
2024-08-18 04:14:39.443187543 12:14:39.442 INF [api] listen addr=:1984
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2024-08-18 04:14:41.158887059 [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-08-18 04:14:41.468517894 127.0.0.1 - - [18/Aug/2024:12:14:41 +0800] "" 400 0 "-" "-" "-"
2024-08-18 04:14:42.144922056 2024/08/18 12:14:42 [error] 176#176: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-08-18 04:14:42.145309697 2024/08/18 12:14:42 [error] 176#176: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2024-08-18 04:14:42.956502800 [2024-08-18 12:14:42] frigate.app INFO : Starting Frigate (0.14.0-da913d8)
2024-08-18 04:14:42.957425110 [2024-08-18 12:14:42] frigate.app INFO : Creating directory: /tmp/cache
2024-08-18 04:14:42.958259390 [2024-08-18 12:14:42] frigate.util.config INFO : Checking if frigate config needs migration...
2024-08-18 04:14:43.020864575 [2024-08-18 12:14:43] frigate.util.config INFO : frigate config does not need migration...
2024-08-18 04:14:43.052182296 *************************************************************
2024-08-18 04:14:43.052189417 *************************************************************
2024-08-18 04:14:43.052197657 *** Your config file is not valid! ***
2024-08-18 04:14:43.052202415 *** Please check the docs at ***
2024-08-18 04:14:43.052955421 *** https://docs.frigate.video/configuration/index ***
2024-08-18 04:14:43.052964803 *************************************************************
2024-08-18 04:14:43.052967579 *************************************************************
2024-08-18 04:14:43.052970136 *** Config Validation Errors ***
2024-08-18 04:14:43.052972507 *************************************************************
2024-08-18 04:14:43.053006863 birdseye.002_Front_Door: Extra inputs are not permitted
2024-08-18 04:14:43.053009676 cameras: Field required
2024-08-18 04:14:43.053012119 *************************************************************
2024-08-18 04:14:43.053015630 *** End Config Validation Errors ***
2024-08-18 04:14:43.053017960 *************************************************************
2024-08-18 04:14:44.510557754 [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 go2rtc-healthcheck: stopping
s6-rc: info: service certsync: stopping
2024-08-18 04:14:44.529921188 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-08-18 04:14:44.534339307 [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2024-08-18 04:14:44.569294332 [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
2024-08-18 04:14:44.578152741 exit with signal: terminated
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-08-18 04:14:44.588961600 [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 stoppedFrigate statsNo response Operating systemHassOS Install methodHassOS Addon Object DetectorCoral Any other information that may be helpfulHi Team I seem to get this error know I have changed nothing ! after version 14 2024-08-18 04:28:24.683023128 ************************************************************* extra input is confusing me Team , sorry I`m no coder ! Regards Maz |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
|
You are missing You should have this: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much Hawker217 , 1 coffee coming up for you .... I cant believe I missed that I feel so stupid ... :) just a quick one s6-rc: info: service legacy-services successfully started |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad it worked. The error you're seeing there isn't a concern - the internal api call is just unable to connect because Frigate hasn't fully started yet. Thanks for the coffee! ☕ |
Beta Was this translation helpful? Give feedback.
-
|
In 0.13.2 config value 2024-09-04 11:33:45.307707261 ************************************************************* |
Beta Was this translation helpful? Give feedback.
-
|
Can you add you add your frigate.yml inside here we may be able to help ! |
Beta Was this translation helpful? Give feedback.
-
|
also their is a good video from mostly Chris that explains some changes that need to be made before going to v0.14 |
Beta Was this translation helpful? Give feedback.
-
|
Only this: |
Beta Was this translation helpful? Give feedback.
-
|
Ok so I'm hoping you have set up MQTT as an addon to Home Assistant ( if not please do ) or look up Mostly Chris how to setup Frigate in Home Assistant ! also I added my frigate.yml config below that's how my setup is and it works ! Also are your cameras IP based if so then add them like I did below BUT you will need to know how to find the correct Address using RTSP sample : rtsp://user:[email protected]:554/Streaming/Channels/202 but this works for my IP cameras ( actually ) I'm lucky My NVR allows me to use its IP address to see all my analog cameras as IP based :) .... If not sure how to get RTSP address then grab a software called : ONVIF Device Manager made by Synesis which can sometimes find your cameras automatically or you add the IP in their to your NVR or IP Camera and it will provide how to RTSP fingers crossed :) see screenshot added Anyway I have added one of my cameras below and then you can see the next camera called: 003_Driveway: which will be similar as 002_Front_Door: but different IP address ! Ok its best I can do Mate unfortunately I'm no computer guy I just love frigate ! and spend hours working it out or asking here in GitHub, but honestly watch you tube videos first ! and research too ( you have to learn it its important to have basic knowledge how it works a little its a must ) best of luck ! To see if it's working you don't need to use from snapshots: onwards remove all from below snapshots: and test ! in stages ! Last but not least do you actually have a coral USB if not remove that too :)mqtt: detectors: cameras: 002 Front door Camera002_Front_Door: 003 Driveway Camera003_Driveway:
|
Beta Was this translation helpful? Give feedback.
-
|
You can use software called studio code Server its an addon in Home Assistant ! this will help with the correct spacing and setup :)
Also if you want to test the rtsp address you can use vlc media player |
Beta Was this translation helpful? Give feedback.
-
|
My setup:
The problem I'm describing above is reduced to having |
Beta Was this translation helpful? Give feedback.
-
|
Then Best you start another support as your issue is not similar to mine , mine was missing the Camera word only which I missed ... |
Beta Was this translation helpful? Give feedback.
You are missing
cameras:above your camera name002_Front_Door:You should have this: