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

Environment variables ignored #1221

Open
1 of 3 tasks
fromlions opened this issue May 21, 2024 · 2 comments
Open
1 of 3 tasks

Environment variables ignored #1221

fromlions opened this issue May 21, 2024 · 2 comments

Comments

@fromlions
Copy link

fromlions commented May 21, 2024

Describe the bug

On Synology NAS in Container Manager, the environment variables I've set for the container don't appear to be used by wyze-bridge.
I noticed I have to fill out all the details I pass in the docker compose file (wyze username and password, api id and key) when I access the web ui. It also ignores the values I set for WB_USERNAME and WB_PASSWORD, as the RTSP address seems to contain the default username and pass.

The only values it appears to use are WB_IP, WB_AUTH, WB_HLS_URL and WB_WEBRTC_URL.

Running docker exec wyze-bridge env returns a list of all the environment variables I've set, including the ones being unused. So I'm sure I've set them correctly.

Environment (if applicable)

  • Affected Bridge Version:2.9.2
  • Bridge type:
    • Docker Compose/Docker Run
    • Home Assistant
    • Other
@mrlt8
Copy link
Owner

mrlt8 commented May 22, 2024

Anything in the logs related to the login when starting the container?

As for the rtsp streams, you can change the stream API key with WB_API, however, it will still use the default wb user name.

Another option is to manually override the credentials, but keep in mind that these may not reflect in the web-ui:

      - MTX_PATHS_ALL_READUSER=username
      - MTX_PATHS_ALL_READPASS=password

@fromlions
Copy link
Author

I restarted the container and checked the logs. It says it uses the auth from the local cache. Does that refer to the cache of the container itself? Because in that case I'm not sure how to clear that and see what it says when I restart after clearing it.

Oh my bad about the RTSP streams, I thought it would inherit the WB_USERNAME and WB_PASSWORD

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

2 participants