Open morikplay opened 1 week ago
Appears that your instance ID in the frigate card is wrong. Think you need to use this: frigate_pve_vm
@igiannakas Many thanks for taking the time to review the logs to provide a way forward. I only have 1 frigate client instance (frigate_pve_vm
) - which per frigate-card's documentation isn't necessary to enter in the case of a single client. That said, adding client instance leads to the same error message.
As next step, I'll remove frigate containers/instance, re-create it (w/ same configuration), and try a re-import into HA. Please do grant me until Sept 22 to report on progress.
If you change the default name from frigate I think it is needed
Version of the custom_component
Frigate: 0.14.1-f4f3cfa Frigate IP: 192.168.100.22 HTTPS: Yes. https://frigate.esco.ghaar:8971
HomeAssistant Core: 2024.9.1 HA Supervisor: 2024.08.0 HA OS: 13.1 HA Frontend: 20240906.0 HA IP: 192.168.0.58 HTTPS: Yes. https://homeassistant.esco.ghaar
HA HACS Frigate Integration: v5.4.0
Frigate Configuration
Describe the bug
Frigate runs in a docker container on a machine separate to HA. Both have
http
(5000
and8123
respectively) andhttps
enabled. HA gets served fromhttps
link.http
links for HA get redirected tohttps
via localnginx
.Frigate access via allowed network'ed computer ✅
HA access via allowed network'ed computer ✅ HA's access to Frigate instance (via HA Terminal) ✅
HA Frigate integration correctly shows all cameras and relevant metrics ✅
But, when viewing any camera's streaming (either via "Visit this camera" option in HA or via
frigate-hass-card
) for cameras other thanbirdseye
results in redirection tohttp://frigate.esco.ghaar:5000
. Debug log indicate:5000/api/stats
is not accesible. But, curl commands above demonstrate that the address is reachable.This results in
custom: frigate-card
being unable to show camera views.If I were to hazard a guess, then
ssl:default
may be an issue. If ssl can be set tofalse
, then perhaps it may work?Debug log