In cas you’re still working on this, Tzapulica… I’m using Blynk server locally and Node-Red. I have the node-red blynk nodes talking to the Blynk server, then via a function node it is easy to send and received MQTT in Node-Red to do whatever you want. The ONLY issue right now - and I have informed the writer of the Node-Red Blynk node, all goes well unless for some reason you stop the Blynk server - at which point the Node-RED nodes disconnect (obviously) but DON’T automatically reconnect to the Blynk server when it comes back on. I’m looking at his code now but I’m not sure I’m up to fixing this - if anyone does fancy their chances modifying the (not THAT complicated node .JS) then please do get in touch.
Using the Raspberry Pi mode, you get 64 virtual pins - which is just as well as a complicated installation could easily run out of the normal 32 pins. Case in point - I run 2 installations of Node-Red and various controllers - and right now they are on separate Blynk servers, well isn’t it a COMPLETE PAIN having to sign out of one and into the other (I’ve mentioned this to the authors) so on the surface of it, simply having ONE Blynk server and have your various Node-Red installations talking to it is great - but if that one Blynk server goes down even for a moment, the whole lot come to a halt. So this node needs fixing - and once it is fixes we have one hell of a powerful way to use Blynk, not least for monitoring multiple site info.