Realtime camera streaming without any delay - WebRTC

Share your Projects!
472

I think I know your issue. You’re testing from a picture glance card in live view?

#5 and #6 won’t work correctly if you don’t have the RTSPtoWebRTC installed as that will allow you to use existing glance cards and such with webrtc. Without that, you’re using HLS and you’re trying to push OPUS through it which won’t work.

You’ve kind of done a full circle here.

If you want to use the in-built cards, you’ll need RTSPtoWebRTC. If you use that package, your nest audio won’t work because it would need to be transcoded but there isn’t a way to reference that camera in go2rtc.yaml in order to do that.
If you don’t want to use the inbuilt cards, you can use iframes (like i do) for video but that will require a more complicated nginx setup to get the feeds into the iframe cards.

I think any way you do this, you’re going to lose audio from one source or you’re not going to be able to use inbuilt cards. You may want to wait for this to mature a bit.

1 Like
473

That makes total sense @calisro, thanks for all the help. I use the panel_custom integration but might look into iframes as well. I have nginx set up for my remote access, so might be able to make it work. Quick question, with iframes, are you able to display multiple cameras together in one panel or one per panel?

I think with regards to go2rtc, I agree with you that my best bet will be to wait for @AlexxIT to incorporate it into the custom component, at which point I’ll be able to truly pick and choose the cameras I use it for.

474

I am still trying to sort this issue out with two of my amcrest cameras. The native resolution is 2560X1440 and in the default card they display as 16:9, on Frigate they display as 16:9, in WebRTC card they display as 4:3

475

@AlexxIT Hi Alexey, your add-on go2rtc is providing lag free and immediate starting video streams. An unbelievable improvement to what it was before with the integrated stream capabilities. :grinning:
Thank you so much!!

1 Like
476

The latest beta 6 release will let you use your nest camera by transcoding the audio. Fixed my audio since you can now reference that nest stream .

477

That’s amazing, just tested it after adding the camera entity_id to the go2rtc.yaml as per the updated instructions and indeed it works! I must say, the speed with which this project is maturing is truly astounding. Keep up the great work @AlexxIT!

I actually had also just gotten the iframes to work on the local network, but not yet remotely as I’m having trouble getting the nginx settings correctly. @calisro, I was just about to ask you for some help in the dedicated go2rtc thread, so I may do that as it looks like the conversation is changing to there. I’ll post there shortly.

1 Like
478

I’m really interested in the iframes config, even if it’s just for local network. Mind sharing (maybe a preview :wink: )?

479

Sure thing. I use a picture-elements card, as I also include the PTZ controls for my Foscam. Here’s my card setup. Don’t forget to define a custom location in your nginx setup if you want to use this remotely, and add the custom nginx settings as described by @calisro here.

Also, the card below assumes you’ve setup browser-mod already.

type: picture-elements
camera_image: camera.baby_cam_1
camera_view: live
elements:
  - type: image
    entity: camera.baby_cam_1
    camera_image: camera.baby_cam_1
    camera_view: live
    style:
      top: 50%
      left: 50%
      width: 100%
      opacity: 0%
    tap_action:
      action: fire-dom-event
      browser_mod:
        service: browser_mod.popup
        data:
          title: Baby Cam 1
          size: wide
          content:
            type: iframe
            url: >-
              https://yourdomain.duckdns.org/go2rtc/webrtc.html?src=camera.baby_cam_1
            aspect_ratio: 75%
  - type: icon
    icon: mdi:arrow-up
    style:
      color: rgba(255, 255, 255, 0.5)
      background: rgba(255, 255, 255, 0)
      right: 15px
      bottom: 40px
    tap_action:
      action: call-service
      service: foscam.ptz
      service_data:
        entity_id: camera.baby_cam_1
        movement: up
  - type: icon
    icon: mdi:arrow-down
    style:
      color: rgba(255, 255, 255, 0.5)
      background: rgba(255, 255, 255, 0)
      right: 15px
      bottom: '-10px'
    tap_action:
      action: call-service
      service: foscam.ptz
      service_data:
        entity_id: camera.baby_cam_1
        movement: down
  - type: icon
    icon: mdi:arrow-left
    style:
      color: rgba(255, 255, 255, 0.5)
      background: rgba(255, 255, 255, 0)
      right: 40px
      bottom: 15px
    tap_action:
      action: call-service
      service: foscam.ptz
      service_data:
        entity_id: camera.baby_cam_1
        movement: left
  - type: icon
    icon: mdi:arrow-right
    style:
      color: rgba(255, 255, 255, 0.5)
      background: rgba(255, 255, 255, 0)
      right: '-10px'
      bottom: 15px
    tap_action:
      action: call-service
      service: foscam.ptz
      service_data:
        entity_id: camera.baby_cam_1
        movement: right

