Jump to content

[SUPPORT] blakeblackshear - Frigate


Recommended Posts

11 minutes ago, ppaul said:

Hi,

I have in my unraid HA, Mqtt and Frigate running. And all work fine. I get the topic frigate/ in mqtt and I can manually add stuff from frigate via mqtt in HA, i.e.:

 # Frigate
  - unique_id: frigate_front_door_pd
    name: "Frigate front door Person Detected"
    topic: "frigate/front_door/person/snapshot" 

 

But I cannot figure out how to autmatically discover the frigate stuff in HA. I know I should install the frigate Integration but I don't know how. Please could someone help me figure this out? In Integrations it doesn't show.

 

You should use HACS to install it. https://github.com/blakeblackshear/frigate-hass-integration

 

Link to comment
2 hours ago, crunchynuts said:

Hi does anyone know if Frigate creates a share automatically at /mnt/user/frigate?

 

I don't have this media folder configured anywhere but it seems to require it for startup.

Tried renaming/removing but it doesnt start.

No. There are 2 folders that need to be bind to the unraid host and these are the corresponding suggested binding points that are presented as default in the template:

 

Frigate -> Unraid

/config -> /mnt/user/appdata/frigate

/media/frigate -> /mnt/user/Media/frigate

 

If you want to use another binding folders you should create it/them before using it.

Edited by yayitazale
Link to comment

So I have trying to set up this frigate container for some time now and it took me a while to figure out that it apparently keeps restarting within several seconds. (I thought i had a faulty config.yml because i just got the spinning wheel on the web ui and tried to mess around with it)

 

