The Issue

If you try to watch GPIO pin 16 in Node using the onoff npm package I get the following error message:

Error: EBUSY: resource busy or locked, write.

You can find the Node code in this PR at the moment:
#22

What I've Tried

I've stopped PureData and the Python script from running on the Pi. I've also updated .bashrc so it doesn't restart those things every time I reboot. All of the other buttons work perfectly—just not button 7 (pin 16)!

I took a look at the pins and noticed pin 16 appeared to be setup as an OUT instead of an IN like the other pins that map to buttons were:

I found this thread, which seems to also involve an issue specific to this pin and the RaspberryPi: https://www.raspberrypi.org/forums/viewtopic.php?t=135813.

I ran rpi-update to update to the latest firmware to 40064f62df458d0a56a8a17c9168d7529372099a. This seemed to fix the issue for people on the thread, but did not see any changes.

Then I tried running this commend to change the pin to an IN type, which seemed promising.

---> raspi-gpio set 16 ip pu

I ran gpio readall again and I saw the pin updated as I'd hoped/expected:

At this point I rebooted the Pi, double-checked to make sure my GPIO settings had kept, and tried it again.

Still no luck :-/

It's curious that it does not fail in Python. I'm wondering if the resource is truly busy and Python simply doesn't care?

https://www.hackster.io/shiva-siddharth/make-your-own-google-voice-hat-9f96ca

• account for space in the enclosure for speaker and battery
• use raspberry pi for guidance on where to place things (don't put dc jack on top of usb ports, etc.)
• get standoffs/spacers

So you don't catch the click of the button