If you want to use a picture-glance card you can also use this code.

2 Likes
480

Hey All,

I have webrtc setup on my supervisor Home assistant setup. And I am using a Cloudflare tunnel (aka Argo tunnel) to remote access the HA instance.

I was wondering if anyone else is having issue on the iOS mobile app this streaming Webrtc when connected to mobile LTE. I have T-Mobile so I know their network is behind a CGNat.
When I connect to my home wifi network I am able to effectively see all of my cameras, through my remote domain.

It is only when I use LTE, do I see these errors in webrtc home assistant logging.

2022-09-22 15:30:17.192 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:17 Stream Exit On Demand No Viewer
2022-09-22 15:30:17.383 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:17 Stream Exit On Demand No Viewer
2022-09-22 15:30:17.384 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:17 Stream Exit On Demand No Viewer
2022-09-22 15:30:23.529 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:23 Set ICEServers [stun:stun.l.google.com:19302]
2022-09-22 15:30:23.544 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:23 Set ICEServers [stun:stun.l.google.com:19302]
2022-09-22 15:30:23.626 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:23 websocket.JSON.Send write tcp 127.0.0.1:8084->127.0.0.1:39144: i/o timeout
2022-09-22 15:30:23.686 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:23 websocket.JSON.Send write tcp 127.0.0.1:8084->127.0.0.1:39142: i/o timeout
2022-09-22 15:30:23.753 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/09/22 15:30:23 Set ICEServers [stun:stun.l.google.com:19302]

Does anyone have any other tips as to troubleshooting this? Wireshark possibly?
I’ve been trying to read up on NAT documentation, but I cant effectively troubleshoot what is going wrong when I try to remotely stream through a LTE connection.

481

Has anyone had any luck finding a way to get the nest camera RTSP stream in WebRTC?

482
483

Thanks for the link - it works!

I installed a docker image of go2rtc, then added RTSPtoWebRTC to Home Assistant.
The nest camera was automatically changed to WebRTC on my RTSPtoWeb card without any further changes.

484

Hi @AlexxIT thanks for this custom component.

I am getting a handful of dns request (coming from my HA IP) for stun.l.google.com whenever I go to the stream in HA. I can see this url has been mentioned a few times but I didn’t really get what it is for.
This is just on my local network so I don’t understand why it is necessary to connect to the internet for this purpose? : )
I am connecting to a Wyze Cam v3 with rtsp enabled by wz_mini_hacks using a very basic config like this

          - type: custom:webrtc-camera
            url: rtsp://login:password@IP_ADDRESS:8554/unicast
485

Just google what is STUN for WebRTC connection

1 Like
486

Yes I have read the guides. I can understand that for streaming from HA to somewhere external the STUN setup or port forwarding is needed. But I am only streaming from HA (or rather the camera) 5 feet away to my laptop and everything is on the same local network. Is it also required in that situation?

487

The component does not know if you are in your network or not. That is why the STUN server is used. Your video data doesn’t go through Google’s servers. It doesn’t matter if you are on a local network or not. It is only a request for a your public IP address and opening a UDP hole.

You can set your STUN settings (empty I guess) for custom card.

1 Like
488

Hello! I facing the constantly restarting connection it’s normal?

Screenshot_2022-10-27-10-55-25-11_c3a231c25ed346e59462e84656a70e50
Screenshot_2022-10-27-10-55-25-11_c3a231c25ed346e59462e84656a70e501080×1226 130 KB

Sometimes it stabilizes but if you refresh the page the problem comes back…

I’m using 2 cameras from tapo c210. Any configuration I have to do on the cameras or in this integration?

489

No, not normal.
Maybe camera sending unstable video feed.

490

This is “normal” for MSE technology. The icon at the top right tells you what technology you have now.

491

Sorry i don’t understand where put “go2rtc.yaml” configuration file,… in hass.io