Closed conorlap closed 1 year ago
I'm facing the same issue.
Possibly a long-shot but can you try having this in your frigate.yml
(not the card, the backend):
go2rtc:
api:
origin: "*"
[... rest of config ...]
See this debugging thread between myself and Nick where we ran into an issue that could theoretically be another version of what you are reporting.
That works!
BTW, I have the Frigate add-on, and the HA integration connects to it using its internal hostname local-frigate-beta
(local because I'm using my modified version with dev release).
@NickM-27 Do you think we should have this set by default? Suspect this may keep happening with various different permutations of host names that people will inevitable use.
Interesting, I hadn't thought of that.
My initial thing is it's either set it by default or just make it prevalent in the frigate and frigate card docs.
I would say it should be the default configuration, unless someone complains otherwise. :)
Yep that fixes my issue also! 🥳
@NickM-27 added this as default in https://github.com/blakeblackshear/frigate/pull/5610 -- thanks Nick!
Closing this issue.
Checklist:
Release with the issue: Latest manual build of 4.1.0
Last working release (if known): Didn't work on any build of 4.1.0 that I've tried so far
Browser and Operating System: Edge / macOS
Description of problem: When go2rtc is selected as live view provider, the stream does not load when HA is accessed via external URL (nginx and reverse proxy). Both Home Assistant Video Stream & WebRTC Card live view options work fine. Live view via go2rtc works fine when using local IP of my HA instance (http://192.168.0.22:8123)
Javascript errors shown in the web inspector (if applicable):
Additional information: