This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hello
i have installed the large image of venus with Node Red included. everything works as it should.
i have 5 relays i want to control, but i do not want to do it on the Venus UI, instead i want to listen on the local MQTT Server and if the value true comes in i want to turn the relay on.
My Relais are on the PINS (7,11,13,19,26)
Does anybody knows how to access them in node red?
The standard Raspberry Pi Nodes arent working
Hi @bo0om,
i solved the problem and testet with RasPI 3 and 4.
With the following it should work:
wget https://updates.victronenergy.com/feeds/venus/testing/packages/dunfell/cortexa7hf-neon-vfpv4/python3-dev_3.8.11-r0_cortexa7hf-neon-vfpv4.ipk opkg install python3-dev_3.8.11-r0_cortexa7hf-neon-vfpv4.ipk wget https://updates.victronenergy.com/feeds/venus/testing/packages/dunfell/cortexa7hf-neon-vfpv4/python3-xmlrpc_3.8.11-r0_cortexa7hf-neon-vfpv4.ipk opkg install python3-xmlrpc_3.8.11-r0_cortexa7hf-neon-vfpv4.ipk wget https://updates.victronenergy.com/feeds/venus/testing/packages/dunfell/cortexa7hf-neon-vfpv4/python3-pip_20.0.2-r0_cortexa7hf-neon-vfpv4.ipk opkg install python3-pip_20.0.2-r0_cortexa7hf-neon-vfpv4.ipk python3 -m pip install RPi.GPIO reboot
Have you tried logging the inputs to see what messages are being sent to your rpi gpio out node?
Have you tried to connect the GPIO pins to LEDs instead of the relay to eliminate any driving issues on the relays?
thanky you, i have to try it
Hello,
I have been running into the same issue as @bo0om, and i also tried the commands from above, right now copying those commands doesn't work because the source has new versions for Python3-dev & python3-xmlrpc. So i used the following:
opkg update opkg install python3-dev opkg install python3-xmlrpc opkg install python3-pip python3 -m pip install rpi.gpio reboot
unfortunately when trying in Node Red, i was getting the error 'Command not running' in de debug field and also it said 'Stopped' underneath the output fields of the GPIO nodes.
In the description of the GPIO-node package node-red-node-pi-gpio (https://flows.nodered.org/node/node-red-node-pi-gpio) i could find some information that for distro's other than Rasbian you need to 'open up' the gpio pins with a list of commands.
The commands listed there don't work because they are not supported by Venus OS.
since i am not familiar with linux command line, this was a trial & error process, but in the end i could find the following command that work:
groupadd gpio chown root:gpio /dev/gpiomem usermod -a root -G gpio usermod -a nodered -G gpio echo 'KERNEL=="gpiomem", NAME="%k", GROUP="gpio", MODE="0660"' | tee /etc/udev/rules.d/45-gpio.rules udevadm control --reload-rules && udevadm trigger reboot
So i made a new group called gpio and added user root & nodered to this group. to check if the users are actually included in this group you can use this command:
groupmems -g gpio -l
I don't know if the nodered user has to be included for this to work since i only tested this once. after the reboot i got the GPIO pins to work!
I am using the Venus OS large image v2.90, running on a Raspberry Pi 3 Rev. B.
Hello and thanks for this guide.
I have VenusOS 2.90-10 large on a RaspberryPi 3B+.
I did all the steps as described.
Debug from node red reports: "nrgpio python command not running"
rpi-gpio out says : stopped
I've been trying for hours, help would be great. Regards
it turns out i am also experiencing problems with the inputs, i never tested it because i only needed to use outputs at that time.
Are you able to get the outputs to work then?
at first my inputs were also giving 'stopped', then i updated the library and it was saying 'OK', after that it does not give me a state so something is still wrong.
Greetings
Hello stijnl,
inputs and outputs don't work for me.
If I get it to work I'll let you know.
Regards
Hi mcbain
By following the above post by stijnl exactly, the GPIO outputs do work on a freshly installed V2.91 VenusOS on my Raspberry Pi 3B+. I've had to include the groupadd part as well because it didn't work with just the installs.
I've had no luck with the inputs either.
Steve
Hello stijnl, steve.
i did a fresh install with 2.92. Now the Outputs works like a charm ;-) thank you.
Unfortunately, inputs do not work. I Try many GPIOS,
Only via the node digital input from the victron library it was possible for me to process a digital input in node red.
Regards
On v2.92 there is permissions problem when user wants read gpio input. Dirty workaround:
Add user nodered to sudo and edit file /data/home/nodered/.node-red/node_modules/node-red-node-pi-gpio/nrgpio
change line python_cmd='python3' to python_cmd='sudo python3'
After redeploy inputs will work but its not persistent its needed again when you add another flow.
The problem is not in reading the input but in creating the callback function for the edge detection (line 107 to 110 in nrgpio.py). The edge detection requires access to other file but gpiomem.
By following the instruction here https://flows.nodered.org/node/node-red-node-pi-gpio outputs work.
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'"
If you add to the rule file 45-gpio.rules also these lines the inputs work too.
This seems to be broken in V3.01 - i am trying to get my GPIO outputs and inputs to work, but i can't get anything working :(
At first, is just showed me "N/A" like the pic above, but after doing what stijnl said, it tells me "nrgpio python command not runing"
Anyone got the same problem, and found a solution?
Thanks!
*Edit - nevermind, got it working with a fresh install!
PS, for those running Node-red under SignalK - change user "nodered" and put in "signalk" instead.
