I'm thinking that requiring WiringPi as a back-end (and associated node-wiringpi dependencies) doesn't give much of an advantage, when SysFS support is much better in new Raspbian kernels, and device-tree support means being able to support add-on GPIO expansion boards (which doesn't work with the current node-wiringpi anyway)...
Any particular thoughts? I'm thinking it would mean changing the module name, as keeping the -wpi2 suffix would be disingenuous. Perhaps there are already other homebridge modules out there that people are using instead of this one, so I should abandon this one all together?
I'm thinking that requiring WiringPi as a back-end (and associated node-wiringpi dependencies) doesn't give much of an advantage, when SysFS support is much better in new Raspbian kernels, and device-tree support means being able to support add-on GPIO expansion boards (which doesn't work with the current node-wiringpi anyway)...
Any particular thoughts? I'm thinking it would mean changing the module name, as keeping the -wpi2 suffix would be disingenuous. Perhaps there are already other homebridge modules out there that people are using instead of this one, so I should abandon this one all together?