return binding.writebuffer issue about onoff HOT 3 CLOSED

This can happen when onoff wants to export a GPIO to userspace but can't because the GPIO is already being used by another piece of code, perhaps in the same process, perhaps in a different process, or perhaps by the kernel. This other piece of code, wherever it happens to be, won't be using the sysfs files locates at /sys/class/gpio to access the GPIO.

Is there another piece of code on your Raspberry Pi that is using the GPIO in question?
Or are you using a device tree overlays that is reserving the GPIO for some purpose?

Also, try the following: open a terminal window and cd to /sys/class/gpio. If there is no directory called /sys/class/gpio/gpio<put-correct-gpio-number-here>, run the following command:

echo  put-correct-gpio-number-here > export

If an error message similar to the following is printed, something has the GPIO reserved:

-bash: echo: write error: Device or resource busy

from onoff.

@fatboy95 what's the status here?

from onoff.

It was an error in my code.. thanks for the help.

from onoff.