nareso

Same issue in Japan with core 2024.4.4

Now available again in Japan It only worked for 3 minutes. Currently down again.

Hi carl Thanks for the information. We are facing a problem with my own APPID as https://github.com/skydiver/ewelink-api/issues/220#issuecomment-1676312471 Please tell us how to solve the error that appears when setDevice method.

Correction, sonoff devices also become errors.

I found a temporary workaround. APP_ID: Uw83EKZFxdif7XFXEsrpduz5YyjP7nTl APP_SECRET: mXLOjea0woSMvK9gw7Fjsy7YlFO4iSu6 works for me. Thanks, LiorLindvor. https://github.com/skydiver/ewelink-api/issues/212#issuecomment-1485629138

Hi carl , thanks for your reply. I do not understand the Create application procedure, but how should I describe it in the redirect URL field? By the way, in...

Hi carl, thank you very much for your kind explanation. But, I can't find config.js in ewelink-api directory. Isn't your example for ewelink-api-next? Please tell me the create application procedure...

Hi carl I noticed that the object structure has changed between V1 and V2. For example, an ”off” information of a single switch from node-red-contrib-ewelink are V1 --- msg.payload.params.switch: "off"...

The change from V1 object {"switch":"off"} to V2 object {"switch":{"switch":"off"}} is a very big change for me. To which of the described changes does such a change apply?

Here is my environment and results. Nod-red version : v3.0.2 node-red-contrib-ewelink version : 2.0.0 node: ewelink-generic-device input : {"method":"getDevice"} Using V1 API output path of "off" is msg.payload.params.switch: "off" Using...