Thanks @tiboys I just saw, but indeed @ProtZ is right, the library is no longer functional, the conclusion on the topic you quote is:
So in summary - its time to give up trying to make this project work (as it uses the old v1 endpoints and an outdated method of connection with a password stored in plain text in your code) and move to the meow common and more secure OAuth2.0 authorisation flow with the resultant token to use as a bearer token in future requests.
Even the lib « ewelin-api-next » apparently isn’t functional:
There is « start » of such a project at « ewelink-api-next » but it’s completely missing the OAuth stuff according to the TODO list and even I was unable to make it actually control my devices.
Unfortunately there is therefore no bug on Gladys’s side to fix, what I see is:
- First, deprecate the current integration with a message to warn users to avoid frustrations like this.
- See if an integration is feasible with the new API; there’s not necessarily a need to wait for a new Node lib, it could be an integration we build ourselves with the Ewelink REST API. I don’t know if you want to take that on @ProtZ?
