-
Notifications
You must be signed in to change notification settings - Fork 5
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
node-red deploy issue #18
Comments
i winder if this could be in some way linked to blynk server connection rate limiting... |
Not sure I get your meaning, like I said I removed the flow that takes ages to load and pasted it into a different instance of node-red on a different pi, |
Whoops that went wrong - Or do you mean, " just one connection " .. just one node? |
sorry, i meant just one token/server combo it kind of seems it does. if you add 3 server connections on the pi0 , does it behave the same? |
Over the last 2 days here is what I have been testing:- This is a pi2 running wheezy node-red v0.12.2 node.js v0.12.6 blynk v0.0.24 contrib-blynk v0.0.17 This is a pizero running noobs jessie with node-red pre installed v0.12.2 node.js v0.10.29 blynk v0.0.24 contrib-blynk v0.0.17 This is a pi b+ running wheezy node-red v0.12.2 node.js v0.12.6 blynk v0.0.24 contrib-blynk v0.0.17 So now I have 3 pi's with the original flows imported and I can switch between them recreating the issue and resolving it depending which one I use, so it appears to me the issue is related to the node.js version. So the question: is there a preferred node.js version associated with blynk / contrib-blynk. Toshi |
wooow, nice going. |
btw, by "4 separate blynk servers" upi mean 4 blynk.cc project keys, right? |
Yes 4 separate servers/project keys, in fact there the same 4 servers as original, each of the servers has a watch-dog led already so I just made the new write nodes switch just the existing watch-dog leds on each server page in the app. Here's the log for the disconnect detailed in para 2 of my post. Authorized |
I have had this problem for about a week now but didn't say anything because I hoped the resolution of #16 may have also resolved this problem but it doesn't...and I am not even sure its a node-red-contib-blynk issue, just wondering if you have any idea what's going on..?
The problem .. I have 4 blynk server connections, when I fully re-deploy node-red, 3 of the servers from connecting to connect take about 2 seconds but the 4th always takes ages like 3-4 minutes, its always the same server connection that has this problem and its every time I deploy nr here's the log:
1 Dec 10:43:16 - [info] Starting flows
Connecting to SSL: cloud.blynk.cc 8441
Connecting to SSL: cloud.blynk.cc 8441
Connecting to SSL: cloud.blynk.cc 8441
Connecting to SSL: cloud.blynk.cc 8441
1 Dec 10:43:46 - [info] Started flows
Connecting to SSL: cloud.blynk.cc 8441
Connecting to SSL: cloud.blynk.cc 8441
1 Dec 10:43:46 - [info] [mqtt-broker:8084e98a.7f7b18] Connected to broker: mqtt://192.168.0.98:1883
Connected
Authorized
1 Dec 10:43:47 - [info] [blynk-server:c1c8f31f.3e371] key: 0cc7 bla bla connected
Authorized
1 Dec 10:43:47 - [info] [blynk-server:39b0b4e1.c64f4c] key: 2972 bla bla connected
Connecting to SSL: cloud.blynk.cc 8441
Connected
Authorized
1 Dec 10:43:49 - [info] [blynk-server:c3307c50.3ccf8] key: f165 bla bla connected
Connecting to SSL: cloud.blynk.cc 8441
Connected
Connecting to SSL: cloud.blynk.cc 8441
Connected
same same repeated for in this case nearly 3 minutes until
Connecting to SSL: cloud.blynk.cc 8441
Connected
Authorized
1 Dec 10:46:11 - [info] [blynk-server:7f2dce8b.80d23] key: adf0 bla bla connected
As you can appreciate its very frustrating having to wait 3-4 minutes for node-red to be working when you are developing a flow,
To ensure its not a problem with my code, I deleted the flow and pasted it into another instance of node-red on a pizero in this case the 3 remaining flows still load within seconds and the flow on the pizero also loads within seconds ...
Its almost like Blynk gets confused/overloaded when connecting to multiple server instances.
The text was updated successfully, but these errors were encountered: