400 client error #1158
Comments
|
Just updated to 2.8 and getting the same thing, i roll back to 2.5 and it works. not sure whats happening. |
|
2.8.1 same here... i have fresh data set to true? do i need to remove my password and login now and use the page to login? i even had the auth token at one point but found it annoying. and now when i rollback to 2.6.0 same error. its borked the install. reverting to any same result |
|
Also tried changing password to not have any special characters in it, as a previous post on an older version was the same issue with special characters, no effect on the 2.8.1 : 400 client error. but i can make 2.5.3 work without an issue. |
|
i've been using 2.6.0 for the last two months without issue when the 2.7.0 lag issue was present. i decided today to try 2.8.1 and now i can't get any to work. 2.5.3 has same issue for me |
|
well this sucks. 2.6.0 was running fine. took the risk. now nothing works. same issue for every single version. |
|
maybe i'm just uniquely screwed. installed in home assistant which i have never used before and same issue.... no special characters. also when i try to sign in via auth website |
|
Hmm. I'll have to look into this. Potentially related to the new Wyze app update they just pushed out and #1000. As a temporary solution, you may need to supply your own API ID and KEY. See https://github.com/mrlt8/docker-wyze-bridge/wiki/Two-Factor-Authentication#wyze-api-keyid |
BINGO BANGO!!! i was correct, i was uniquely screwed. this did fix the issue. are password and username still required in the docker template? seems with api keys and unique id's it should not be, but i left them. i wonder if this will be required going forward? thanks again! glad to see you are back. edit: 2.8.1 seems to be running just fine also. i don't use audio so can't attest to that, but otherwise all cams streaming. |
|
Yes, you still need to supply the email and password when using the API key/id. |
mrlt8
added
bug
|
Thank you, I was having this issue too importing HA from a backup (migrated from RPI4 to Synology NAS). I initially thought updating from 2.7 to 2.8 was the issue but it was just the missing API in the config. |
|
Sweet timing @mrlt8 |
|
I'm still not sure if this is a temporary service issue with the Wyze servers or if they're block all non-oauth based logins now. |
|
|
|
Appears to be working again. Possibly just an issue on Wyze end |
|
adding the API keys fixed my issue as well. thanks! |
|
2.6.0 just stopped working for me today when I went to restart the bridge cause my cams were starting to lag. |
|
Just built my first Wyze bridge on a Synology. Running 2.8.1. Ran into this problem immediately, that nice Mr Google brought me here, had to get an API key to make it work. |
|
API Key worked for me as well. I see a couple of you said it was working again a few days ago. But definitely down again for me this morning (first time I have noticed it - but I also don't use it that often). |
|
Down for me today. Was on 2.5.3. Upgraded to 2.8.1 and still a problem. I do not use 2FA, simple longin. Wyze App still works. **** UPDATE **** API work around worked fine - even with no 2FA in both 2.5.3 & 2.8.1 Since this is first time using API Keys - it seems now I have to go to the Wyze Bridge WebUI everytime I restart the bridge docker to login - that kinda sucks **** UPDATE **** Don't be stupid like me - if you do not use 2FA and switch to API Keys - you can leave the login creds there and when it restarts you will not have to use the WebUI as I mistakenly did - doh! |
|
I replicate this error on 2.6/2.7/2.8 and can confirm setting an api key successfully works around the issue. |
|
I'm getting the error on 2.8.1 even with an API key |
|
@karcaw did you set the API key and API ID as well? |
|
API Key/ID worked for me too. Would load in but not show cameras otherwise. CMD showed the api login error stated earlier. |
|
Yes, I have email, password, api_id, and api_key all set. |
|
Adding the API Key and ID fixed it for me thanks @mrlt8! |
|
Hi! Just ran into this problem myself: root@ASUSET2410-Ubuntu:/home/ron/docker-wyze-bridge# docker run -p 8554:8554 -p 8888:8888 -p 5000:5000 -e ENABLE_AUDIO=True mrlt8/wyze-bridge & 🚀 DOCKER-WYZE-BRIDGE v2.8.1 X86_64 [WyzeBridge] [WARN] Credentials are NOT set
Then I log into the server dashboard with username and password: [WyzeBridge] 192.168.1.248 - - [27/Apr/2024 07:39:49] "GET /login HTTP/1.1" 200 - I see this message on the web dashboard: Wyze credentials required to complete authentication. How/where do I find api_id, and api_key? UPDATE: I found where to generate the api_id and api_key: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key New question: How do I add it to this command? docker run -p 8554:8554 -p 8888:8888 -p 5000:5000 -e ENABLE_AUDIO=True mrlt8/wyze-bridge & I just need to know what my new process is for getting the bridge up and running. Up until now, all I did was enter the above. And, I don't get anything in the Web UI to enter API or MFA info. |
|
With the api keys generated (not sure if it is supposed to be in yaml format or not) I am still not able to get it to work. Stopped working 20240425. 🚀 DOCKER-WYZE-BRIDGE v2.8.1 X86_64 [WyzeBridge] 🔍 Could not find local cache for 'auth'
Granted I realize the auth-pro.api.wyze.com is not working when going to that address directly. I did get a json payload link to the api when removing the v3 from the link. |
|
I'm still getting this error. I just loaded up the add on today. I've got 3 V3 and a V2. I can see them in the wyze app and login credentials work through the app and logging in to the Wyze account on Safari. This is my configuration, I tried the API method, generated one about 10min after initial install. Some of the V3 may have had the RTSP firmware on them from previously (about a year ago) but there is definitely one V3 camera that is brand new, doesn't even have an SD card in it from about 3 weeks ago. Nothing is detected. I'm running HAOS directly on a minipc (Kamrui device that I loaded HAOS directly onto through Ubuntu). WYZE_EMAIL: MYEMAIL
This is the error I consistently get in the log [WyzeBridge] 🏠 Home Assistant Mode 🚀 DOCKER-WYZE-BRIDGE v2.8.1 X86_64 [WyzeBridge] 🔍 Could not find local cache for 'auth'
I used to get this But since I tried the API method that doesn't happen as much. If I click refresh a few times it'll happen again with the v3/user/login error. |
I still have the same problem, what I did is with YAML editor, I don’t see anything wrong, thanks for your help: WYZE_EMAIL: myemail
|
|
Following and getting this error. This has been working well for a long time but recently had to reboot my server which hosts the this container. Credentials were all I had in config previously but after reading up on issues I created and added an API key. Not seeing any cameras.
|
|
@rw377 Did you add the API and key to your config? You have them commented out in
your screenshot.
…On Sat, Apr 27, 2024, 21:43 rw377 ***@***.***> wrote:
Following and getting this error. This has been working well for a long
time but recently had to reboot my server which hosts the this container.
Credentials were all I had in config previously but after reading up on
issues I created and added an API key. Not seeing any cameras.
?? DOCKER-WYZE-BRIDGE v2.8.1 X86_64
[WyzeBridge] ?? Could not find local cache for 'auth'
[WyzeBridge] ?? Fetching 'auth' from the Wyze API...
* Serving Flask app 'frontend'
* Debug mode: off
[WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on all addresses (0.0.0.0)
* Running on http://127.0.0.1:5000
* Running on http://172.24.0.2:5000
[WyzeBridge] Press CTRL+C to quit
[WyzeBridge] ?? 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
[WyzeBridge] ?? Could not find local cache for 'user'
[WyzeBridge] ?? Fetching 'user' from the Wyze API...
[WyzeBridge] ?? Could not find local cache for 'auth'
[WyzeBridge] ?? Fetching 'auth' from the Wyze API...
[WyzeBridge] ?? 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
image.png (view on web)
<https://github.com/mrlt8/docker-wyze-bridge/assets/75325891/eed9d1d9-d4ca-4f99-a583-16e97d6821b5>
version: '2.4'
services:
wyze-bridge:
container_name: wyze-bridge
restart: unless-stopped
image: mrlt8/wyze-bridge:latest
ports:
- 1935:1935 # RTMP
- 8559:8554 # RTSP
- 8888:8888 # HLS
- 8889:8889 #WebRTC
- 8189:8189/udp # WebRTC/ICE
- 5000:5000 # WEB-UI
environment:
# [OPTIONAL] (Can be set in the WebUI):
- WYZE_EMAIL=myEmail
- WYZE_PASSWORD=myPass
# [OPTIONAL] IP Address of the host to enable WebRTC e.g.,:
# - WB_IP=192.168.1.122
# [OPTIONAL] Wyze API credentials:
# - API_ID=myID
# - API_KEY=myKey
—
Reply to this email directly, view it on GitHub
<#1158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZ2EZA5CMSR63XWVOEUDDY7RH2NAVCNFSM6AAAAABGTU7Q6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGI4DIMBQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm so dumb! You're a legend, that worked (of course). Thank you so much. |
Have you had success? Mine isn’t working despite my best efforts |
UPDATE********* |
|
I've included API Key and API id with YAML editor (maintaining user and password) and can not log in. I don't know what I'm doing wrong. I'm not using docker, is HA OS. I'll try to reset HA server. |
OH MY GOD YOU BEAUTY! This has worked!!!! Legend, thank you! |
|
@SomebodySysop something like: |
|
@ManuelAstro See what @dedblank posted:
|
Thanks so much!! with this unused optional configuration options, it worked!! |
If I might suggest, since these items are now required, according to the post on the wyze site (I believe it was directed towards this project specifically), that the key id and api key are required in the next revision. |
Thank you @mrlt8! I actually got it to work by putting the api id and key into the yml environment as suggested, and I accidently got docker to run and load it. Still don't actually know how I did it. But, for some reason, when it runs from the yml, it has a tendency to stop and has to be restarted pretty consistently. The above command works best for me as once I log into the web ui, it runs continuously. Again, many thanks for the update! |
This doesn't work for me. Was there anything else that needed to be done? I added the API_KEY and API_ID environment variable to Dockerman but still get the 400 client error in the logs. |
That is what I am using. I've been meaning to get the template updated for Community Apps but honestly have no idea how to submit a pull request. I've added in several things since the early days. I'd be happy to share my template. |
I'm on unRAID, and all I did was add those variables, too. Worked fine. |
|
Is there anything I can do to update the unRAID configs? I believe we already have the API key/ID variables in the example: https://github.com/mrlt8/docker-wyze-bridge/blob/main/unraid/docker-wyze-bridge.xml |
|
the community apps would need to update the template. it affects first time users who actually get the template from Community Apps. once installed the template lives on the server unless you manually delete the xml file, or install a second instance with a different name. this is what he current template from community apps looks like to the end user, and above i linked to the previous discussion about updating the template. so it does need an update with the API key addition at a minimum. you have massive amount of options available for the docker itself. if i shared mine it'd be even longer than your updated one. a little bit of knowledge needs to come into play for the user though. Like how to add variables, paths, extra-parameters. the unraid forum should help with this aspect. your guides are sufficient on options available. the template you shared is overkill in my opinion, but fine since users can remove options they don't use. Getting up, running and connected should be sufficient for a template to get users started. they should be able to add, remove variables for different things after they establish it connects and can get streams. |
|
I made a pull request with an updated template: selfhosters/unRAID-CA-templates#488 |
sounds good. thank you, that should help some people get api keys, etc, figured out. |
|
My issue is fixed now, I had quotes around my username and password, once I removed them, it started working properly. |
* 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
and others
Resarted the server and this is the error I am now getting
[WyzeBridge]⚠️ 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/v3/user/login
The text was updated successfully, but these errors were encountered: