Orange Pi 3B + Armbian: pigpio does not work, is there a native way to control GPIO?

1

Hello!

I installed Mycodo on Orange Pi 3B under Armbian (64-bit). The interface works perfectly, and the installation went smoothly.

When adding GPIO Input/Output, Mycodo requires pigpio and installs it automatically. However, when I start the pigpiod daemon, I get error 203/EXEC — systemd cannot find/start the daemon. I checked: /lib/systemd/system/pigpiod.service is missing from the system, and pigpiod itself is not installed (only the Python module).

I am trying to understand if there is a working way to control GPIO on Orange Pi within Mycodo, considering that pigpio is tailored for Raspberry Pi (Broadcom SoC), and Orange Pi 3B has Allwinner H6.

:red_question_mark: Is there:

GPIO support on Orange Pi without pigpio?

The ability to use OPi.GPIO as a backend?

Has anyone run GPIO through Custom Output with OPi.GPIO?

I can control the pins directly through OPi.GPIO in Python — it works. But I would like to use Mycodo’s functionality (output control, automation) through the interface, without workarounds.

Alternatively, I’m thinking of switching to MQTT + external ESP if there is no native way.

I would appreciate any advice from those who have run Mycodo on Orange Pi.

Thank you!

2

You’re likely going to have to create a new output module using the library that works with the hardware. If the OPi library is a drop in replacement of RPi, this would be as simple as copying the output module that uses RPi, changing the unique name, and replacing all instances of RPi with OPi. Do you have experience with Python and can make an attempt at doing this or would you like assistance?

3

I have some experience with Python, but I must admit it is limited. Later, I may try to approach it more seriously, but for now, I have chosen to use API and MQTT for my project.

But I am not refusing help and am ready to provide whatever I can if anyone is willing to help with this.