pi-webrtc
Signaling

WHEP

WHEP (WebRTC-HTTP Egress Protocol) lets any WHEP player play the stream from a URL. pi-webrtc serves WHEP itself, so you need no broker and no account.

WHEP signaling

Start pi-webrtc with WHEP

./pi-webrtc --camera=libcamera:0 --uid=my-pi --no-audio --use-whep --whep-port=8080

The stream URL is http://<device-ip>:8080. The default port is 8080.

Players

PlayerHow to use it
app.mazupo.com/whepEnter the stream URL as the WHEP URL, and connect.
Eyevinn webrtc-playerOpen the demo player. Keep the adapter on WHEP, and play the stream URL.
Home AssistantAdd a WebRTC Camera card with the stream URL.

HTTP and HTTPS

pi-webrtc serves WHEP over plain HTTP. A player page loaded over https:// then makes a "mixed content" request:

  • Chrome allows it for private addresses, such as 192.168.x.x, after you click Allow on its local network prompt.
  • Other browsers may block it. Then open the player over http://, for example http://app.mazupo.com/whep.

Limits

  • WHEP carries no DataChannel. Snapshots, recording control, file transfer and IPC do not work over WHEP. Use MQTT for them.
  • Each viewer gets its own connection and its own encoder on the device. For many viewers, use an SFU.
Edit on GitHub

Signaling

Before video can flow, the browser and the device must exchange connection details (an SDP offer and answer, and ICE candidates). This step is called signali...

MQTT

Watch the camera from anywhere, without a public IP address or port forwarding. The device and the browser exchange connection details through an MQTT broker...

On this page

Start pi-webrtc with WHEPPlayersHTTP and HTTPSLimits