Create a local WebRTC, RTSP, RTMP, or HLS/Low-Latency HLS stream for most of your Wyze cameras including the outdoor, doorbell, and 2K cams.

No modifications, third-party, or special firmware required.

It just works!

Streams direct from camera without additional bandwidth or subscriptions.

Based on @noelhibbard's script with kroo/wyzecam and bluenviron/mediamtx.

Please consider ⭐️ starring or ☕️ sponsoring this project if you found it useful, or use the affiliate link when shopping on amazon!

See the supported cameras section for additional information.

Install docker and run:

docker run -p 8554:8554 -p 8888:8888 -p 5000:5000 mrlt8/wyze-bridge

You can then use the web interface at http://localhost:5000 where localhost is the hostname or ip of the machine running the bridge.

The default login for the WebUI will be:

username: wbadmin
password: <username portion of your wyze email>

Example: For the wyze email [email protected], the default password would be myEmail123.

See basic usage for additional information or visit the wiki page for additional information on using the bridge as a Home Assistant Add-on.

FIXED: Could not disable WB_AUTH if WB_API is set. (#1304)

Simplify default credentials for the WebUI:

• This will not affect users who are setting their own WB_PASSWORD and WB_API.
• Default WB_PASSWORD will now be derived from the username part of the Wyze email address instead of using a randomly generated password.
  • Example: For the email address [email protected], the WB_PASSWORD will be john123.
• Default WB_API will be based on the wyze account for persistance.

NEW: STREAM_AUTH option to specify multiple users and paths:

• Username and password should be separated by a :
• An additional : can be used to specify the allowed IP address for the user.
  • This does NOT work with docker desktop
  • Specify multiple IPs using a comma
• Use the @ to specify paths accessible to the user.
  • Paths are optional for each user.
  • Multiple paths can be specified by using a comma. If none are provided, the user will have access to all paths/streams
• Multiple users can be specified by using | as a separator

EXAMPLE:

STREAM_AUTH=user:pass@cam-1,other-cam|second-user:password@just-one-cam|user3:pass

• user:pass has access to cam-1 and other-cam
• second-user:password has access to just-one-cam
• user3:pass has access to all paths/cameras

See Wiki for more information and examples.

Recoding streams has been updated to use MediaMTX with the option to delete older clips.

Use RECORD_ALL or RECORD_CAM_NAME to enable recording.

• RECORD_PATH Available variables are %path or {cam_name}, %Y %m %d %H %M %S %f %s (time in strftime format).
• RECORD_LENGTH Length of each clip. Use s for seconds , h for hours. Defaults to 60s
• RECORD_KEEP Delete older clips. Use s for seconds , h for hours. Set to 0s to disable automatic deletion. Defaults to 0s

View previous changes

• How does this work?
  • It uses the same SDK as the app to communicate directly with the cameras. See kroo/wyzecam for details.
• Does it use internet bandwidth when streaming?
  • Not in most cases. The bridge will attempt to stream locally if possible but will fallback to streaming over the internet if you're trying to stream from a different location or from a shared camera. See the wiki for more details.
• Can this work offline/can I block all wyze services?
  • No. Streaming should continue to work without an active internet connection, but will probably stop working after some time as the cameras were not designed to be used without the cloud. Some camera commands also depend on the cloud and may not function without an active connection. See wz_mini_hacks for firmware level modification to run the camera offline.
• Why aren't all wyze cams supported yet (OG/Doorbell Pro)?
  • These cameras are using a different SDK and will require a different method to connect and stream. See the awesome cryze project by @carTloyal123.

Should work on most x64 systems as well as on most modern arm-based systems like the Raspberry Pi 3/4/5 or Apple Silicon M1/M2/M3.

The container can be run on its own, in Portainer, Unraid, as a Home Assistant Add-on, locally or remotely in the cloud.

This is similar to the docker run command, but will save all your options in a yaml file.

1. Install Docker Compose.
2. Use the sample as a guide to create a docker-compose.yml file with your wyze credentials.
3. Run docker-compose up.

Once you're happy with your config you can use docker-compose up -d to run it in detached mode.

To update your container, cd into the directory where your docker-compose.yml is located and run:

docker-compose pull # Pull new image
docker-compose up -d # Restart container in detached mode
docker image prune # Remove old images

Visit the wiki page for additional information on Home Assistant.

• Camera Commands (MQTT/REST API)
• Two-Factor Authentication (2FA/MFA)
• ARM/Apple Silicon/Raspberry Pi
• Network Connection Modes
• Portainer
• Unraid
• Home Assistant
• Homebridge Camera FFmpeg
• HomeKit Secure Video
• WebUI API

The bridge features a basic Web-UI which can display a preview of all your cameras as well as direct links to all the video streams.

The web-ui can be accessed on the default port 5000:

http://localhost:5000/

See also:

• WebUI page
• WebUI API page

WebRTC should work automatically in Home Assistant mode, however, some additional configuration is required to get WebRTC working in the standard docker mode.

• WebRTC requires two additional ports to be configured in docker:

    ports:
      ...
      - 8889:8889 #WebRTC
      - 8189:8189/udp # WebRTC/ICE

• In addition, the WB_IP env needs to be set with the IP address of the server running the bridge.

    environment:
      - WB_IP=192.168.1.116

• See documentation for additional information/options.

All environment variables are optional.

• Audio
• Bitrate and Resolution
• Camera Substreams
• MQTT Configuration
• Filtering Cameras
• Doorbell/Camera Rotation
• Custom FFmpeg Commands
• Interval Snapshots
• Stream Recording and Livestreaming
• rtsp-simple-server/MediaMTX Config
• Offline/IFTTT Webhook
• Proxy Stream from RTSP Firmware
• BOA HTTP Server/Motion Alerts
• Debugging Options

Video Streaming:

• gtxaspec/wz_mini_hacks - Firmware level modification for Ingenic based cameras with an RTSP server and self-hosted mode to use the cameras without the wyze services.
• carTloyal123/cryze - Stream video from wyze cameras (Gwell cameras) that use the Iotvideo SDK from Tencent Cloud.
• mnakada/atomcam_tools - Video streaming for Wyze v3.

General Wyze:

• shauntarves/wyze-sdk - python library to interact with wyze devices over the cloud.