Node-RED loses connection with GPIOD after two “deploys” (frequent docker restart necessary) :(
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, raspberry-pi
- Domain
- devops, embedded-iot
Research direction
Reproduce the failure in the official Docker container on a Raspberry Pi with gpiod, following the two-deploy sequence described in the report. Investigate the Node-RED/gpiod connection behavior after redeploying; done means the GPIO input continues changing state without restarting the container.
Written by the indexing model from the issue text.
Description
What are the steps to reproduce?
Run node-red in the official docker container.
Verify that the gpiod nodes have connection to the gpiod (daemon). 
Check that gpio input node actually works (e.g. use a simple switch to connect pin 5 to ground and see "OK" changing to 1 or 0).
Move some nodes and click “Deploy”. Do it again.
Check that gpio input node still works (in my setup it stoppes working). The gpiod node still states "OK" which indicates the gpio daemon is running. Running ps aux confirms this.
HOWEVER -connecting a pin to ground no longer makes the node change state.
restart the docker container - now it works again, but only until you click deploy 2 times again. Then a docker restart is needed again :(
Please tell us about your environment:
Hardware: Raspberry Pi 3B+.
- Node-RED version: 1.0.3
- Node.js version: latest?
- npm version: latest?
- Platform/OS: latest docker image.
host os: latest Raspian Buster - Browser: google chrome (not a browser issue).
- pigiod is latest version:
- Dominant language
- Shell
- Stars
- 540
- Forks
- 434
- Avg merge
- 24m
- Merged PRs (30d)
- 5
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.
More from node-red/node-red-docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
node-red/node-red-docker#536 ·
-
node-red/node-red-docker#522 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
node-red/node-red-docker#513 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
node-red/node-red-docker#510 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
node-red/node-red-docker#493 · 13 comments ·
All issues in node-red/node-red-docker
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hust-open-atom-club/hustmirror-cli#52 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
koalaman/shellcheck#3539 ·
-
package-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
msys2/MINGW-packages#31806 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ansible-collections/community.openwrt#271 · 1 comment ·