ottoszika / node-red-contrib-ewelink

NodeRED nodes for eWeLink smart devices
https://ottoszika.github.io/node-red-contrib-ewelink
MIT License
49 stars 28 forks source link

ewelink listener problem after restart #141

Open demokedes opened 2 years ago

demokedes commented 2 years ago

Firs of all, I would like to thank you for your effort. What you did is amazing. I am using nodes inside node-red for a quite a long time now.

Yesterday I was doing some maintenance on my node-red (did few reboots) and I realized that after reboot of node-red server ewelink listener is not working. It is showing green "connected" icon, but it is not sending any messages, although ewelink devices are sending signals. Everything I have to do is to copy the node (create the new one with the same credentials) and the new one is working. Do you know what might be the problem? Does anyone else have the same problem. Currently that means, that I have to do this manually after each reboot.

nareso commented 2 years ago

https://github.com/ottoszika/node-red-contrib-ewelink/issues/110#issuecomment-1042509534

demokedes commented 2 years ago

That makes sense, but can you tell me a bit more how you achieved this . Because listener doesn't have any input, only output. How can inject this? Thank you in advance. in the bellow screen, you can see my example. Bellow listener is not working as it should. I created above one with the same credentials...with the inject node to check for the fw od particular device. I am getting the firmware version, but bellow listener is not sending messages from the devices. Thank you in advance, Rok [image: image.png]

On Thu, 17 Feb 2022 at 09:50, driagi @.***> wrote:

I have the same problem. I'll tell you a trick that works for me. Activate a node with an inject (every minute) that asks for the FW of the device.

— Reply to this email directly, view it on GitHub https://github.com/ottoszika/node-red-contrib-ewelink/issues/141#issuecomment-1042708596, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZ26D2EKOLS25DNYVGMTX3U3SZF3ANCNFSM5ONXVVIQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>