# How to ensure gpio is low after deployment or nodered start

**URL:** <https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420>\
**Category:** General\
**Created:** [10 March 2021 15:50 UTC](https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420 "2021-03-10T15:50:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![riker65](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/riker65/32/38453_2.png) [@riker65](https://discourse.nodered.org/u/riker65)\
**Post date:** [10 March 2021 15:50 UTC](https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420/1 "2021-03-10T15:50:33Z")

</div>

Hi

I have an injection - timestamp to set GPIO to low  
but it is always high after a deployment or restart

i did read: but did not "understande" the solution  
[https://discourse.nodered.org/t/rpi-gpio-in-node-always-incorrect-first-read-after-boot/26339/21](https://discourse.nodered.org/t/rpi-gpio-in-node-always-incorrect-first-read-after-boot/26339/21)

to ensure GPIO low I did

```auto
[{"id":"33e87854.1286d8","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"dc3f7bc.3f76488","type":"rpi-gpio out","z":"33e87854.1286d8","name":"Giandel_low_init","pin":"40","set":true,"level":"0","freq":"","out":"out","x":460,"y":200,"wires":[],"icon":"node-red/light.svg"},{"id":"a88dfb2d.a449a8","type":"inject","z":"33e87854.1286d8","name":"gpio_low_p40","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":true,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":230,"y":200,"wires":[["dc3f7bc.3f76488"]]}]

thanks for guiding

BR T

```

PS. Looks like I made an error using same GPIO parallel. and not all where initialized with low.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 March 2021 21:10 UTC](https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420/2 "2021-03-10T21:10:34Z")

</div>

Is it all working now?

The link you posted was about a bug in the GPIO In node that was fixed a year ago. I think you are using GPIO Out so it is irrelevant anyway.

---

<div class="post-metadata">

**Author:** ![riker65](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/riker65/32/38453_2.png) [@riker65](https://discourse.nodered.org/u/riker65)\
**Post date:** [11 March 2021 07:34 UTC](https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420/3 "2021-03-11T07:34:47Z")

</div>

Hi Colin,

I think it is working now.  
as I added in first comment, I deleted duplicate GPIO Nodes and checked the initilized box and set to low.

thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 March 2021 07:35 UTC](https://discourse.nodered.org/t/how-to-ensure-gpio-is-low-after-deployment-or-nodered-start/42420/4 "2021-03-25T07:35:08Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.