Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Authentication error #19

Open
sysonebr opened this issue Dec 10, 2021 · 14 comments
Open

Authentication error #19

sysonebr opened this issue Dec 10, 2021 · 14 comments

Comments

@sysonebr
Copy link

Anyone else has trouble on authenticate on https://www.weback-login.com/WeBack/WeBack_Login_Ats_V3

Always return fail... they change something?

@Jezza34000
Copy link

No problem. You may use bad authentication information.
Take care about login who need to be like this : +33-myemail@mail.com
+33 is your country code

@sysonebr
Copy link
Author

Already check the login... it's correct... I create a test account, in app works fine, but on api keeps getting fail

curl --location --request POST 'https://www.weback-login.com/WeBack/WeBack_Login_Ats_V3'
--header 'Content-Type: application/json'
--data-raw '{
"App_Version": "android_3.9.3",
"Password": "09134b78b78ab5f22a16781758d3ccb6",
"User_Account": "+55-testweback@sysone.com.br"
}'

Region: Brazil - +55
Email: testweback@sysone.com.br
password: weback1234

@GeorgKlaussner
Copy link

GeorgKlaussner commented Jan 6, 2022

I'm trying to auth with Tesvor X500, but iam not able connect. Password or username incorrect. I double checked via weback app and also tried a telephone number instead of email. Any clues what I can do?

@mattes66
Copy link

I had the same issue, but solution was easy. I just hadn't updated my client.py and hence missed the change, Tim made last year exactly for this error "CERTIFICATE_VERIFY_FAILED".

@GeorgKlaussner
Copy link

So what needs to be changed? Sorry for my dumb question.

@mattes66
Copy link

Hello Georg,
I don‘t know your own setup using the module. I have a main program based on vacuum.py with my own modifications. This uses the class WebackApi from the file weback_unofficial/client.py. I only replaced my old client.py file with the updated one out of the repository. And I use my phone number as user to login in form +49-015…….. hope this helps

@GeorgKlaussner
Copy link

Iam using latest. Tried with email and phone number (also germany +49). But iam always getting the authentification error.

@mattes66
Copy link

my last idea: check your Python environment regarding SSL certification
pip3 install certifi --upgrade

@GeorgKlaussner
Copy link

thats already satisfied. Does the example from sysonebr work on your side?

@GeorgKlaussner
Copy link

GeorgKlaussner commented Feb 7, 2022

I found a github site saying api has changed.

curl --location --request POST 'https://user.grit-cloud.com/oauth' --header 'Content-Type: application/json' --data-raw '{"payload":{"opt":"login","pwd": "PW HASH"},"header":{"language":"de","app_name":"WeBack","calling_code":"COUNTRY CODE e.g 0049","api_version":"1.0","account":"EMAIL OR TEL","client_id":"yugong_app"}}'

this worked for me and i got a positive response.
marcelkordek/homebridge-tesvor#4 (comment)

@tokra
Copy link

tokra commented Mar 23, 2022

I found a github site saying api has changed.

curl --location --request POST 'https://user.grit-cloud.com/oauth' --header 'Content-Type: application/json' --data-raw '{"payload":{"opt":"login","pwd": "PW HASH"},"header":{"language":"de","app_name":"WeBack","calling_code":"COUNTRY CODE e.g 0049","api_version":"1.0","account":"EMAIL OR TEL","client_id":"yugong_app"}}'

this worked for me and i got a positive response. marcelkordek/homebridge-tesvor#4 (comment)

Anyone has some V4 api docs or some example ? thank you!

@Jezza34000
Copy link

I've rewrite a plugin to use the new API.
But it's for Jeedom, not HomeAssistant.
If you want to see how to use new API check my repo : Jezza34000/Weback
New API does not use HTTPS anymore to send command it use WSS and it make architecture completely different.

@GeorgKlaussner
Copy link

Did anyone found a documentation or a fix?

@tokra
Copy link

tokra commented May 8, 2022

@GeorgKlaussner there is no fix, new api isnt backward compatible, and u need to register to new api. old login wont work with new api, i tried in my nodejs app. also all devices u had registered wont be accessible in new api, you need to register them again.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants