node-red / node-red/node-red-nodes
[node-red-node-pi-gpio] on Venus OS and other non raspian OS
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
The workaround proposed here (https://flows.nodered.org/node/node-red-node-pi-gpio) for non raspian OS works good for input and output setup and set/read function but it does not work with edge detection.
A possible workaround can be found here https://forums.raspberrypi.com/viewtopic.php?t=302177.
Basically, the following lines must be added to the rule file too:
SUBSYSTEM=="gpio", KERNEL=="gpiochip*", ACTION=="add", PROGRAM="/bin/sh -c 'chown root:dialout /sys/class/gpio/export /sys/class/gpio/unexport ; chmod 220 /sys/class/gpio/export /sys/class/gpio/unexport'"
SUBSYSTEM=="gpio", KERNEL=="gpio*", ACTION=="add", PROGRAM="/bin/sh -c 'chown root:dialout /sys%p/active_low /sys%p/direction /sys%p/edge /sys%p/value'"
SUBSYSTEM=="gpio", KERNEL=="gpio*", ACTION=="add", PROGRAM="/bin/sh -c 'chmod 660 /sys%p/active_low /sys%p/direction /sys%p/edge /sys%p/value'"
Please, add to the help for this node.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the node-red-node-pi-gpio help referenced in the issue and compare its non-Raspbian workaround with the linked Raspberry Pi forum guidance. Add the three supplied udev rules to that help, then verify it explains edge detection on Venus OS and other non-Raspbian systems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, raspberry-pi
- Domain
- documentation, embedded-iot
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100