WebRTC (HTTP) local OK but remote = no go

[JustinTDCT]

Maybe I am missing something here. If I am local HA has no issues using the webpage card and the WebRTC URL. If I VPN into my house, it works fine. Outside my home or not VPN'd in not so much. Since it would appear that bridge acts like a funnel of sorts for the cameras I setup an external URL and internal resolution. IE, if you are inside the LAN it resolves to the local IP but outside the LAN it would resolve to the external. I setup rules in my firewall to allow 8889TCP and 8189UDP from the WAN to that interal IP. Packet tracing shows packets look to be going in and out fine, not seeing drops. I edited the card and put the DNS name. No love. Internal is great, external not so much. What did I mniss?

[Deach01]

I’m using the WyzeBridge with Home assistant behind a router firewall with no issues whatsoever.
I don’t believe the webpage card is the correct way to implement a camera
Here’s what I have:
1st, I’m using nabu-casa for external access. It makes the entire dns, dhcp, Nat, etc go away. ISP’s are just too unpredictable with all sorts of nonsense going on like double Nat, rapidly changing dhcp, and general obstacles to running “servers” on “their” systems
2nd, create camera entities using the generic camera platform
Example only! Use your own rtsp camera names
Still image: http://127.0.0.1:5000/img/front-doorbell.jpg
Stream source: rtsp://127.0.0.1:8554/front-doorbell
TCP
basic
No username and password (this may depend on your WyzeBridge authentication settings)
3rd use picture entity card (or other card designed for cameras) for display.

This will also take advantage of the home assistant built in go2rtc feature that was added a month or so ago and really sped up startup time for the display of cameras.

If things work internally and don’t work outside the local lan, it’s not a WyzeBridge issue, it’s a network issue and that’s beyond the scope of this “forum”.