Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Credentials for snapshot via http requires wb_password, but stream requires wb_api #1199

Closed
mgrimace opened this issue May 15, 2024 · 6 comments

Comments

@mgrimace
Copy link

Describe the bug

When my still image url is http, for example http://IP:5000/img/wyze-doorbell.jpg and the stream is RTSP, for example rtsp://IP:8554/wyze-doorbell then I can enter credentials for one or the other, but not both in something like Home Assistant. Specifically, the stream credentials are user: wb, and password wb_api, while the snapshot/http password is web_auth user and password.

I have DWB as a container via docker compose and home assistant containerized as well, and access my cameras via the generic camera plugin. I cannot enter both my api credentials and my web auth credentials in this setup.

Environment (if applicable)

  • Affected Camera(s): n/a
  • Affected Camera Firmware: n/a
  • Affected Bridge Version: v2.91
  • Bridge type:
    • [ x ] Docker Compose/Docker Run
@mrlt8
Copy link
Owner

mrlt8 commented May 15, 2024

I still need to update the documentation, but you should be able to pass the API key as a query parameter eg:

http://localhost:5000/snapshot/<cam-name>.jpg?api=mywb_apikey

@mgrimace
Copy link
Author

I still need to update the documentation, but you should be able to pass the API key as a query parameter eg:

http://localhost:5000/snapshot/<cam-name>.jpg?api=mywb_apikey

Worked, thanks! As it is, v2.91 is 100% working for me on original doorbell and v1 floodlight, with home assistant and also scrypted+homekit secure video. Thanks for all your work on this!

@jak83A
Copy link

jak83A commented May 19, 2024

@mrlt8 i have tried this with http://homeassistant.local:5000/snapshot/<cam-name>.jpg?api=mywb_apikey
(mywb_api_key being the wyze API Key obtained from the developer portal).

In the browser i am redirected to the login page of the Web UI to enter the credentials.

@jak83A
Copy link

jak83A commented May 19, 2024

@mrlt8 i have tried this with http://homeassistant.local:5000/snapshot/<cam-name>.jpg?api=mywb_apikey (mywb_api_key being the wyze API Key obtained from the developer portal).

In the browser i am redirected to the login page of the Web UI to enter the credentials.

Ok i see my mistake is that is should use the wyze bridge API key, not the authentification seems to go through, hoe ever i get now a "Preview not available" Screen http://homeassistant.local:5000/static/notavailable.svg

The Cam Model is: HL_PAN3

@mrlt8
Copy link
Owner

mrlt8 commented May 19, 2024

@jak83A You'll usually get redirected to the not available image if it fails or times out to take a snapshot.
Do you see anything in the logs for the bridge?

@jak83A
Copy link

jak83A commented May 20, 2024

@mrlt8 i found the "problem": while wyze sdk shows camera names with whitelists with underscores: "my home cam 1" -> "my_home_cam_1", the required format in the snapshot http call is "myhomecam1". Thank you for trying to help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants