Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats #754
Comments
|
Need to see the logs of the addon itself |
|
So sorry @NickM-27, here it is. What I find weird is that addon logs are mentioning only cam_one whereas HA logs are mentioning both of my cameras. And here are the different log entries in HA related to Frigate: |
|
Looks like the camera connection is timing out |
|
|
There are things to try like increasing timeout |
|
Which I can change by using this from what I found in the documentation. Is that right?
```
ffmpeg:
retry_interval: 30
```
…________________________________
De : Nicolas Mowen ***@***.***>
Envoyé : vendredi 1 novembre 2024 19:31
À : blakeblackshear/frigate-hass-integration ***@***.***>
Cc : Mathieu Gimenez ***@***.***>; Author ***@***.***>
Objet : Re: [blakeblackshear/frigate-hass-integration] Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats (Issue #754)
There are things to try like increasing timeout
—
Reply to this email directly, view it on GitHub<#754 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOK7FD6JHZFJO3SSMD5JKLDZ6PCJBAVCNFSM6AAAAABQ7HN5OOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGM3TQNZVG4>.
You are receiving this because you authored the thread.
|
|
As a |
|
Ok, it seems to work for the moment. However, I still get the error log in HA when I restart Frigate addon: And in the starting process in the Frigate addon log: |
|
Tengo el mismo problema desde la ultima Actualizacion de HA, llevaba funcionando mas de 1 año sin problemas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello there! I have two separate and independent instances of Home Assistant running HA OS and core on RPi5 with Google Coral. On both of them I run Frigate custom component and official addon and I have the same error log on both instances. The two instances are in different cities, so in different networks.
Version of the custom_component
v.5.4.0 on HACS and 0.14.1 for the full access addon
Debug log
Log entry
The text was updated successfully, but these errors were encountered: