Bonjour,
J’essaie d’installer frigate sur un petit pc intel …
Le module compléméntaire est ok , frigate fonctionne … mais si j essais d’installer l’integration
.
.
.
dans les journeaux , j’ai :
.
.`Cette erreur provient d’une intégration personnalisée
Enregistreur: custom_components.frigate.api
Source: custom_components/frigate/api.py:364
intégration: Frigate (documentation, problèmes)
S’est produit pour la première fois: 17:52:05 (2 occurrences)
Dernier enregistrement: 17:59:15
Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:default [DNS server returned answer with no data]`.
.
.
c’est le deuxième frigate que j’installe , et celui d’avant , je n’avais pas ce problème de DNS …
.
je suis sur le même réseau …
ma config :
## System Information
version | core-2024.12.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.13.0
os_name | Linux
os_version | 6.6.63-haos
arch | x86_64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 4999
Installed Version | 2.0.1
Stage | running
Available Repositories | 1486
Downloaded Repositories | 7
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 14.0
-- | --
update_channel | stable
supervisor_version | supervisor-2024.11.4
agent_version | 1.6.0
docker_version | 27.2.0
disk_total | 109.3 GB
disk_used | 7.2 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | generic-x86-64
supervisor_api | ok
version_api | ok
installed_addons | Mosquitto broker (6.4.1), File editor (5.8.0), Advanced SSH & Web Terminal (19.0.0), Frigate (0.14.1)
</details>
<details><summary>Dashboards</summary>
dashboards | 2
-- | --
resources | 2
views | 2
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 9 décembre 2024 à 15:50
-- | --
current_recorder_run | 15 décembre 2024 à 17:50
estimated_db_size | 8.19 MiB
database_engine | sqlite
database_version | 3.45.3
</details>
.
.
ma config frigate
mqtt:
host: 192.168.0.29
port: 1883
user: mXXXX
password: diXXXXX15
ui:
time_format: 24hour
ffmpeg:
hwaccel_args: preset-vaapi
objects:
track:
- person
- bird
- cat
- dog
detectors:
cpu1:
type: cpu
num_threads: 2
snapshots:
enabled: true
timestamp: true
retain:
default: 10
record:
enabled: true
retain:
days: 2
mode: motion
events:
retain:
default: 2
mode: motion
cameras:
balcon:
ffmpeg:
inputs:
- path: rtsp://admin:HXXXXXXXX344@192.168.0.31:554/h.264
roles:
- detect
objects:
filters:
person:
min_score: 0.57
threshold: 0.57
bird:
min_score: 0.75
threshold: 0.75
dog:
min_score: 0.70
threshold: 0.70
cat:
min_score: 0.70
threshold: 0.70
mask: 0.017,0.941,0.37,0.952,0.366,0.995,0.016,0.994
detect:
# width: 1280
# height: 720
width: 640
height: 360
fps: 5
motion:
threshold: 20
contour_area: 25
improve_contrast: 'true'
mask: 0.016,0.944,0.371,0.952,0.369,1,0.019,1
version: 0.14
…
.le journal de demarrage de frigate
2024-12-15 17:19:43.682592418 [2024-12-15 18:19:43] frigate.storage INFO : Exiting storage maintainer...
2024-12-15 17:19:43.682773005 [2024-12-15 18:19:43] frigate.events.cleanup INFO : Exiting event cleanup...
2024-12-15 17:19:43.682934832 [2024-12-15 18:19:43] frigate.ptz.autotrack INFO : Exiting autotracker...
2024-12-15 17:19:43.683061967 [2024-12-15 18:19:43] frigate.stats.emitter INFO : Exiting stats emitter...
2024-12-15 17:19:43.683178781 [2024-12-15 18:19:43] frigate.watchdog INFO : Exiting watchdog...
2024-12-15 17:19:43.683447826 [2024-12-15 18:19:43] frigate.record.cleanup INFO : Exiting recording cleanup...
2024-12-15 17:19:43.684501852 [2024-12-15 18:19:43] frigate.app INFO : Waiting for capture process for bacon to stop
2024-12-15 17:19:43.685329648 [2024-12-15 18:19:43] watchdog.bacon INFO : Terminating the existing ffmpeg process...
2024-12-15 17:19:43.685725834 [2024-12-15 18:19:43] watchdog.bacon INFO : Waiting for ffmpeg to exit gracefully...
2024-12-15 17:19:43.704223036 [2024-12-15 18:19:43] frigate.object_processing INFO : Exiting object processor...
2024-12-15 17:19:43.728105235 [2024-12-15 18:19:43] frigate.app INFO : Waiting for process for bacon to stop
2024-12-15 17:19:43.791735325 [2024-12-15 18:19:43] frigate.video INFO : bacon: emptying frame queue
2024-12-15 17:19:43.792028910 [2024-12-15 18:19:43] frigate.video INFO : bacon: exiting subprocess
2024-12-15 17:19:43.796866144 [2024-12-15 18:19:43] frigate.app INFO : Closing frame queue for bacon
2024-12-15 17:19:43.830970242 [2024-12-15 18:19:43] frigate.events.maintainer INFO : Exiting event processor...
2024-12-15 17:19:44.297993581 [2024-12-15 18:19:44] root INFO : Waiting for detection process to exit gracefully...
2024-12-15 17:19:44.298269171 [2024-12-15 18:19:44] detector.cpu1 INFO : Signal to exit detection process...
2024-12-15 17:19:44.789884114 [2024-12-15 18:19:44] detector.cpu1 INFO : Exited detection process...
2024-12-15 17:19:44.794287404 [2024-12-15 18:19:44] root INFO : Detection process has exited...
2024-12-15 17:19:45.295791667 [2024-12-15 18:19:45] frigate.app INFO : Detection queue closed
2024-12-15 17:19:45.797197161 [2024-12-15 18:19:45] frigate.app INFO : Detected frames queue closed
2024-12-15 17:19:46.298540805 [2024-12-15 18:19:46] frigate.app INFO : Timeline queue closed
2024-12-15 17:19:47.508603830 [2024-12-15 18:19:47] frigate.output.output INFO : exiting output process...
2024-12-15 17:19:52.717508380 [2024-12-15 18:19:52] frigate.review.maintainer INFO : Exiting review maintainer...
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 certsync-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 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 frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2024-12-15 17:20:20.694257497 [INFO] Preparing Frigate...
2024-12-15 17:20:20.697934870 [INFO] Starting NGINX...
2024-12-15 17:20:20.700226039 [INFO] Preparing new go2rtc config...
2024-12-15 17:20:20.708318463 [INFO] No TLS certificate found. Generating a self signed certificate...
2024-12-15 17:20:20.708431390 [INFO] Starting Frigate...
2024-12-15 17:20:20.750935311 [INFO] Got IP address from supervisor: 192.168.0.29
2024-12-15 17:20:20.800292120 [INFO] Got WebRTC port from supervisor: 8555
2024-12-15 17:20:21.290129695 [INFO] Starting go2rtc...
2024-12-15 17:20:21.502822118 18:20:21.502 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-12-15 17:20:21.502851011 18:20:21.502 INF config path=/dev/shm/go2rtc.yaml
2024-12-15 17:20:21.503712227 18:20:21.503 INF [rtsp] listen addr=:8554
2024-12-15 17:20:21.503717582 18:20:21.503 INF [api] listen addr=:1984
2024-12-15 17:20:21.503941392 18:20:21.503 INF [webrtc] listen addr=:8555/tcp
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-12-15 17:20:21.731745249 [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-12-15 17:20:21.835321947 127.0.0.1 - - [15/Dec/2024:18:20:21 +0100] "" 400 0 "-" "-" "-"
2024-12-15 17:20:22.885632101 [2024-12-15 18:20:22] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa)
2024-12-15 17:20:22.885875538 [2024-12-15 18:20:22] frigate.app INFO : Creating directory: /tmp/cache
2024-12-15 17:20:22.886069047 [2024-12-15 18:20:22] frigate.util.config INFO : Checking if frigate config needs migration...
2024-12-15 17:20:22.907898027 [2024-12-15 18:20:22] frigate.util.config INFO : frigate config does not need migration...
2024-12-15 17:20:22.946619324 [2024-12-15 18:20:22] peewee_migrate.logs INFO : Starting migrations
2024-12-15 17:20:22.947885228 [2024-12-15 18:20:22] peewee_migrate.logs INFO : There is nothing to migrate
2024-12-15 17:20:22.956848617 [2024-12-15 18:20:22] frigate.app INFO : Recording process started: 349
2024-12-15 17:20:22.963097876 [2024-12-15 18:20:22] frigate.app INFO : Recording process started: 351
2024-12-15 17:20:22.967413232 [2024-12-15 18:20:22] frigate.app INFO : go2rtc process pid: 96
2024-12-15 17:20:22.994846611 [2024-12-15 18:20:22] detector.cpu1 INFO : Starting detection process: 378
2024-12-15 17:20:23.002146522 [2024-12-15 18:20:22] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-12-15 17:20:23.003579510 [2024-12-15 18:20:22] frigate.app INFO : Output process started: 380
2024-12-15 17:20:23.027671395 [2024-12-15 18:20:23] frigate.app INFO : Camera processor started for bacon: 394
2024-12-15 17:20:23.027677462 [2024-12-15 18:20:23] frigate.app INFO : Capture process started for bacon: 397
2024-12-15 17:20:30.695965497 [INFO] Starting go2rtc healthcheck service...
2024-12-15 17:21:21.861576165 127.0.0.1 - - [15/Dec/2024:18:21:21 +0100] "" 400 0 "-" "-" "-"
.
c’est quoi ce probléme de DNS ?? Svp …
… je ne saurai te dire pourquoi ça a changé… .
.
