search

mrlt8 / docker-wyze-bridge

WebRTC/RTSP/RTMP/LL-HLS bridge for Wyze cams in a docker container
GNU Affero General Public License v3.0
2.7k stars 176 forks source link

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

Open stievenkowalski opened 6 months ago

stievenkowalski commented 6 months ago

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 commented 6 months ago

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

nhadler commented 6 months ago

Also having this issue on installing 2.9

mrlt8 commented 6 months ago

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 commented 6 months ago

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

richh1 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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