Replies: 1 comment 1 reply
|
I know it's a little confusing, but some users were running the bridge with ports open, so I've set If you're running the bridge completely local, then you can set You can change the web ui login with 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. More info on the 2.9.0 release page: https://github.com/mrlt8/docker-wyze-bridge/releases/tag/v2.9.0 |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Finally booted up the DWB PC at new house - only got the wyze db cam now. Got the wyze api id and key, fixed up yml file, pulled latest 2.9.2 - bingo, all working well. Web ui did ask for login even with the api id and key which only worked with my wyze username and pw - curious if the wb auth stuff replaces the need to use the wyze login? like we can set our own login credentials?
Also, for some reason I am not seeing any log, stats show activity, and running on LAN is fine since I can log into web ui from any PC/device, just odd no log. Don't recall anything to turn log on or off in the past.
All reactions