mrlt8/docker-wyze-bridge

WebRTC/RTSP/RTMP/LL-HLS bridge for Wyze cams in a docker container

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 21st, 2026
Created on June 26th, 2021
Open Issues & Pull Requests: 376 (+0)
GitHub issues: Enabled
Number of forks: 292
Total Stargazers: 3,268 (+0)
Total Subscribers: 71 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.7 hours
Mean response time: 14.3 days
90th percentile: 35.5 days
Tracked items: 122

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 126
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 582 days
Stale 30+ days: 122
Stale 90+ days: 118

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (62)
  • enhancement (5)
  • documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

docker-wyze-bridge is a Docker container that bridges Wyze cameras to multiple streaming protocols.

The tool solves the problem of integrating Wyze cameras into home automation and NVR systems by translating their proprietary protocol into standard streaming formats. It runs as a containerized service that accepts connections from Wyze cameras and exposes them via WebRTC, RTSP, RTMP, and LL-HLS protocols. This approach allows Wyze cameras to work with any system that understands these standard protocols, rather than requiring proprietary Wyze software.

The project suits users running Home Assistant, Portainer, or other home automation platforms who want to incorporate Wyze cameras without vendor lock-in. It works well for those building custom NVR setups or integrating cameras with MQTT-based home systems. The tool is distributed as a Docker image and Home Assistant add-on, making deployment straightforward for users already operating containerized infrastructure.

Development activity shows consistent engagement with the codebase. The project receives regular updates addressing user-reported issues and adding refinements to streaming protocol support. Pull requests are reviewed and merged at a steady pace, indicating active maintenance. The maintainer responds to issues and incorporates community feedback into the tool's evolution. Documentation is kept current alongside code changes, reflecting an organized approach to project stewardship.