FAQ: I have an existing Blynk 1.0 account - do I use these credentials to access Blynk 2.0 (ie Log In), or Do I create a new Blynk 2.0 account (ie Sign Up)?
Something at your end . . . I logged in no problem, setup my first test project, little bit of a learning curve but all good . . . not “useless” at all . . .
No, unfortunately it doesn’t, certainly at the moment.
This is because websockets integration has not been built in to Blynk.360. Blynk say that it’s on the roadmap, along with native MQTT support, but have not given a timescale.
@gab.lau (who wrote and maintains the current node-red-contrib-blynk-ws) has said this:
There is a workaround to post data to Blynk from Node-Red using the HTTP Request node, using the Blynk.360 API (which is different to the old one) and I’ve been using this to push data into 4 virtual pins every 5 seconds for the past two months and it’s working well.
As far as getting data back from Blynk, I guess you’d need to query each virtual pin on a regular basis using the API, and look for changes (maybe using the RBE node). I have no idea how often you’d be able to get away with doing this though, before your API requests were disallowed.
Personally, I’m rather disillusioned by this, and by the lack of a firm commitment from Blynk on enabling websockets, so I’m looking around for different alternatives to Blynk at the moment.
I think all blynk 1.0 examples should work in the same way.
However, some new features weren’t yet fully documented, like this one - Log Event - Blynk Documentation
Thank you for this effort. I made a simple code to turn on and off a virtual LED, but it didn’t work with the new Blink and at the same time it works on Blink 1.0
Thank you for your tremendous support in making it happen 
