-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eWeLink Event Listener stops working #147
Comments
I am experiencing a similar problem. Can't keep refreshing the credentials every time. Its really frustrating. |
This continues to happen for me every other day. Anyone, any ideas? |
I read somewhere that the present authentication is login based and does not support multiple parallel logins. So, if you are logged into eWelink from multiple apps(eWeLink app, Alexa etc.), the [Node-red-contrib-ewelink] node will stop working as eWeLink will kick you off after sometime(some kind of time out with multiple logins) After 2 days of testing, below steps worked for me:
I sincerely feel that the node author should try some token based authentication to enable multiple parallel sessions |
I am having the same problem again... :( ..... |
I've a sonoff DW-Wi-Fi door sensor - which reliably triggers on change in the eWeLink app - but in Node-Red - after a while the event listener stops responding to open and close (on/off) evenst. If I remove the node - replace it with an identical one, put in in the same ID and credentials again - it comes back every time, but then after a while it just stops doing anything again.
Thoughts?
Pete
The text was updated successfully, but these errors were encountered: