No, it currently only covers 1.x as that is all I use. I've looked at moving to v2 twice now and each time, I realise that there is too much to take into account and to have to deal with manually. Hopefully they will come up with a better migration path at some point and then I can think about transitioning. Until then, I'll start to try and use the v2 API's and Flux language. The returned data from Flux though is a nightmare. They have the cheek to label it as CSV but really that isn't true at all. You certainly shouldn't run it through the Node-RED CSV node.
I have some other example flows that I will share at some point where I've been investigating the use of Flux. But those are still against a v1.8 db. I've also been looking at the v2 API's (which work with v1.8). Again, I will share something when I have a better set of tests.
I would actually like to avoid the use of node-red-contrib-influxdb if I can and would prefer to write direct to the API's.
I also did some tests using the influx command line tool and the exec node. Mostly I've been trying to create some standard query and create commands because I always forget how I've got things set up. As I'm working on my next-gen home automation system, I thought this was the best time to create some flows that will create/recreate my standard dbs, CQs, RPs, and measures.
v2 API tests:
v1.x API tests:
The function nodes in the above flows process the output into something more Node-RED'ish.
I also need to do an equivalent set of tests using node-red-contrib-influxdb for comaprison.