Hi there!
A bit of a shameless self advertisement… I’ve created a Virtual Weather Station WebThing based on the DarkSky API. It’s up for grabs at GitHub.
It needs a bit more work, but it’s usable at this stage 
I’m open for suggestions or better yet, pull requests! 
Looks nice. You should move the env definitions to the “schema”, so it can be configured in adapter options.
I don’t know where the docs for this would be, but I can offer you an example:
https://github.com/freaktechnik/netatmo-weather-adapter/blob/master/package.json#L42-L61 for the declaration
and https://github.com/freaktechnik/netatmo-weather-adapter/blob/master/adapter.js#L268 then reads the values in the last parameter passed to the adapter.
This certainly sounds like the next step
I’m not really familiar with the whole env, yet… are there any advantages of creating an adapter instead of my current solution? Other than the listing & configuration ui?
Also, what can I do to get my adapter listed?
The upsides of an adapter is that it is easy to install and use with the gateway. You also get notified when the users tries to pair new devices.
You can find more details on packaging and distribution in the readme here:
Thanks!
It’s really helpful!
QQ, is there an easy/proper way to test adapters not yet in the list?
You can just link or drop it into the ~/.mozilla-iot/addons folder. If there’s a git repo in the folder the gateway knows that it’s an in-development addon, and ignores all released addon things.