This is the error i get:

 

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 13, column 11:
        ffmpeg:
              ^
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-12-24 11:13:28.919764877    File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 133, in compose_mapping_node
2023-12-24 11:13:28.919765669      item_value = self.compose_node(node, item_key)
2023-12-24 11:13:28.919780186    File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node
2023-12-24 11:13:28.919781148      node = self.compose_mapping_node(anchor)
2023-12-24 11:13:28.919782120    File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node
2023-12-24 11:13:28.919783051      while not self.check_event(MappingEndEvent):
2023-12-24 11:13:28.919783933    File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event
2023-12-24 11:13:28.919784684      self.current_event = self.state()
2023-12-24 11:13:28.919785606    File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 428, in parse_block_mapping_key
2023-12-24 11:13:28.919807958      if self.check_token(KeyToken):
2023-12-24 11:13:28.919809081    File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 116, in check_token
2023-12-24 11:13:28.919809842      self.fetch_more_tokens()
2023-12-24 11:13:28.919810744    File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 223, in fetch_more_tokens
2023-12-24 11:13:28.919811645      return self.fetch_value()
2023-12-24 11:13:28.919812547    File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 577, in fetch_value
2023-12-24 11:13:28.919813288      raise ScannerError(None, None,
2023-12-24 11:13:28.919814080  yaml.scanner.ScannerError: mapping values are not allowed here
2023-12-24 11:13:28.919814851    in "<unicode string>", line 13, column 11:
2023-12-24 11:13:28.919815573          ffmpeg:
2023-12-24 11:13:28.919816244                ^
2023-12-24 11:13:28.919816885  
2023-12-24 11:13:28.919817687  *************************************************************
2023-12-24 11:13:28.919818498  ***    End Config Validation Errors                       ***
2023-12-24 11:13:28.919819310  *************************************************************
2023-12-24 11:13:29.277951226  [INFO] Preparing go2rtc config...
2023-12-24 11:13:29.535628713  [INFO] The go2rtc service exited with code 1 (by signal 0)
2023-12-24 11:13:30.100706110  [INFO] Service Frigate exited with code 1 (by signal 0)
2023-12-24 11:13:30.111917236  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2023-12-24 11:13:30.149506121  [INFO] Service NGINX exited with code 0 (by signal 0)

 

What did i do wrong?

 

 

EDIT: AHA! The name of the cam is not a mapping this was throwing me off!!

Edited by Zeze21
  • Like 1
Link to comment

I am trying to get started with the Tensorrt-models docker container and have set it up as below with the script,

have did the "chmod +x /mnt/user/appdata/trt-models/tensorrt_models.sh" and when running the container I get the error below:

 

/opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory
/opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success

 

image.thumb.png.ea3ab20b13d6931423d50f95b1e1fe6b.png

 

any ideas what I am doing wrong?

Link to comment
13 hours ago, Hellomynameisleo said:

I am trying to get started with the Tensorrt-models docker container and have set it up as below with the script,

have did the "chmod +x /mnt/user/appdata/trt-models/tensorrt_models.sh" and when running the container I get the error below:

 

/opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory
/opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success

 

image.thumb.png.ea3ab20b13d6931423d50f95b1e1fe6b.png

 

any ideas what I am doing wrong?

Do you have the /mnt/user/appdata/trt-models folder mapped already to frigate and frigate running? If yes, please stop frigate, run this container and then restar frigate.

Link to comment
2 hours ago, yayitazale said:

Do you have the /mnt/user/appdata/trt-models folder mapped already to frigate and frigate running? If yes, please stop frigate, run this container and then restar frigate.

Yes its mapped to frigate, I've stopped the frigate container and started the Tensorrt-models docker and it the same error that pops up. Is there something else I am missing?

 

image.thumb.png.b14e608cdb02e024a1f6eaa6763b0529.png

Link to comment
23 hours ago, Hellomynameisleo said:

Yes its mapped to frigate, I've stopped the frigate container and started the Tensorrt-models docker and it the same error that pops up. Is there something else I am missing?

 

image.thumb.png.b14e608cdb02e024a1f6eaa6763b0529.png

Maybe you have to download the sh again or try another path. Anyway, don't waste too much time on this, the next frigate versión witch will be released very soon will have the tensor model integrated inside the container, so what you are doing will be in vain. I suggest you to wait some weeks and use this feature in the frigate v13.

  • Like 1
Link to comment

Hello,
i was searching a while but didn't find the answer for my question...

I have a multi gpu setup. And wan't frigate to use the second gpu.

but it always uses the first one.

i have fount the part in the documentation but i don't know how to get this in unraid to work...

 

https://docs.frigate.video/configuration/hardware_acceleration/#docker-compose---nvidia-gpu

 

can someone point me in the right direction, to get this working?

 

edit:

 

of course i have set up all other setting in the docker section and the nvidia-plugin running...

59723622_Bildschirmfoto2024-01-03um14_52_46.png.590824b79d31950029069a276e79d9b4.png

1887785964_Bildschirmfoto2024-01-03um14_53_12.png.2e045c6a87c922f7e917d9d2ca007c33.png

 

This is the id of the second gpu...

 

Mit freundlichen Grüßen

Chris

Edited by cmeyer86
Link to comment
21 hours ago, cmeyer86 said:

Hello,
i was searching a while but didn't find the answer for my question...

I have a multi gpu setup. And wan't frigate to use the second gpu.

but it always uses the first one.

i have fount the part in the documentation but i don't know how to get this in unraid to work...

 

https://docs.frigate.video/configuration/hardware_acceleration/#docker-compose---nvidia-gpu

 

can someone point me in the right direction, to get this working?

 

edit:

 

of course i have set up all other setting in the docker section and the nvidia-plugin running...

59723622_Bildschirmfoto2024-01-03um14_52_46.png.590824b79d31950029069a276e79d9b4.png

1887785964_Bildschirmfoto2024-01-03um14_53_12.png.2e045c6a87c922f7e917d9d2ca007c33.png

 

This is the id of the second gpu...

 

Mit freundlichen Grüßen

Chris

No idea, please ask on github as it looks a develop error, I can't help you, you are doing it in the right way.

Link to comment

Trying to install that tensort model.  Reading the instructions it says to place the tensorrt_models.sh script inside the /appdata/tensort directory.

 

Disregard.  Just saw yayitazale's post about the next version of Frigate coming out.

Edited by CoZ
new information obtained
  • Like 1
Link to comment

Why if I use my camera's substream to detect, and set the


 

detect:

  width: 640

  height: 480

  fps: 10

 

Frigate dashboard only displays that feed?  Even though I have the 2k Resolution set up for “record” and the sub stream for detect, Frigate is only displaying the sub in live view.  (or, I'm assuming it's the sub because of it's squished down view)

 

If I change the above code to, for instance, 720p then my thumbnail of the video feeds and the video feed itself doesn't look as “squishy” as the 640x480. 

 

I thought perhaps I had gotten my sub and main streams reversed, but I have checked and re-checked them and they are correct. 

 

If my substream is only 640x480 but I set it to 720p just to get a clearer live view, am I now not upscaling my detect stream, using more resources than I need to be?

 

 

Link to comment
5 hours ago, CoZ said:

Why if I use my camera's substream to detect, and set the


 

detect:

  width: 640

  height: 480

  fps: 10

 

Frigate dashboard only displays that feed?  Even though I have the 2k Resolution set up for “record” and the sub stream for detect, Frigate is only displaying the sub in live view.  (or, I'm assuming it's the sub because of it's squished down view)

 

If I change the above code to, for instance, 720p then my thumbnail of the video feeds and the video feed itself doesn't look as “squishy” as the 640x480. 

 

I thought perhaps I had gotten my sub and main streams reversed, but I have checked and re-checked them and they are correct. 

 

If my substream is only 640x480 but I set it to 720p just to get a clearer live view, am I now not upscaling my detect stream, using more resources than I need to be?

 

 

Did you set up the corresponding input path and roles on each camera?

 

https://docs.frigate.video/configuration/cameras#setting-up-camera-inputs

 

If you want to use two different stream inputs one for detection and one for recording you should have something like the example of the link, with one role per stream path.

 

PD: the stream feed of the frontend is indeed the one of the detect role. If you have the chance to use a hwaccel card I suggest you to use the restreaming ability to create a internal feed of the main high res stream and use it for both record and detect, you shouldn't see a big difference of CPU usage.

Edited by yayitazale
Link to comment
6 minutes ago, yayitazale said:

Did you set up the corresponding input path and roles on each camera?

 

https://docs.frigate.video/configuration/cameras#setting-up-camera-inputs

 

If you want to use two different stream inputs one for detection and one for recording you should have something like the example of the link, with one role per stream path.

 

 

Yes Sir, I believe I set it up properly – unless of course, like usual, I screwed something up.  This is a lot to take in and one wrong indent along the way and POOF everything crashes. lol.

 

go2rtc:
  streams:
    Rear_Deck:
      - rtsp://admin:[email protected]:554/h264Preview_01_main
    Rear_Deck_sub:
      - rtsp://admin:[email protected]:554/h264Preview_01_sub
    Garage_Camera:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    Garage_Camera_sub:
     - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1

ffmpeg:
  hwaccel_args: preset-nvidia-h265

rtmp:
  enabled: False 




cameras:
############## REAR DECK ##################
  Rear_Deck:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/Rear_Deck
          input_args: preset-rtsp-restream
          roles:
            - detect
        - path: rtsp://127.0.0.1:8554/Rear_Deck_sub
          input_args: preset-rtsp-restream
          roles:
            - record

 

Link to comment
6 minutes ago, CoZ said:

 

 

Yes Sir, I believe I set it up properly – unless of course, like usual, I screwed something up.  This is a lot to take in and one wrong indent along the way and POOF everything crashes. lol.

 

go2rtc:
  streams:
    Rear_Deck:
      - rtsp://admin:[email protected]:554/h264Preview_01_main
    Rear_Deck_sub:
      - rtsp://admin:[email protected]:554/h264Preview_01_sub
    Garage_Camera:
      - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    Garage_Camera_sub:
     - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1

ffmpeg:
  hwaccel_args: preset-nvidia-h265

rtmp:
  enabled: False 




cameras:
############## REAR DECK ##################
  Rear_Deck:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/Rear_Deck
          input_args: preset-rtsp-restream
          roles:
            - detect
        - path: rtsp://127.0.0.1:8554/Rear_Deck_sub
          input_args: preset-rtsp-restream
          roles:
            - record

 

PD: the stream feed of the frontend is indeed the one of the detect role. If you have the chance to use a hwaccel card I suggest you to use the restreaming ability to create a internal feed of the main high res stream and use it for both record and detect, you shouldn't see a big difference of CPU usage.

Link to comment
48 minutes ago, yayitazale said:

PD: the stream feed of the frontend is indeed the one of the detect role. If you have the chance to use a hwaccel card I suggest you to use the restreaming ability to create a internal feed of the main high res stream and use it for both record and detect, you shouldn't see a big difference of CPU usage.

Sorry.  Absolutely nothing you just said made any sense to me.

 

I'm waiting for the next version of Frigate, like you mentioned, that will have the NVIDIA detection stuff "built in".  I can only guess that's what you meant by hwaccel card?  I gave up on the TesnoRT stuff once I read your comment about that. 

 

I've offered cold-hard-Paypal funds to many people on many Frigate forums to just code my YML for me since I've been working on this for almost a year now and simply can't figure it out.  No one has taken me up on my offer.  So, I just keep plugging away at this in an act of frustration.

 

Thanks anyway.  I will continue to just lurk here and read and not post anything because I don't have the basic knowledge to even understand your reply. lol

Link to comment

Would anyone be willing to help me get notifications working?  I have Frigate installed (ghcr.io/blakeblackshear/frigate:stable-tensorrt),  Home Assistant (lscr.io/linuxserver/homeassistant) installed with Frigate Integration and Blueprint, and Mosquitto (eclipse-mosquitto:2) installed.  I cannot figure out how to get notifications working.  Any help would be greatly appreciated.

Link to comment
On 1/10/2024 at 4:05 PM, dopeytree said:

10fps is quite high for detection. Frigate recommends 5fps. My cameras go up in 2s so 2,4,6,8,10 etc. have found 4fps works just as well with less cpu strain. 

See how you go with it.

 

If you need more personalised help try creating an issue on the GitHub for frigate here and one of the devs will help.

https://github.com/blakeblackshear/frigate/issues

 

Ok, I took your advice and dropped it down to 4ps.  I didn't see any noticeable difference either.  Thank you for that suggestion.

Link to comment
On 1/13/2024 at 3:34 PM, CyberOxide said:

Would anyone be willing to help me get notifications working?  I have Frigate installed (ghcr.io/blakeblackshear/frigate:stable-tensorrt),  Home Assistant (lscr.io/linuxserver/homeassistant) installed with Frigate Integration and Blueprint, and Mosquitto (eclipse-mosquitto:2) installed.  I cannot figure out how to get notifications working.  Any help would be greatly appreciated.

 

This helped me a great deal when setting up my notifcations

 

https://community.home-assistant.io/t/frigate-mobile-app-notifications/311091

  • Like 1
Link to comment
  • 2 weeks later...

Hi all,

 

Having trouble getting Frigate running on docker in unRAID.

When I log in into the web UI, all I get is the frigate logo in the top left and a spinning blue icon in the middle. It never loads. 

I assume the appdata config/frigate directory should not be empty? The 'frigate' folder is created but there is nothing inside it. I get permission errors when trying to create folders/files while the docker image is running.

I can't see the logs as the log window auto closes after like half a second. I have had no issues with any of my other containers.

I've deleted the docker image and manually created the frigate folder, and created the subfolder and frigate.yaml file (with some default code), but the same issue occurs.

 

Any ideas or am I missing something obvious?

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...