HomeAssistant & CCTV setup

banie01

Folks I've been beavering away with setting up new IP cameras around the house and the plan is/was to set up motion record to my NAS.
I'm banging my head against a wall at this point though.
I can view the camera feeds within HA and they appear as cards within my HA dash.
Where I'm falling down is, getting them to appear in Frigate or Motioneye.

Current camera setup is 4 x Simicam 4K poe cameras and 1 reolink doorbell. These cameras are all viewable within their own apps, via VLC and appear as cards on my dash.
Where I'm falling down, is, I think, that my .yaml is flawed.
I have a folder on my NAS setup and it is showing as my "network storage" within my Home Assistant green.
When I install Frigate, it repeatedly fails to start.
When I try motioneye, it hangs on adding a camera.

Any tips on what to try next?

sundodger5

What does the frigate log file say?

banie01

https://www.boards.ie/discussion/comment/122314630#Comment_122314630

I cannot believe I forgot to check the logs 🤦‍♀️ It's the only way to actually know what went wrong.

It's my config that's causing the problem. I'll spend a bit more time reading the docs and see if I can get it running.

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 frigate-log successfully started
s6-rc: info: service nginx-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
2024-06-28 14:56:35.572865820  [INFO] Preparing Frigate...
2024-06-28 14:56:35.581035991  [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2024-06-28 14:56:36.248783824  [INFO] Preparing new go2rtc config...
2024-06-28 14:56:36.270272377  [INFO] Starting Frigate...
2024-06-28 14:56:36.799012099  [INFO] Got IP address from supervisor: 192.168.0.245
2024-06-28 14:56:37.329651739  [INFO] Got WebRTC port from supervisor: 8555
2024-06-28 14:56:38.917062654  [INFO] Starting go2rtc...
2024-06-28 14:56:39.090519532  15:56:39.090 INF go2rtc version 1.8.4 linux/arm64
2024-06-28 14:56:39.092888450  15:56:39.092 INF [api] listen addr=:1984
2024-06-28 14:56:39.092903617  15:56:39.092 INF [rtsp] listen addr=:8554
2024-06-28 14:56:39.093960034  15:56:39.093 INF [webrtc] listen addr=:8555
2024-06-28 14:56:45.290262774  [2024-06-28 15:56:45] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-06-28 14:56:45.291103650  [2024-06-28 15:56:45] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-06-28 14:56:45.331399170  *************************************************************
2024-06-28 14:56:45.331414045  *************************************************************
2024-06-28 14:56:45.331428336  ***    Your config file is not valid!                     ***
2024-06-28 14:56:45.331497170  ***    Please check the docs at                           ***
2024-06-28 14:56:45.331502420  ***    https://docs.frigate.video/configuration/index     ***
2024-06-28 14:56:45.331505628  *************************************************************
2024-06-28 14:56:45.331508253  *************************************************************
2024-06-28 14:56:45.331512920  ***    Config Validation Errors                           ***
2024-06-28 14:56:45.331634545  *************************************************************
2024-06-28 14:56:45.331640087  'XPY@7O&ll6e7O'
2024-06-28 14:56:45.335064547  Traceback (most recent call last):
2024-06-28 14:56:45.335080005    File "/opt/frigate/frigate/app.py", line 645, in start
2024-06-28 14:56:45.335082630      self.init_config()
2024-06-28 14:56:45.335085547    File "/opt/frigate/frigate/app.py", line 113, in init_config
2024-06-28 14:56:45.335088172      self.config = user_config.runtime_config(self.plus_api)
2024-06-28 14:56:45.335091088    File "/opt/frigate/frigate/config.py", line 1200, in runtime_config
2024-06-28 14:56:45.335093713      input.path = input.path.format(**FRIGATE_ENV_VARS)
2024-06-28 14:56:45.335096338  KeyError: 'XPY@7O&ll6e7O'
2024-06-28 14:56:45.335108880  
2024-06-28 14:56:45.335112380  *************************************************************
2024-06-28 14:56:45.335115588  ***    End Config Validation Errors                       ***
2024-06-28 14:56:45.335118505  *************************************************************
2024-06-28 14:56:45.564057993  [INFO] Starting go2rtc healthcheck service...
2024-06-28 14:56:47.499362074  [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-06-28 14:56:47.548414598  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-06-28 14:56:47.728372437  [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-06-28 14:56:47.741195860  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-06-28 14:56:47.759601202  [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

sundodger5

This will not fix all things but can sonetimes help.try AI.

Throw your config into phind.com.

I seem to recall talk on the HA forums of a specific AI for HA but i haven't found it yet.

As a side project once you get frigate up and running you can get AI on the camera snapshots to describe what they see and send a message to your phone.

banie01

https://www.boards.ie/discussion/comment/122316810#Comment_122316810

Thank you for this. I'd never heard of that site before and it's very handy.

On the camera and AI descriptors, I have seen a little bit on that and it's fascinating. Some talk that one may need a TPU to take full advantage though.

sundodger5

I am running my HA on a pi4 so it definitely needed a TPU even for frigate. Not big money though i added the coral got it from RS online 60 quid ish i think.

banie01

I'm completely stuck at this point. MQTT is up and running. I added a frigate folder to /media via ssh and verified its there vi "ls"
Frigate keeps failing (log below) with a "config.yml" not found.
Do I ditch my frigate.yaml and just copy everything into the config.yml?

At this point I feel like I'm chasing my tail and should probably step away for a day or 2 because I'm missing something quite simple (no doubt)

The cameras are working, they are present as devices in my Home Assistant device list, and I can view a live feed via my HA overview screen, just no recordings.
My frigate.yaml
mqtt:

enabled: true

host: 192.168.0.245
cameras:

Front Door: # <---

enabled: true

ffmpeg:

inputs:

- path: rtsp://admin:XPY@7O&ll6e7O@192.168.0.166:554/rtsp

roles:

- detect

- record

Front of House: #

enabled: true

ffmpeg:

inputs:

- path: rtsp://admin:123456@192.168.0.83:554/rtsp

roles:

- detect

- record

Back Garden 1: #

enabled: true

ffmpeg:

inputs:

- path: rtsp://admin:123456@192.168.0.77:554/rtsp

roles:

- detect

- record

Back Garden 2: #

enabled: true

ffmpeg:

inputs:

- path: rtsp://admin:123456@192.168.0.66:554/rtsp

roles:

- detect

Side of House: # <--- this will be changed to your actual camera later

enabled: true

ffmpeg:

inputs:

- path: rtsp://admin:123456@192.168.0.54:554/rtsp

roles:

- detect

- record

MQTT Log

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[12:42:56] INFO: Starting NGINX for authentication handling...

s6-rc: info: service legacy-services successfully started

[12:42:57] INFO: Starting mosquitto MQTT broker...

2024-07-02 12:42:58: Warning: Mosquitto should not be run as root/administrator.

2024-07-02 12:42:58: mosquitto version 2.0.18 starting

2024-07-02 12:42:58: Config loaded from /etc/mosquitto/mosquitto.conf.

2024-07-02 12:42:58: Loading plugin: /usr/share/mosquitto/go-auth.so

2024-07-02 12:42:58:  ├── Username/password checking enabled.

2024-07-02 12:42:58:  ├── TLS-PSK checking enabled.

2024-07-02 12:42:58:  └── Extended authentication not enabled.

2024-07-02 12:42:58: Opening ipv4 listen socket on port 1883.

2024-07-02 12:42:58: Opening ipv6 listen socket on port 1883.

2024-07-02 12:42:58: Opening websockets listen socket on port 1884.

2024-07-02 12:42:58: mosquitto version 2.0.18 running

2024-07-02 12:43:06: New connection from ::1:59966 on port 1883.

2024-07-02 12:43:06: Client <unknown> disconnected due to protocol error.

[12:43:09] INFO: Successfully send discovery information to Home Assistant.

[12:43:12] INFO: Successfully send service information to the Supervisor.

2024-07-02 12:48:19: New connection from 172.30.32.2:43172 on port 1883.

2024-07-02 12:48:19: Client <unknown> closed its connection.

2024-07-02 12:50:19: New connection from 172.30.32.2:36168 on port 1883.

2024-07-02 12:50:19: Client <unknown> closed its connection.

2024-07-02 12:52:19: New connection from 172.30.32.2:41336 on port 1883.

2024-07-02 12:52:19: Client <unknown> closed its connection.

2024-07-02 12:54:19: New connection from 172.30.32.2:37266 on port 1883.

2024-07-02 12:54:19: Client <unknown> closed its connection.

2024-07-02 12:56:19: New connection from 172.30.32.2:47386 on port 1883.

2024-07-02 12:56:19: Client <unknown> closed its connection.

2024-07-02 12:57:59: New connection from 172.30.32.1:57463 on port 1883.

2024-07-02 12:57:59: New client connected from 172.30.32.1:57463 as 1xLxbsuQ0wa8EelarhcxUI (p2, c1, k60, u'homeassistant').

2024-07-02 12:58:00: Client 1xLxbsuQ0wa8EelarhcxUI disconnected.

2024-07-02 12:58:00: New connection from 172.30.32.1:37107 on port 1883.

2024-07-02 12:58:00: New client connected from 172.30.32.1:37107 as 7oajTEq3SJJZ0EDbm5KHX7 (p2, c1, k60, u'homeassistant').

2024-07-02 12:58:19: New connection from 172.30.32.2:46438 on port 1883.

2024-07-02 12:58:19: Client <unknown> closed its connection.

2024-07-02 13:00:19: New connection from 172.30.32.2:37396 on port 1883.

2024-07-02 13:00:19: Client <unknown> closed its connection.

2024-07-02 13:02:19: New connection from 172.30.32.2:39754 on port 1883.

2024-07-02 13:02:19: Client <unknown> closed its connection.

2024-07-02 13:04:19: New connection from 172.30.32.2:39688 on port 1883.

2024-07-02 13:04:19: Client <unknown> closed its connection.

2024-07-02 13:06:19: New connection from 172.30.32.2:40702 on port 1883.

2024-07-02 13:06:19: Client <unknown> closed its connection.

2024-07-02 13:08:19: New connection from 172.30.32.2:41748 on port 1883.

2024-07-02 13:08:19: Client <unknown> closed its connection.

2024-07-02 13:08:50: Client 7oajTEq3SJJZ0EDbm5KHX7 closed its connection.

s6-rc: info: service legacy-services: stopping

2024-07-02 13:09:12: mosquitto version 2.0.18 terminating

2024-07-02 13:09:12: Saving in-memory database to /data//mosquitto.db.

[12:09:12] INFO: Service restart after closing

[12:09:12] INFO: Service restart after closing

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

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-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/mosquitto.sh

[13:16:47] INFO: SSL is not enabled

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[13:16:55] INFO: Starting NGINX for authentication handling...

s6-rc: info: service legacy-services successfully started

[13:16:56] INFO: Starting mosquitto MQTT broker...

2024-07-02 13:16:57: Warning: Mosquitto should not be run as root/administrator.

2024-07-02 13:16:57: mosquitto version 2.0.18 starting

2024-07-02 13:16:57: Config loaded from /etc/mosquitto/mosquitto.conf.

2024-07-02 13:16:57: Loading plugin: /usr/share/mosquitto/go-auth.so

2024-07-02 13:16:57:  ├── Username/password checking enabled.

2024-07-02 13:16:57:  ├── TLS-PSK checking enabled.

2024-07-02 13:16:57:  └── Extended authentication not enabled.

2024-07-02 13:16:57: Opening ipv4 listen socket on port 1883.

2024-07-02 13:16:57: Opening ipv6 listen socket on port 1883.

2024-07-02 13:16:57: Opening websockets listen socket on port 1884.

2024-07-02 13:16:57: mosquitto version 2.0.18 running

2024-07-02 13:17:04: New connection from ::1:50950 on port 1883.

2024-07-02 13:17:04: Client <unknown> disconnected due to protocol error.

[13:17:07] INFO: Successfully send discovery information to Home Assistant.

[13:17:09] INFO: Successfully send service information to the Supervisor.

2024-07-02 13:19:47: New connection from 172.30.32.1:42285 on port 1883.

2024-07-02 13:19:47: New client connected from 172.30.32.1:42285 as 6TeGi1eFKCm5CHFHAkdNGW (p2, c1, k60, u'homeassistant').

2024-07-02 13:21:58: New connection from 172.30.32.2:48190 on port 1883.

2024-07-02 13:21:58: Client <unknown> closed its connection.

Frigate Log

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

2024-07-02 12:01:40.240571939  [INFO] Preparing Frigate...

2024-07-02 12:01:40.240969191  [ERROR] Frigate config file not found

s6-rc: info: service frigate successfully started

s6-rc: info: service nginx: starting

s6-rc: info: service go2rtc-healthcheck successfully started

2024-07-02 12:01:40.339510404  [INFO] Starting NGINX...

2024-07-02 12:01:40.359147538  [INFO] Service Frigate exited with code 1 (by signal 0)

s6-rc: info: service nginx successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

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-07-02 12:01:40.918147124  [INFO] Service NGINX exited with code 256 (by signal 15)

s6-rc: info: service nginx successfully stopped

s6-rc: info: service nginx-log: stopping

s6-rc: info: service frigate: stopping

2024-07-02 12:01:40.933149944  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)

s6-rc: info: service frigate successfully stopped

s6-rc: info: service frigate-log: stopping

s6-rc: info: service go2rtc-healthcheck successfully stopped

s6-rc: info: service go2rtc: stopping

s6-rc: info: service nginx-log successfully stopped

2024-07-02 12:01:41.159801092  [INFO] The go2rtc service exited with code 256 (by signal 15)

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 legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service s6rc-fdholder successfully stopped

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

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

2024-07-02 12:20:31.687695224  [INFO] Starting NGINX...

2024-07-02 12:20:31.687695224  [INFO] Preparing Frigate...

2024-07-02 12:20:32.229261207  [ERROR] Frigate config file not found

2024-07-02 12:20:32.229276665  [INFO] Service Frigate exited with code 1 (by signal 0)

2024-07-02 12:20:31.953461808  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)

2024-07-02 12:20:32.232785441  [INFO] The go2rtc service exited with code 256 (by signal 15)

s6-rc: info: service go2rtc successfully stopped

s6-rc: info: service go2rtc-log: stopping

s6-rc: info: service nginx-log successfully stopped

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

I'm starting to feel like I'm lost on this and any steer would be very, very appreciated.

sundodger5

Ok i am no expert and mine took a lot of hit and miss to get running.

My Frigate config is below maybe it will help you with ideas or tweak to suit your setup maybe?

Substiute username:password to your own values

mqtt:
enabled: true
host: core-mosquitto
port: 1883
user: mqtt-user
password: mqtt
topic_prefix: frigate
client_id: frigate
# if you want to decode a h264 stream
ffmpeg:
hwaccel_args: preset-rpi-64-h264
detectors:
coral:
type: edgetpu
device: usb

cameras:
Driveway:
enabled: true
ffmpeg:
inputs:
#- path: rtsp://username:password@192.168.1.170:554/1
# roles:
# - detect
- path: rtsp://username:password@192.168.1.170:554/0
roles:
- record
- detect
detect:
width: 1920
height: 1080
fps: 7
record:
enabled: true
retain:
days: 7
mode: motion
events:
retain:
default: 7
mode: motion
snapshots:
enabled: true
retain:
default: 7
zones:
zone_0:
coordinates: 1920,832,1920,499,886,482,987,307,911,290,663,240,538,281,314,362,0,486,0,763
motion:
threshold: 80
mask:
- 1920,0,1920,285,1540,104,1518,0,1213,0,714,212,446,310,0,488,0,0

outside:
enabled: true
ffmpeg:
inputs:
- path: rtsp://username:password@192.168.1.180:554/stream2
roles:
- detect
- path: rtsp://username:password@192.168.1.180:554/stream1
roles:
- record
detect:
width: 720
height: 480
fps: 7
record:
enabled: true
retain:
days: 7
mode: motion
events:
retain:
default: 7
mode: motion
snapshots:
enabled: true
retain:
default: 7
motion:
threshold: 50
mask:
- 263,22,0,23,0,0,265,0
# zones:
# zone_0:
#coordinates: 302,69,300,175,286,222,534,220,568,315,234,306,167,202,214,76
objects:
# Optional: list of objects to track from labelmap.txt (default: shown below)
track:
- person
- cat
- car
- cell phone
- dog
- horse
- sheep
- cow
filters:
car:
min_score: 0.5
person:
min_score: 0.6
database:
path: /config/frigate.db

banie01

Thanks for the share, I'll spend a bit more time over the weekend in the weeds.

In the meantime, I've setup motioneye to ensure that I at least have a record capability until I get Frigate nailed down.

meathenterpr

I this it is the password that is causing the issue (I hope you did not expose the actual password). the @ symbol is a reserved character. Try changing the password. Maybe stick to alpha-numberic combination .

banie01

https://www.boards.ie/discussion/comment/122440765#Comment_122440765

Thanks for the steer, the PW in my post & logs has been edited to generic. I will check to make sure I'm not using @ in any of the actual camera passwords and report back 👍