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

Docket Wyze Bridge 2.9.0 - Go to configuration does not match regular expression [a-zA-Z0-9]{60}. #1188

Open
stievenkowalski opened this issue May 12, 2024 · 7 comments

Comments

@stievenkowalski
Copy link

After upgrading to 2.9.0 I'm unable to start Wyze Bridge. I'm getting error "Go to configuration does not match regular expression [a-zA-Z0-9]{60}." I try to edit configuration, and I'm getting error given below.

Failed to save add-on configuration, does not match regular expression [a-zA-Z0-9]{60}. Got {'ENABLE_AUDIO': True, 'ON_DEMAND': True, 'WB_AUTH': True, 'MOTION_API': True, 'MQTT_DTOPIC': 'homeassistant', 'CAM_OPTIONS': [], 'WYZE_EMAIL': 'xaxaxaxaxa@gmail.com', 'WYZE_PASSWORD': 'xaxaxaxaxa', 'NET_MODE': 'ANY', 'SNAPSHOT': 'RTSP30', 'SUBSTREAM': False, 'MFA_TYPE': 'Email', 'API_KEY': 'xaxaxaxaxa', 'API_ID': 'xaxaxaxaxa'}

Btw. How to setup up Authentication for the webUI and streams? I'm running only Wyze Pan Cam v3.

@GraceANDahalf
Copy link

GraceANDahalf commented May 13, 2024

Had the same issue - reinstalled the app which reset the config, fixing the issue once I reconfigured.

@nhadler
Copy link

nhadler commented May 13, 2024

Also having this issue on installing 2.9

@mrlt8
Copy link
Owner

mrlt8 commented May 13, 2024

hmm, can you make sure you didn't accidentally swap the key and id (API_KEY should be longer one)?
Also make sure your API_KEY doesn't have any special characters

@rspierenburg
Copy link

I just removed the API information I had inputted recently and it started up no problems.

@richh1
Copy link

richh1 commented May 14, 2024

After I upgraded to 2.91 I was having the issue reported here; was working fine before the upgrade. I copied the API Key and Key ID to a txt file and realized there was a space at the beginning of each. I removed the space and copied back to the configuration and saved. It started fine then.

@rsissons
Copy link

After I upgraded to 2.91 I was having the issue reported here; was working fine before the upgrade. I copied the API Key and Key ID to a txt file and realized there was a space at the beginning of each. I removed the space and copied back to the configuration and saved. It started fine then.

This was it. for some reason after the upgrade, it put a space before both API Key and Key ID. I just removed the space at the beginning of each and it saved and started.

mrlt8 added a commit that referenced this issue May 17, 2024
@mrlt8
Copy link
Owner

mrlt8 commented May 17, 2024

Thanks @richh1! I've updated the regex to ignore any whitespaces in the key or id!

mrlt8 added a commit that referenced this issue May 17, 2024
* Tweak AV sync and ffmpeg cmd #1175 #1196 #1194 #1193 #1186

* Catch AccessTokenError

* don't drop timestamp #1175 #1196 #1194 #1193 #1186

* Don't use_wallclock_as_timestamps  #1175 #1196 #1194 #1193 #1186

* keep audio in sync #1175 #1196 #1194 #1193 #1186

* Ignore whitespaces in api key/id #1188

* Remove quotes from credentials #1158

* HA Add FORCE_FPS option #1161

* FORCE_FPS option for all cameras #1161

* changelog
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

7 participants