-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go2rtc dashboard as an iframe in the Frigate UI #7668
Comments
I think the same work that would go into this would be more worthwhile just supporting two way talk in the frigate webui |
That's true. |
go2rtc can serve https itself from version 1.6.0 |
Yeah, but it doesn't make anything easier. To make it work I would need to setup a local DNS server or expose 1984 to open internet, which I very much don't want. |
you can get wildcard cert for your domain and create a sub-domain (A-record) that point to local IP of frigate/go2rtc host |
That's clever, I could do that indeed. Still, I would have to generate a certificate and configure the domain. Too much work for such a simple goal. (PS: I'm not looking for alternative solutions, as stated in the issue description I already have one solution working). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe what you are trying to accomplish and why in non technical terms
I am testing whether some cameras I have are working with 2-way audio or not, but to test that, I need the go2rtc dashboard to be served with HTTPs.
When running go2rtc as its own add-on, this is trivial thanks to hassio's ingress. But when running it inside Frigate, it's a lot more complicated.
Describe the solution you'd like
I believe it would be possible to embed the go2rtc dashboard in the Frigate UI itself, by using some iframe trickery I suppose. I am not experienced with this, but I'm assuming it's possible and it should not be too difficult.
Describe alternatives you've considered
Additional context
None.
The text was updated successfully, but these errors were encountered: