Q2 - As far as I know, the new version uses auth tokens in the same way as before, but if you’re using the automatic provisioning then maybe you don’t see it (I never managed to get dynamic provisioning working during beta testing, so had to manually enter the auth token via the captive portal.
Q3 - The datastreams are configured in the device template, via the web portal, and are available to all widgets in that device. The thing to look out for is that the default maximum value is 1, so if you write a value higher than that to the virtual pin it well be displayed as 1
Q4 - It should work the same, but beware of the issue I pointed out in Q3
Hi Pete, eventually after 2 days struggling, I got this working. I see the potential in V2.0 but it is heavy going. Still have loads of questions but will ask in a new topic.