pmh1947
commented
1 year ago Partly resolved!
It appears that accessing from 2 independent Node-Red flows - running on separate machines in separate countries - the Ewelink host is allowing access from the second machine and then dropping the connection. . It is going to take some experimenting when I have local access to the 2 machines next to each other - using remote access the screen resolution makes detailed editing of Node-Red via TeamViewer just visually hard work.
The Android App seems to work ok whilst Node-red is running on one machine.
Has anybody come up with some simple solution? Scheduled access does not appear a good solution as some events are 'event triggered'. Maybe one Pi designated as master with it relaying info to the second?
o] Node-RED version: v3.0.2 14 Aug 15:26:37 - [info] Node.js version: v16.16.0 14 Aug 15:26:37 - [info] Windows 10.0.19043 x64 LE
I succeeded after hours of frustration of installing the Node node-red-contrib-ewelink 2.0.0 by installing and installing and running git as outlined in another thread that I found on here. Is this a prerequisite or was I just lucky?
After inputting the EweLink credentials via the Devices Node it will now connect and get an immediate response with details of all Sonoff Devices on my Account. However after the first response the Flow sometimes becomes unresponsive and I cannot make changes or force it to connect again. The console gives me a message relating to websocket 'not connected' or something similar.
If I restart Node-red it works for a few times (Neither consistent number of times or a fixed time) and then consistent Authentication failed 406 messages on a regular basis.
Any ideas please or suggestions?
I am also running an older version of Node-red on a Pi4 which appears to be rock solid and was hoping to run the upgraded version as the graphical editing is so much better!
I had previously posted this in an old thread, but I suspect it raises some new issues and is therefore appropriate to post as a 'new' issue.