v2.9.5

What's Changed in v2.9.5

• POTENTIALLY BREAKING: The bridge will now use PCMU/8000 as the default audio codec when the camera does not provide an RTSP/WebRTC-compatible audio format. This change should enhance compatibility with various NVR systems like Surveillance Station which do not support opus. Thanks @Dot50Cal!
  • To use a different audio codec, set the desired codec in the AUDIO_CODEC environment variable.
• Always re-encode aac_eld (Wyze Cam v4) even when WebRTC is not enabled (#1236) Thanks @Dot50Cal!
• HOME ASSISTANT: Disable MQTT from automatically setting up by setting MQTT_DTOPIC to something other than homeassistant (#1232)

v2.9.4

What's Changed in v2.9.4

• Adjust AV sync issue/delay when audio is enabled. (#1231) Thanks @delmlund!

v2.9.3

What's Changed in v2.9.3

• FIX: Clear the retain flag from MQTT Discovery which was causing commands to be resent to the bridge on startup for some users. (#1182)
• Ignore commands when connection is stopping.

v2.9.2

What's Changed in v2.9.2

• Improved video connection stability and audio sync. #1175 #1196 #1194 #1193 #1186 Thanks @vipergts450!
• FIX: Remove quotes from credentials #1158
• NEW: FORCE_FPS option for all cameras #1161
• Home Assistant: Add FORCE_FPS option #1161
• Home Assistant: Ignore whitespaces in api key/id #1188 Thanks @richh1!

v2.9.1

What's Changed in v2.9.1

• FIX: Setting bitrate higher than 255 would not report correctly (#1185) Thanks @Anc0dia!
• FIX: Wrong bitrate for HL_CFL2 (#1112) Thanks @dreondre!
• FIX: Could not set values with the REST API when WB_AUTH is enabled.(#1189) Thanks @kiwi-cam!
• NEW: api header authentication option for the RES API when WB_AUTH is enabled:
  • -H "api: MyWbApiKey"

What's Changed in v2.9.0

Important

WebUI and stream authentication will be enabled by default to prevent unintentional access.

Default Authentication

• To disable default authentication, set WB_AUTH=False explicitly.
• Note that all streams and the REST API will necessitate authentication when WB_AUTH is enabled.

WebUI Authentication

• If WB_USERNAME and WB_PASSWORD are not set, the system will try to use WYZE_EMAIL and WYZE_PASSWORD.
• In case neither sets of credentials are provided, the username will default to wbadmin with a randomly generated WB_PASSWORD, which will be logged and stored in a wb_password file within the tokens directory.
• Credentials are case sensitive.

Stream and REST API Authentication

• A unique API key will be accessible at the bottom of your WebUI and saved to a wb_api file in your tokens directory.
  • For persistence, ensure to set the WB_API environment variable or volume mount the /tokens directory.
• REST API will require an api query parameter.
  • Example: http://localhost:5000/api/<camera-name>/state?api=<your-wb-api-key>
• Streams will also require authentication.
  • username: wb
  • password: your unique wb api key

FIXES

• Wrong file permission caused errors for non-root. (#1174) Thanks @GiZZoR!
• Fix MOTION_API when substreams were enabled. (#1125) Thanks @kiwi-cam!
• Changing FPS and FORCE_FPS were broken (#1161) Thanks @jarrah31!
• Dropped frame issue when camera is falling behind. (#1167) Thanks @34t614t1254y!

NEW

• Token based wyze authentication from WebUI. See wiki.
• Remove 255 limit from QUALITY. Can now go as high as your network can handle. e.g. - QUALITY=HD8000
• Update snapshot with MOTION_API and push to mqtt (#709) (#970)
• Additional headers for MOTION_WEBHOOKS.
• OFFLINE_WEBHOOKS will send a POST request when the bridge cannot connect to a camera because it is offline. Replaces ifttt_webhook.

POTENTIALLY BREAKING

• CHANGES: MOTION_WEBHOOKS now makes a POST request instead of a GET request.
• CHANGES: MOTION_WEBHOOKS includes the event timestamp in the message body which may require you to adjust the timezone for your container with the TZ environment.
• REMOVED: ifttt_webhook as webhooks are no longer free with IFTTT.
• CHANGED: Renamed WebUI authentication related ENV options:
  • WEB_AUTH -> WB_AUTH
  • WEB_USERNAME -> WB_USERNAME
  • WEB_PASSWORD -> WB_PASSWORD

HOME ASSISTANT

• Login with API Key/ID or existing token via Ingress/WebUI.
• Config now uses yaml instead of json.
• Credentials are now optional to allow for WebUI based login, but it is still recommended to set them under advanced options.

v2.9.0

What's Changed in v2.9.0

Important

WebUI and stream authentication will be enabled by default to prevent unintentional access.

Default Authentication

• To disable default authentication, set WB_AUTH=False explicitly.
• Note that all streams and the REST API will necessitate authentication when WB_AUTH is enabled.

WebUI Authentication

• If WB_USERNAME and WB_PASSWORD are not set, the system will try to use WYZE_EMAIL and WYZE_PASSWORD.
• In case neither sets of credentials are provided, the username will default to wbadmin with a randomly generated WB_PASSWORD, which will be logged and stored in a wb_password file within the tokens directory.
• Credentials are case sensitive.

Stream and REST API Authentication

• A unique API key will be accessible at the bottom of your WebUI and saved to a wb_api file in your tokens directory.
  • For persistence, ensure to set the WB_API environment variable or volume mount the /tokens directory.
• REST API will require an api query parameter.
  • Example: http://localhost:5000/api/<camera-name>/state?api=<your-wb-api-key>
• Streams will also require authentication.
  • username: wb
  • password: your unique wb api key

FIXES

• Wrong file permission caused errors for non-root. (#1174) Thanks @GiZZoR!
• Fix MOTION_API when substreams were enabled. (#1125) Thanks @kiwi-cam!
• Changing FPS and FORCE_FPS were broken (#1161) Thanks @jarrah31!
• Dropped frame issue when camera is falling behind. (#1167) Thanks @34t614t1254y!

NEW

• Token based wyze authentication from WebUI. See wiki.
• Remove 255 limit from QUALITY. Can now go as high as your network can handle. e.g. - QUALITY=HD8000
• Update snapshot with MOTION_API and push to mqtt (#709) (#970)
• Additional headers for MOTION_WEBHOOKS.
• OFFLINE_WEBHOOKS will send a POST request when the bridge cannot connect to a camera because it is offline. Replaces ifttt_webhook.

POTENTIALLY BREAKING

• CHANGES: MOTION_WEBHOOKS now makes a POST request instead of a GET request.
• CHANGES: MOTION_WEBHOOKS includes the event timestamp in the message body which may require you to adjust the timezone for your container with the TZ environment.
• REMOVED: ifttt_webhook as webhooks are no longer free with IFTTT.
• CHANGED: Renamed WebUI authentication related ENV options:
  • WEB_AUTH -> WB_AUTH
  • WEB_USERNAME -> WB_USERNAME
  • WEB_PASSWORD -> WB_PASSWORD

HOME ASSISTANT

• Login with API Key/ID or existing token via Ingress/WebUI.
• Config now uses yaml instead of json.
• Credentials are now optional to allow for WebUI based login, but it is still recommended to set them under advanced options.

v2.8.3

What's Changed in v2.8.2/3

• Add support for developer API Key/ID for WebUI based logins.
• Update Home Assistant and unraid config to support API Key/ID
• Refactor to catch additional WyzeAPIErrors.

v2.8.1

What's Changed in v2.8.1

• Fix video lag introduced in v2.7.0
• Add aac_eld audio support for V4 cams (HL_CAM4).
• Add 2k resolution support for Floodlight V2 cams (HL_CFL2).
• fix version number

Home Assistant:

• Add dev and previous builds (v2.6.0) to the repo.
• Note: you may need to re-add the repo if you cannot see the latest updates.

Full Changelog: v2.7.0...v2.8.1

v2.7.0

What's Changed in v2.7.0

• Audio sync - bridge will now try to make minor adjustments to try to keep the video and audio in sync Thanks @carlosnasillo and everyone who helped with testing! (#388).
• Refactor for compatibility with Scrypted. Thanks @koush (#1066)
• Use K10050GetVideoParam for FW 4.50.4.x (#1070)
• Fix jittery video in Firefox (#1025)
• Retain MQTT Discovery Message Thanks @jhansche! (#920)

Home Assistant:

• Now uses addon_config instead of config Additional info
  • May need to cleanup old config manually.
• Reset alarm/siren state (#953) (#1051)

v2.6.0

What's Changed in v2.6.0

• NEW: ARM 64-bit native library (#529 #604 #664 #871 #998 #1004)

  The arm64 container now runs in 64-bit mode, addressing compatibility issues, particularly on Apple Silicon M1/M2/M3, when using the Home Assistant Add-on.

  Resolves issues on the Raspberry Pi 4/5 running the 64-bit version of Raspbian.

• Update: Python 3.11 -> Python 3.12