Domoticz

Creating thread as requested in tracker: http://www.domoticz.com/forum/tracker.php?p=2&t=351

GPIO States can be read and changed via filesystem layer: /sys/class/gpio/gpioXX/value without requiring specific additional GPIO libraries for hardware already supported by any modern Linux Kernel. When supported by the hardware Interrupts can be used with these devices to trigger changes without polling.. I dont know if there is any good way to tell if a GPIO will work wit interrupts so it will likely need to be a configurable option (polling vs interupt)

IMHO the current GPIO support needs to abandon the WiringPI Libraries which are applicable to only PI devices and go straight for GPIO access without additional libraries.. Setting up SysFS should be done externally from domoticz and it should use what ever is available.

the gpio paths should be able to be mapped to header labels, this could be as simple as an alias name within the UI.. such as gpio27 = P8_12

SysFS also supports PWM Outputs via run, duty_ns and period_ns files, in domoticz these could be the equivalent of GPIO "Dimmers"

I believe this to be critical functionality that is missing from Domoticz, with proper support anything that can run linux with GPIO's could be utilized as a Domoticz server/node, limited to only what the kernel supports.. for example i2c or spi IO expanders

Would be great!, Could you propose a git pull/patch request?

Considering the problems/bugs some of us have with the current GPIO implementatio (even on an RPI), I will certainly welcome a more solid approach and a rewrite of the code!
I hope someone in the community - I'm not a programmer - can see a nice challenge here

not many response here .... could be great

agreed, its disappointing that Domoticz has became RPI centric.

I think I might have found a way, using the MQTT interface..
see: https://github.com/kylegordon/mqtt-gpio-trigger

I think I might be able to write a nodejs daemon that monitors GPIO's and publishes them right to domoticz without the need for any red5 mapping..

This seems like a much better way than banging around on virtual devices using json requests and trying to prevent feedback loops.

The MQTT documentation has me scratching my head, think its going to take me a bit to get my head around it.

I have been running Domoticz with GPIO in various applications on different Raspberry Pi's for years. When I updated one Pi to Bookworm, I realized that “sysfs” and the “easy way” to use GPIO in Domoticz no longer work under the Bookworm operating system.
I have learned a lot from reading this forum, thanks for that.
But there doesn't seem to be an easy way yet. Then I thought about the following:

I installed MQTT and Node RED on the Raspberry Pi, for example to integrate data from the solar system into Domoticz. So why not use Node Red to address the GPIO? It was quickly programmed. Node Red offers ready-made nodes for setting or reading the bits in the GPIO and the data can be easily exchanged between Domoticz and Node Red via MQTT!