search

DoganM95 / Ewelink-Rest-Api-Server

Server-code accepting http requests to control ewelink devices
MIT License
4 stars 3 forks source link

Authentication failed #11

Open mdlaat opened 1 year ago

mdlaat commented 1 year ago

Thank you very much for this work!

I am having a hard time to get the authentication right. I am using the same username (my mailadres) and password as I am using to log in to the ewelink app. I am in the Netherlands, and have set the region to "eu"

When starting, I see an error in the docker log: Authentication failed. The application will continue and respond with the error message, to make sure you are informed.

I am in doubt of the right region, so i also tried "nl". In that case I get a docker log error: FetchError: request to https://nl-api.coolkit.cc:8080/api/user/login failed, reason: getaddrinfo ENOTFOUND nl-api.coolkit.cc

Which makes me think my eu region is correct.

Should I use the same credentials as using in the ewelink app?

Kind regards

sharinganthief commented 1 year ago

also getting this

DoganM95 commented 1 year ago

Hi, thanks for contacting me on this. was able to replicate it, will try to fix it soon.

your region "eu" should be fine. And yes, it needs the same username & password that you use in your ewelink app. The authorization needs to be a bearer token, containing your hashed data as you probably know.

DoganM95 commented 1 year ago

Just checked everything, seems like these guys switched to a new auth mechanism (OAuth). Will add that soon and update this project. what you guys can do meanwhile is following these steps, to create an "ewelink developer account", which seems to be necessary from now on.

find the instructions here: https://github.com/coolkit-carl/eWeLinkOAuthLoginDemo#readme

mdlaat commented 8 months ago

So I created an ewelink developer account and an app. Filled in redirecturl: http://127.0.0.1:3000/redirectUrl and got an appid and secret. But it is still unclear to me where to fill this appid & secret. Any help appreciated.