Tom Janson

This is described in the [setup instructions](https://github.com/domenic/chai-as-promised#installation-and-setup) and [demonstrated in the code](https://github.com/domenic/chai-as-promised/blob/master/test/support/setup.js): Use a separate file for setting up chai and `require` it. Or does that not solve the problem?...

I worked around it by simply entering my server’s (thankfully static) IP address.

If I may: unfortunately boolean parsing in Ansible is a wildly inconsistent mess, so it's best to assume the worst at the place of consumption, i.e., handle conversion from string....

What’s the use case? If in doubt, you could just open again. Do you need to know the status? In that case: I wrote a wrapper for the WiringPi `gpio`...

> How hard do you think it will be to support backwards compatibility? Would you say it's worth sacrificing backwards compatibility (if, say, we do that with a significant version...

I’ve pushed to [branch `gpioutil-switch`](https://github.com/rakeshpai/pi-gpio/tree/gpioutil-switch); it’s not quite finished yet, but ready to be tested. Apart from adding tests for the auto-export functionality, I’m thinking about rewriting `read` and `write`...

I’ve cleaned everything up and opened a PR #27, please have a look. :)

You are correct, and that looks good. Feel free to submit a PR. Unfortunately this project is for the time being somewhat abandoned: Neither the owner nor I currently use...

Wait, unless I’m missing something this has been fixed by https://github.com/rakeshpai/pi-gpio/commit/82ef7bddbb0af8edf03470023be71febeac6ed32 since March 2015 (in `master`, not the other branch).

I’m afraid pi-gpio hasn’t seen active development (by owner @rakeshpai) for almost a year. (Though small PRs have been merged.) I myself haven’t worked with my Pi in a while...