karamel
karamel copied to clipboard
odensc
[Feature request] Show all hidden child comments by default!
Show all hidden child comments by default so users don't need to click on load more comments
Solution: https://github.com/skydiver/ewelink-api/issues/220
Update APP_ID and APP_SECRET in node-red/node-modules/ewelink-api/src/data/constants.js with your APP_ID or from the previous link.
changed APP_ID and APP_SECRET, rebooted multiple times, still doesn't work
Same problems, started 3 days ago having been ok for months.
p xxx Sent from my phone, apologies for brevity and my dexterity inspired errors 😃
Updating APP_ID & APP_SECRET from Solution: https://github.com/skydiver/ewelink-api/issues/220 works fine but if you create a new app on https://dev.ewelink.cc/#/ and use your own APP_ID & APP_SECRET then you can get a list of devices but cannot control switches. I suspect the reason is due to the v1 login being depreciated and only v2 logins being an option. When the working APP_ID & APP_SECRET stop working then this will all become a problem again. Hopefully someone will fix this or we face the arduous task of flashing and configuring Tasmota on our Sonoff switches.
Don"t seem to work anymore, and the APP_ID & APP_SECRET don't seems to be issued by ottoszika but a community member.
coolkit-carl Says d'ont use it ! https://github.com/skydiver/ewelink-api/issues/220#issuecomment-1678308792
In issue https://github.com/skydiver/ewelink-api/issues/220 , the problem seems to be more located on new auth method (oauth 2) than in a legacy api id/secret...
Who's got the skill to integrate oauth 2.0 in node-red-contrib-ewelink, since it seems to be the only valid method provided by the underlying ewelink-api...
Still works for me, but only using the 'DEVICES' Node.
p xxx Sent from my phone, apologies for brevity and my dexterity inspired errors 😃
Still works for me, but only using the 'DEVICES' Node. With my own created APP id & secret I can only list devices but using the id & secret supplied in the post above I can also control the switches. The working id & secret are probably using oauth1 and this will last at most a year before the keys become invalid and this all becomes an unfix-able problem. I'm experimenting with an ESP8266 programmed with Tasmota and controlling it via a node-red dashboard (local) and Telegram (remote) just in case nobody can fix the oauth2 problem.
works but only for devices registered to that userID. shared devices cannot be accessed. Any advice on how to monitor shared devices also ?
Mine has worked just fine until today I finally upgraded my node-red install to 3 and nodejs to 18 to handle the new MATTER node - and now my node-red-contrib-ewelink will not connect... all the nodes including devices just say disconnected. Ideas anyone?
Hi Peter, I'm having the same problem with my Node Red ewelink: {"error":403,"msg":"Sign:oauthClient enable invalid"} I have not upgraded anything on node red or node.js and cant understand why ewelink just suddenly stopped working. Have you managed to get yours going again and if you have could you offer a helping hand please. Kind regards Don....
Having the same issue here, hopefully someone can release an update to fix issue. Looks like this module uses an older version of the API that has been shutdown.
Hi Peter, I'm having the same problem with my Node Red ewelink: {"error":403,"msg":"Sign:oauthClient enable invalid"} I have not upgraded anything on node red or node.js and cant understand why ewelink just suddenly stopped working. Have you managed to get yours going again and if you have could you offer a helping hand please. Kind regards Don.... I've just come back to this now - no - no working.. I ope someone has the answer - I ecently upgraded to nodjs18 to get the latest Node-Red.