That means it is crashing and restarting, which is confirmed by the first ps output that you posted.i pi 254181 144 0.3 176048 11904 ? Rl 15:43 0:00 python3 -u /home/pi/.node-red/node_modules/node-red-node-pi-gpio/nrgpio.py in 4 up 25 pi 254183 0.0 0.0 6088 1920 pts/0 S+ 15:43 0:00 grep --color=auto nrgpio
The second line is the ps command showing the grep part of the ps command you entered, and it shows the time the command was started as 15:43. The first line shows that the nrpgpio command started only just before the grep command, whereas it should have been running since you deployed that node.
So I think that is an explanation of why the node never gets any data, because the nrgpio command it is relying on keeps crashing.
@dceejay do you agree with my analysis here, and can you suggest what the way forward may be?
The wiring and interface to the header has not changed or been modified in 5 years. The system has operated 100% for a very long time. There are no "voltage" inputs to the header, all inputs are simply pi ground returns to pins pulled hi. There is no reason to believe the external interface would be involved here.
Personally, I think the evidence so far seems to be pointing to a python issue.
I’m tending to think that the recent changes to the way bookworm handles gpio and the way they have then tried to make it backwards compatible are probably at the root of this. Of course it needs more investigation but if so then I’m not sure what we can do about it without fully embracing the new way of working without breaking anyone on previous os / nodejs versions and a major rewrite.
