Alex X

What viewers (html) have your tried? What about Frigate 12 release?

Basic docker users (also Frigate docker users) shouldn't have any problems with LAN connections. And shouldn't add any local IP to go2rtc config. They should use docker network host option....

@gedl do you have problems with local or with external connections?

WebRTC (in the browser and in the go2rtc) will try all possible ways to connect. Because they don't know which is the best route.

You can disable STUN in the go2rtc yaml. Just use empty ice servers list.

Browser still has ice settings. You can be changed only with JS code. No any settings for that. But it shouldn't be a problem.

You can enable trace log level for webrtc module and check all local and remote candidates there

I think it's hard task for really hi level network engineers to build solid local routing between multiple local subnets. There is no magic here. Two clients are exchanging IP...

- check you don't have any errors in HA log - check you using same ewelink username - check you using same ewelink home - check https://github.com/AlexxIT/SonoffLAN?tab=readme-ov-file#issues

https://github.com/AlexxIT/SonoffLAN?tab=readme-ov-file#issues