Skip to content

v2.9.1
Compare
Choose a tag to compare
@mrlt8 mrlt8 released this 13 May 15:10
· 33 commits to main since this release
v2.9.1
ae31b2d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

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.

Contributors

dreondre, jarrah31, and 4 other contributors
Assets 2