go2rtc support hardcode IP list. Check docs.
I’m trying to decide which networks to ignore. Maybe all networks 172.xxx.xxx.xxx
Nice @AlexxIT ! I plan to look deeper at your new project on the weekend so will read the docs fully then. I suspect you will need to allow the user to configure what ranges they should ignore - as docker people may like to fiddle with non standard ranges. Did you want me to move this chat to a new github issue (how do you find the time mate?!!! Very appreciative of your dev. Ill buy you a coffee when im up and running).
Range of networks is very complicated for middle user. I don’t like having options like this.
Unfortunately, you can’t send me a coffee after february 2022…
New feature for go2rtc - support stream from local USB cameras to RTSP and WebRTC.
Tested cameras from Windows, macOS, HassIO installations.
1 Like
I am using 172.16.3.x as my local net …might not be the best option 
To close this tangent off here… ive just spun up your go2rtc project, and early signs are very promising (for anyone following the IP address problem of hass inside of docker running behind nginx - i believe it will be solved via this new project - by virtue of the fact that the webRTC server in the new project runs as its own container - which you can place on a more accessible part of your docker network, NOT behind nginx where your HASS probably lives - which gets around the random UDP port thing that webRTC uses).
I do have some early questions… so have spawned off a new thread so as to not bug these good people on this already mega-thread.
For those interested in @AlexxIT wonderful new go2rtc project, lets continue the chat over here —> Go2rtc project - help thread
I have been using WebRTC player on my frontend for some time now, it was working great up until recently. I’m now getting an error: “ERROR: WebRTC server not available”, after some time it tries to restart the stream and it get’s the same error again.
When I hit F12 in my browser I see the following:
When I try to open the RTSP stream on my system it works great (through VLC player) for both the bunny.mp4 and my camera.
I honestly don’t know what has changed, but something must have changed.
Where can I start to troubleshoot.
Can you try to reload the integration?
And by integration you mean “WebRTC camera”. When I choose to reload it tell’s me I need to restart Homeassistant in order to reload the integration. This I have done multiple times lately.
Have you seen this project? The guy is doing interesting things with Eufy’s P2P
Thanks for sharing, yes, we had discussed this briefly inside eufy security repository.
In the go2rtc project, are you planning on mirroring the webrtc.create_link service that is in this project? I’ve been slowly moving over to the new project (which is pretty great btw) and I’m trying to work out now how I can get https streams over to some of my android devices that require it per camera. I currently use the create_link from this project to do that.
Yes. Some custom functions like webrtc.create_link require a custom component. I can’t do them with only addon. But them will be later. When go2rtc will be released as stable version.
Btw. New unique function: go2rtc now can get stream from HomeKit Camera. It’s the first app in the World that can do that.
4 Likes
Great work, thanks for everything.
Can we add streams using rest api rather than defining them in yaml file? I want eufy_security integration to get benefit of this add-on, via publishing its stream information automatically, without user intervention.
My experience so far says the zero config will work just fine out of the box with the eufy_security camera. You won’t need to do anything as long as the rtsp2webrtc addon is installed by the user. This is routing even my google home hub camera over webrtc without doing anything. It’s pretty slick.
1 Like
All Hass streams can be added on the fly on first start. No need to setup them via go2rtc config.
1 Like
You are right, i was supposed ask question about new add-on:-) wrong thread
The only thing about zero config though is what if I don’t want it for a particular stream (disables my AAC codec atm for example). THere’s no way to disable it that I can tell for one or more streams. They all convert to webrtc.
Both. WebRTC Camera integration and go2rtc add-on support create stream on the fly
First of, thanks so much for this great project @AlexxIT . I had tried to use the WebRTC custom component with my Foscam cameras and it was pretty unstable. Go2RTC works flawless, so I finally can get sound from them in Home assistant. I have a quick question about creating the streams on the fly. I have 3 Foscams and a Nest Cam (via a Nest Hub max). The Nest Cam works well with the standard Nest integration including the sound. The Foscams use an incompatible audio codec, hence why I need Go2RTC to get sound to work. Go2RTC works great with the Foscams but not so well with the Nest Cam, which often times out when negotiating a WebRTC offer, and when it does the sound actually doesn’t come through. I would prefer to not use Go2RTC with my Nest Cam at all. I tried specifying the streams in the go2rtc.yaml file, thinking that would disable the on-the-fly setup, but it didn’t. Any way to add a setting to either enable or disable on-the-fly stream setup? Alternatively, any chance you may know why Go2RTC doesn’t work well with the Nest Cam? Thanks in advance, and thanks again for all the hard work that must have gone into creating this addon.