Problème affichage flux vidéo Frigate

Stef_42 · Juillet 15, 2025, 8:00

Bonjour,

J’ai un problème de flux vidéo avec Frigate depuis ce matin…
J’ai tenté une restauration car j’ai mis à jour le Core et Frigate mais c’est toujours pareil…

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
s6-rc: info: service s6rc-fdholder successfully started
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 nginx-log successfully started
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 certsync-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
2025-07-15 08:01:09.748817379  [INFO] Preparing new go2rtc config...
2025-07-15 08:01:09.749189687  [INFO] Preparing Frigate...
2025-07-15 08:01:09.749474958  [INFO] Starting NGINX...
2025-07-15 08:01:09.884317861  [INFO] Got IP address from supervisor: 192.168.1.68
2025-07-15 08:01:09.922873570  [INFO] Got WebRTC port from supervisor: 8553
2025-07-15 08:01:10.280908550  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-07-15 08:01:10.702086429  [INFO] Starting Frigate...
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
2025-07-15 08:01:12.265475273  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-07-15 08:01:12.410844594  127.0.0.1 - - [15/Jul/2025:10:01:12 +0200] "" 400 0 "-" "-" "-"
2025-07-15 08:01:13.571009166  2025/07/15 10:01:13 [error] 165#165: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:13.571013971  2025/07/15 10:01:13 [error] 165#165: *2 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:13.710002224  2025/07/15 10:01:13 [error] 166#166: *4 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"
2025-07-15 08:01:13.710037595  2025/07/15 10:01:13 [error] 166#166: *4 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"
2025-07-15 08:01:14.910180068  [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually
2025-07-15 08:01:15.428932825  [INFO] Starting go2rtc...
2025-07-15 08:01:15.826797416  10:01:15.826 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-07-15 08:01:15.826869008  10:01:15.826 INF config path=/dev/shm/go2rtc.yaml
2025-07-15 08:01:15.828185703  10:01:15.828 INF [api] listen addr=:1984
2025-07-15 08:01:15.828200620  10:01:15.828 INF [rtsp] listen addr=:8554
2025-07-15 08:01:15.828812741  10:01:15.828 INF [webrtc] listen addr=:8555
2025-07-15 08:01:18.570080525  2025/07/15 10:01:18 [error] 165#165: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:18.570084607  2025/07/15 10:01:18 [error] 165#165: *6 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:18.758250029  2025/07/15 10:01:18 [error] 165#165: *8 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"
2025-07-15 08:01:18.758254663  2025/07/15 10:01:18 [error] 165#165: *8 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"
2025-07-15 08:01:19.740084787  [INFO] Starting go2rtc healthcheck service...
2025-07-15 08:01:23.569841307  2025/07/15 10:01:23 [error] 165#165: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:23.569845973  2025/07/15 10:01:23 [error] 165#165: *10 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:23.789060909  2025/07/15 10:01:23 [error] 165#165: *12 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"
2025-07-15 08:01:23.789065359  2025/07/15 10:01:23 [error] 165#165: *12 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"
2025-07-15 08:01:28.570297279  2025/07/15 10:01:28 [error] 165#165: *14 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:28.570301412  2025/07/15 10:01:28 [error] 165#165: *14 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2025-07-15 08:01:28.699235193  [2025-07-15 10:01:28] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-07-15 08:01:28.746033737  [2025-07-15 10:01:28] frigate.util.config            INFO    : frigate config does not need migration...
2025-07-15 08:01:28.826902960  2025/07/15 10:01:28 [error] 165#165: *16 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"
2025-07-15 08:01:28.826907426  2025/07/15 10:01:28 [error] 165#165: *16 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"
2025-07-15 08:01:28.938250126  [2025-07-15 10:01:28] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-07-15 08:01:28.964805578  [2025-07-15 10:01:28] frigate.app                    INFO    : Starting Frigate (0.15.2-3bda638)
2025-07-15 08:01:28.965321604  [2025-07-15 10:01:28] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-07-15 08:01:28.965345204  [2025-07-15 10:01:28] frigate.util.services          INFO    : Current file limits - Soft: 1024, Hard: 524288
2025-07-15 08:01:28.965350062  [2025-07-15 10:01:28] frigate.util.services          INFO    : File limit set. New soft limit: 65536, Hard limit remains: 524288
2025-07-15 08:01:29.004535334  [2025-07-15 10:01:29] peewee_migrate.logs            INFO    : Starting migrations
2025-07-15 08:01:29.004817608  [2025-07-15 10:01:29] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-07-15 08:01:29.135480065  [2025-07-15 10:01:29] frigate.app                    INFO    : Recording process started: 315
2025-07-15 08:01:29.138432480  [2025-07-15 10:01:29] frigate.app                    INFO    : Review process started: 316
2025-07-15 08:01:29.143432081  [2025-07-15 10:01:29] frigate.app                    INFO    : go2rtc process pid: 102
2025-07-15 08:01:29.164971765  [2025-07-15 10:01:29] detector.coral                 INFO    : Starting detection process: 331
2025-07-15 08:01:29.179784806  [2025-07-15 10:01:29] frigate.app                    INFO    : Output process started: 347
2025-07-15 08:01:29.183856451  [2025-07-15 10:01:29] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-07-15 08:01:29.395998920  10:01:29.393 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.396002922  10:01:29.394 WRN [rtsp] error="streams: wrong response on SETUP" stream=entree
2025-07-15 08:01:29.403486149  10:01:29.403 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.403490584  10:01:29.403 WRN [rtsp] error="streams: wrong response on SETUP" stream=entree_sub
2025-07-15 08:01:29.432966685  10:01:29.432 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.436939670  10:01:29.436 WRN [rtsp] error="streams: wrong response on SETUP" stream=terrasse_sub
2025-07-15 08:01:29.521743324  10:01:29.521 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.521747791  10:01:29.521 WRN [rtsp] error="streams: wrong response on SETUP" stream=terrasse
2025-07-15 08:01:29.535709267  10:01:29.535 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.535751328  10:01:29.535 WRN [rtsp] error="streams: wrong response on SETUP" stream=chambre_sub
2025-07-15 08:01:29.601668066  10:01:29.601 INF [streams] can't get track error="wrong response on SETUP"
2025-07-15 08:01:29.604242053  10:01:29.603 WRN [rtsp] error="streams: wrong response on SETUP" stream=chambre
2025-07-15 08:01:31.938306897  [2025-07-15 10:01:29] frigate.app                    INFO    : Camera processor started for entree: 364
2025-07-15 08:01:31.939849317  [2025-07-15 10:01:29] frigate.app                    INFO    : Camera processor started for terrasse: 365
2025-07-15 08:01:31.939852398  [2025-07-15 10:01:29] frigate.video                  ERROR   : entree: Unable to read frames from ffmpeg process.
2025-07-15 08:01:31.939854178  [2025-07-15 10:01:29] frigate.video                  ERROR   : terrasse: Unable to read frames from ffmpeg process.
2025-07-15 08:01:31.939855923  [2025-07-15 10:01:29] frigate.video                  ERROR   : terrasse: ffmpeg process is not running. exiting capture thread...
2025-07-15 08:01:31.939998405  [2025-07-15 10:01:29] frigate.video                  ERROR   : chambre: Unable to read frames from ffmpeg process.
2025-07-15 08:01:31.940128898  [2025-07-15 10:01:29] frigate.video                  ERROR   : chambre: ffmpeg process is not running. exiting capture thread...
2025-07-15 08:01:31.940308019  [2025-07-15 10:01:29] frigate.app                    INFO    : Camera processor started for chambre: 370
2025-07-15 08:01:31.940502777  [2025-07-15 10:01:29] frigate.app                    INFO    : Capture process started for entree: 377
2025-07-15 08:01:31.940613484  [2025-07-15 10:01:29] frigate.app                    INFO    : Capture process started for terrasse: 385
2025-07-15 08:01:31.940752848  [2025-07-15 10:01:29] frigate.app                    INFO    : Capture process started for chambre: 399
2025-07-15 08:01:31.940868698  [2025-07-15 10:01:29] frigate.video                  ERROR   : entree: ffmpeg process is not running. exiting capture thread...
2025-07-15 08:01:31.941447287  [2025-07-15 10:01:29] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-07-15 08:01:31.941605353  [2025-07-15 10:01:29] frigate.api.fastapi_app        INFO    : FastAPI started
2025-07-15 08:01:31.947154390  [2025-07-15 10:01:31] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

Savez vous d’où cela vient svp ?

EDIT : je viens de voir que sur mon appli Hikvision je n’accède plus aux caméras, il n’y a qu’en local.
Par contre je n’ai rien touché donc je ne sais pas d’où ça vient…

Merci d’avance!

WarC0zes · Juillet 15, 2025, 8:55

Bonjour,
tu as fais la maj de l’os en 16.0 ?

Stef_42 · Juillet 15, 2025, 8:59

Oui mais à priori cela ne vient pas de là.
Je viens de voir que sur mon appli Hikvision je n’accède plus aux caméras, il n’y a qu’en local.
Par contre je n’ai rien touché donc je ne sais pas d’où ça vient…
Le NVR j’y accède :

Par contre si je prends une caméra :

Je n’ai rien touché je ne sais pas pourquoi je n’arrive pas à accéder à la caméra depuis Hikconnect

WarC0zes · Juillet 15, 2025, 9:02

Comme j’avais vu cette issue:

github.com/home-assistant/operating-system

OS 16.0 - Frigate Add On fails to start - too many files open

ouvert 11:19AM - 20 Jun 25 UTC

fermé 07:17PM - 12 Jul 25 UTC

S-Przybylski

board/generic-x86-64

### Describe the issue you are experiencing After upgrading to OS 16.0.rc1 Frig…ate add on is not able to start. Reverting back to 15.2 fix the issue. Execpt the OS nothing else was changed at the same time! ```` ... 2025-06-20 10:44:56.042727893 Traceback (most recent call last): 2025-06-20 10:44:56.042952901 File "<frozen runpy>", line 198, in _run_module_as_main 2025-06-20 10:44:56.042956366 File "<frozen runpy>", line 88, in _run_code 2025-06-20 10:44:56.042960399 File "/opt/frigate/frigate/__main__.py", line 108, in <module> 2025-06-20 10:44:56.043705879 File "/opt/frigate/frigate/__main__.py", line 104, in main 2025-06-20 10:44:56.043932192 File "/opt/frigate/frigate/app.py", line 655, in start 2025-06-20 10:44:56.043936155 File "/opt/frigate/frigate/app.py", line 479, in start_camera_capture_processes 2025-06-20 10:44:56.044256808 File "/opt/frigate/frigate/util/image.py", line 839, in create 2025-06-20 10:44:56.044446621 File "/opt/frigate/frigate/util/image.py", line 818, in __init__ 2025-06-20 10:44:56.044627774 File "/usr/lib/python3.11/multiprocessing/shared_memory.py", line 104, in __init__ 2025-06-20 10:44:56.044987542 OSError: [Errno 24] Too many open files: '/cam8_frame22' 2025-06-20 10:44:56.059673380 Too many open files (src/ipc_listener.cpp:297) 2025-06-20 10:44:56.059679236 Fatal Python error: Aborted ... ```` ### What operating system image do you use? generic-x86-64 (Generic UEFI capable x86-64 systems) ### What version of Home Assistant Operating System is installed? 16.0.rc1 ### Did the problem occur after upgrading the Operating System? Yes ### Hardware details Asus PN41 - Intel(R) Pentium(R) Silver N6000 @ 1.10GHz - 16GByte RAM - 2 TB NVMe refer: https://www.asus.com/displays-desktops/mini-pcs/pn-series/mini-pc-pn41/ ### Steps to reproduce the issue 1. Upgrade OS from 15.2 to 16.0.rc1 2. Frigate add on version 0.16.0-beta3 fails to start ... ### Anything in the Supervisor logs that might be useful for us? ```txt ... 2025-06-20 12:42:43.919 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Frigate Beta is failed, restarting... ... 2025-06-20 12:45:08.209 ERROR (MainThread) [asyncio] Task exception was never retrieved future: <Task finished name='Task-4488' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1586> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')> Traceback (most recent call last): File "/usr/src/supervisor/supervisor/addons/addon.py", line 1600, in watchdog_container await self._restart_after_problem(event.state) File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 305, in wrapper raise on_condition( f"Rate limit exceeded, more than {self.throttle_max_calls} calls in {self.throttle_period(group_name)}", ) supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00 ``` ### Anything in the Host logs that might be useful for us? ```txt 2025-06-20 10:42:39.785 homeassistant systemd-coredump[7944]: Process 6948 (python3) of user 0 terminated abnormally with signal 6/ABRT, processing... 2025-06-20 10:42:39.795 homeassistant systemd[1]: Created slice Slice /system/systemd-coredump. 2025-06-20 10:42:39.801 homeassistant systemd[1]: Started Process Core Dump (PID 7944/UID 0). ... 2025-06-20 10:42:40.230 homeassistant systemd-coredump[7968]: Process 6948 (python3) of user 0 terminated abnormally without generating a coredump. 2025-06-20 10:42:40.235 homeassistant systemd[1]: systemd-coredump@0-7944-0.service: Deactivated successfully. ``` ### System information _No response_ ### Additional information _No response_

tu as mis a jour ton frigate ?

Stef_42 · Juillet 15, 2025, 9:06

J’ai remis le code mais cela me laisse « Disconnecté ». Je me demande si il n’y a pas un souci général depuis le serveur Hikvision ? Mais je ne sais pas comment vérifier à part demander à une autre personne si elle accède à ses caméras à distance.

WarC0zes · Juillet 15, 2025, 9:09

Bien possible, je ne pourrais pas te dire. Attends des réponses d’utilisateur de Hikvision.

Stef_42 · Juillet 16, 2025, 8:09

Bon c’est revenu comme c’est parti…
Par contre je vois que les caméras sont « Disconnecté » et je me demande si c’est pas en lien avec le fait que je ne reçois plus les notifications sur mon appli Hikvision…j’avais essayé de les mettre en protocole « ONVIF » et depuis plus rien…j’utilise des notifs Frigate pour mieux filtrer.

thib3113 · Juillet 16, 2025, 8:26

comment tu configures frigate pour accéder aux flux de tes cams ? via l’extérieur ?

Stef_42 · Juillet 16, 2025, 8:43

Voici mon fichier « Frigate.yml » :

mqtt:
  enabled: true
  host: IP_HA
  user: user_mqtt
  password: mdp
  client_id: frigate

detectors:
  coral:
    type: edgetpu
    device: usb
    
go2rtc:
  webrtc:
    candidates:
      - IP_HA:8555
      - stun:8555
  streams:
    entree:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/101?transportmode=multicast
    entree_sub:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/102?transportmode=multicast
    terrasse:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/201?transportmode=multicast
    terrasse_sub:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/202?transportmode=multicast
    chambre:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/301?transportmode=multicast
    chambre_sub:
      - rtsp://user:mdp@IP_NVR:554/Streaming/channels/302?transportmode=multicast
      
review:
  alerts:
    labels:
      - person
      - car
      - motorcycle
  detections:
    labels:
      - cat
      - dog
      - bird

cameras:
#Caméra entrée
  entree:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/entree
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/entree_sub
          roles:
            - detect
    detect:
      enabled: true
      width: 1280
      height: 720
      fps: 5
    objects:
      track:
        - person
        - cat
        - dog
        - car
        - motorcycle
      filters:
        person:
          threshold: 0.7
          min_area: 40000
        cat:
          threshold: 0.7
          min_area: 2000
          max_area: 20000
        dog:
          threshold: 0.7
          min_area: 2000
          max_area: 20000
        car:
          threshold: 0.7
          min_area: 60000
    snapshots:
      enabled: true
      bounding_box: true
      crop: false
      quality: 100
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 0
      alerts:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
      detections:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
    motion:
      mask: 0,0,0,0.298,0.687,0.333,0.668,0

#Caméra terrasse
  terrasse:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/terrasse
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/terrasse_sub
          roles:
            - detect
    detect:
      enabled: true
      width: 1280
      height: 720
      fps: 5
    objects:
      track:
        - person
        - cat
        - dog
      filters:
        person:
          threshold: 0.7
          min_area: 40000
        cat:
          threshold: 0.7
          min_area: 2000
          max_area: 20000
        dog:
          threshold: 0.7
          min_area: 3000
          max_area: 20000
    snapshots:
      enabled: true
      bounding_box: true
      crop: false
      quality: 100
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 0
      alerts:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
      detections:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
    motion:
      mask: 0,0,0,1,0.328,0.894,0.824,0

#Caméra chambre
  chambre:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/chambre
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/chambre_sub
          roles:
            - detect
    detect:
      enabled: true
      width: 1280
      height: 720
      fps: 5
    objects:
      track:
        - person
        - cat
        - dog
      filters:
        person:
          threshold: 0.7
          min_area: 40000
        cat:
          threshold: 0.7
          min_area: 2000
          max_area: 20000
        dog:
          threshold: 0.7
          min_area: 3000
          max_area: 20000
    snapshots:
      enabled: true
      bounding_box: true
      crop: false
      quality: 100
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 0
      alerts:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
      detections:
        retain:
          days: 14
        pre_capture: 15
        post_capture: 10
    motion:
      mask: 0,0,0,0.63,0.914,0
version: 0.15-1

Mon blueprint pour les notifications :

alias: Notification Frigate caméras pour Stef
description: ""
use_blueprint:
  path: SgtBatten/Stable.yaml
  input:
    camera:
      - camera.chambre
      - camera.entree
      - camera.terrasse
    notify_device: 762d5d199e413ae79ea3b00a6fe5c23d
    attachment: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg?bbox=1
    title: Détection caméra {{ camera_name }}
    update_thumbnail: true
    video: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/{{camera}}/clip.mp4
    message: Un(e) détection a eu lieu sur la caméra {{ camera_name }}.
    state_filter: false
    presence_filter:
      - person.stephane
      - person.emilie
    attachment_2: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg?bbox=1

thib3113 · Juillet 16, 2025, 8:49

ok, donc c’est du local .

Du coup, si ton NVR n’envoie rien à ton cloud, et ne donne pas d’accès au rtsp .

Est ce que ton NVR à bien accès aux vidéos ? est ce que tu as désactivé une option qui aurais désactiver le rtsp ?

Stef_42 · Juillet 16, 2025, 8:56

En local oui j’ai accès aux flux vidéos. J’ai vérifié hier à la maison sur l’écran branché au NVR.
Sur mon NVR :

Et un ex sur une de mes caméras :

Et là je ne sais pas si cela a une incidence…mais je suppose que oui puisqu’aucune communication ves l’extérieur ?

thib3113 · Juillet 16, 2025, 8:59

je connais pas le fonctionnement d’un NVR hikvision … tu sais comment on active/désactive le rtsp dessus ? ( ce serait pas dans le mode d’accès à la plateforme ? )

Stef_42 · Juillet 16, 2025, 9:26

Je ne sais pas du tout…

thib3113 · Juillet 16, 2025, 9:38

va falloir fouiller dans l’interface de ton NVR … et/ou dans sa doc …

Stef_42 · Juillet 16, 2025, 9:42

J’ai ça :

J’en fais quoi?

thib3113 · Juillet 16, 2025, 9:54

alors, je suis pas sûr d’avoir suivi, mais tu disais que ça refonctionne ?

Tu as touché ça ?

Sinon, au pire tu peux toujours tester les flux rtsp dans VLC (ouvrir un flux réseau) :
et tu mets juste : rtsp://user:mdp@IP_NVR:554/Streaming/channels/101?transportmode=multicast

Du coup, si frigate voit bien, et arrive à émettre des événements . Tu auras peut être des infos dans l’historique du blueprint ?

Stef_42 · Juillet 16, 2025, 10:00

Non je n’ai rien touché hier et c’est revenu tout seul.
Par contre lors de la mise en place de Frigate il y a quelques mois j’avais essayé de mettre les caméras en protocole ONVIF et depuis je n’ai plus de notifications sur mon aplli Hikvision. Je ne sais pas pourquoi…
J’ai donc utilisé le blueprint Frigate pour filtrer un peu plus et j’aimerais trouver une solution sur ma problématique plus haut avec l’ajout des filtres. Si quelqu’un utilise cela également.

thib3113 · Juillet 16, 2025, 10:10

J’ai donc utilisé le blueprint Frigate pour filtrer un peu plus et j’aimerais trouver une solution sur ma problématique plus haut avec l’ajout des filtres. Si quelqu’un utilise cela également.

C’est dans l’histoire de ton blueprint que tu as de grandes chances de trouver une réponse …

Par contre lors de la mise en place de Frigate il y a quelques mois j’avais essayé de mettre les caméras en protocole ONVIF et depuis je n’ai plus de notifications sur mon aplli Hikvision. Je ne sais pas pourquoi…

Si tu n’as pas de PTZ, l’onvif n’apporte pas grand chose avec frigate . Sinon, à part regarder les docs de ton NVR, ou fouiller dans l’interface, je ne sais pas trop comment t’aider là dessus … ( faudrait voir avec des experts hikvision sinon )

Stef_42 · Juillet 16, 2025, 12:27

Justement le but était de pouvoir contrôler ma caméra PTZ depuis HA…j’ai laissé tomber et remis comme c’était avant dans le paramétrage sur le NVR et caméras mais cela a fait sauté les notifications sur l’application.

thib3113 · Juillet 17, 2025, 7:43

je peux pas trop t’aider sur tout ça … car c’est vraiment lié à hikvision, et son NVR … faut lire ses docs …

Après, perso j’utilise le ptz sur plusieurs caméras avec frigate, sans soucis .

Si jamais, tu peux tenter d’explorer l’onvif pour trouver des infos . Tu peux t’aider de ODM download | SourceForge.net .

Pour les notifications HA, il faut regarder ton historique d’éxécutions dans ton automatisation/blueprint