RiderCrazy a écrit :
Perso, je resterai sur le couple pass/mdp que tu utilisent avec octoprint. Chez moi, j'ai même pas déclaré le enabled ni le port (vu que c'est celui par défaut)
|
Je vais tester avec ce que tu me dis, en attendant si ça peut aider :
Logs MQTT en activant juste avant de relancer frigate, j'ai une chiée de lignes avec ça, pour plusieurs caméras et plusieurs entités, ça indiquerait que MQTT reçoit bien? :
Code :
- 2024-04-09 08:43:01.495 WARNING (MainThread) [homeassistant.components.select.reproduce_state] Invalid state specified for select.camera_chambre_move_to_preset: unknown
|
Logs frigate :
Code :
- 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
- 2024-04-09 06:43:11.433793284 [INFO] Preparing new go2rtc config...
- 2024-04-09 06:43:11.433830777 [INFO] Preparing Frigate...
- s6-rc: info: service nginx successfully started
- s6-rc: info: service legacy-services: starting
- 2024-04-09 06:43:11.435917591 [INFO] Starting NGINX...
- s6-rc: info: service legacy-services successfully started
- 2024-04-09 06:43:11.445340898 [INFO] Starting Frigate...
- 2024-04-09 06:43:11.470205577 [INFO] Got IP address from supervisor: 192.168.1.9
- 2024-04-09 06:43:11.505979058 [INFO] Got WebRTC port from supervisor: 8555
- 2024-04-09 06:43:11.768958605 [INFO] Starting go2rtc...
- 2024-04-09 06:43:11.860310301 08:43:11.860 INF go2rtc version 1.8.4 linux/amd64
- 2024-04-09 06:43:11.861023512 08:43:11.860 INF [rtsp] listen addr=:8554
- 2024-04-09 06:43:11.861050056 08:43:11.860 INF [api] listen addr=:1984
- 2024-04-09 06:43:11.861281197 08:43:11.861 INF [webrtc] listen addr=:8555
- 2024-04-09 06:43:12.937499928 [2024-04-09 08:43:12] frigate.app INFO : Starting Frigate (0.13.2-6476f8a)
- 2024-04-09 06:43:12.937752396 [2024-04-09 08:43:12] frigate.app INFO : Creating directory: /tmp/cache
- 2024-04-09 06:43:21.432482433 [INFO] Starting go2rtc healthcheck service...
- 2024-04-09 06:43:25.812888001 [2024-04-09 08:43:25] peewee_migrate.logs INFO : Starting migrations
- 2024-04-09 06:43:25.817745145 [2024-04-09 08:43:25] peewee_migrate.logs INFO : There is nothing to migrate
- 2024-04-09 06:43:25.823063314 [2024-04-09 08:43:25] frigate.app INFO : Recording process started: 404
- 2024-04-09 06:43:25.825933657 [2024-04-09 08:43:25] frigate.app INFO : go2rtc process pid: 89
- 2024-04-09 06:43:25.854722534 [2024-04-09 08:43:25] detector.cpu INFO : Starting detection process: 414
- 2024-04-09 06:43:25.858200509 [2024-04-09 08:43:25] frigate.app INFO : Output process started: 416
- 2024-04-09 06:43:25.859480971 [2024-04-09 08:43:25] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
- 2024-04-09 06:43:25.892848940 [2024-04-09 08:43:25] frigate.app INFO : Camera processor started for camera_Bureau: 422
- 2024-04-09 06:43:25.896729968 [2024-04-09 08:43:25] frigate.app INFO : Camera processor started for camera_Cuisine: 423
- 2024-04-09 06:43:25.902897653 [2024-04-09 08:43:25] frigate.app INFO : Camera processor started for camera_Chambre: 425
- 2024-04-09 06:43:25.914572031 [2024-04-09 08:43:25] frigate.app INFO : Camera processor started for camera_Salon: 428
- 2024-04-09 06:43:25.924635112 [2024-04-09 08:43:25] frigate.app INFO : Capture process started for camera_Bureau: 431
- 2024-04-09 06:43:25.924869666 [2024-04-09 08:43:25] frigate.app INFO : Capture process started for camera_Cuisine: 433
- 2024-04-09 06:43:25.925157017 [2024-04-09 08:43:25] frigate.app INFO : Capture process started for camera_Chambre: 444
- 2024-04-09 06:43:25.930369123 [2024-04-09 08:43:25] frigate.app INFO : Capture process started for camera_Salon: 453
|
En dessous de ça j'ai les logs de connexion Nginx que j'ai volontairement coupé car répétitif et pas d'erreur à priori
et conf frigate :
Code :
- mqtt:
- enabled: True
- host: 192.168.1.9
- port: 1883
- user: frigate
- password: frigate
-
- database:
- path: /config/frigate.db
- detect:
- enabled: True # <---- disable detection until you have a working camera feed
- objects:
- # Optional: list of objects to track from labelmap.txt (default: shown below)
- track:
- - person
- - cat
- - dog
- - cell phone
- record:
- # Optional: Enable recording (default: shown below)
- # WARNING: If recording is disabled in the config, turning it on via
- # the UI or MQTT later will have no effect.
- enabled: True
- retain:
- days: 1
- mode: all
- events:
- # Optional: Number of seconds before the event to include (default: shown below)
- pre_capture: 5
- # Optional: Number of seconds after the event to include (default: shown below)
- post_capture: 5
- # Optional: Objects to save recordings for. (default: all tracked objects)
- objects:
- - person
- - cat
- - dog
- retain:
- default: 10
- mode: motion
- # Optional: Configuration for the jpg snapshots written to the clips directory for each event
- # NOTE: Can be overridden at the camera level
- snapshots:
- # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
- enabled: True
- # Optional: save a clean PNG copy of the snapshot image (default: shown below)
- clean_copy: True
- # Optional: print a timestamp on the snapshots (default: shown below)
- timestamp: True
- # Optional: draw bounding box on the snapshots (default: shown below)
- bounding_box: True
- cameras:
- camera_Bureau: # <--- this will be changed to your actual camera later
- enabled: True
- ffmpeg:
- inputs:
- - path: rtsp://xx:xx@192.168.1.150:554/stream1
- roles:
- - detect
- - rtmp
-
- camera_Cuisine: # <--- this will be changed to your actual camera later
- enabled: True
- ffmpeg:
- inputs:
- - path: rtsp://xx:xx@192.168.1.151:554/stream1
- roles:
- - detect
- - rtmp
-
- camera_Chambre: # <--- this will be changed to your actual camera later
- enabled: True
- ffmpeg:
- inputs:
- - path: rtsp://xx:xx@192.168.1.152:554/stream1
- roles:
- - detect
- - rtmp
-
- camera_Salon: # <--- this will be changed to your actual camera later
- enabled: True
- ffmpeg:
- inputs:
- - path: rtsp://xx:xx@192.168.1.153:554/stream1
- roles:
- - detect
- - rtmp
|
J'ai pris des bouts de confs dans le ficheir de référence, et d'autres tapés à la main, d'où les lignes commentées
Edit : avec cette config :
mqtt:
host: 192.168.1.9
user: homeassistant
password: xxx
Même comportement à priori, pas d'entité qui remontent, pas de logs spécifiques