# Optional gpio input debounce

**URL:** https://discourse.nodered.org/t/optional-gpio-input-debounce/12131
**Category:** Feature Requests
**Created:** [12 June 2019 16:06 UTC](https://discourse.nodered.org/t/optional-gpio-input-debounce/12131 "2019-06-12T16:06:56Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![edrean](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edrean/32/9263_2.png) [@edrean](https://discourse.nodered.org/u/edrean)
#### Post date: [13 June 2019 20:12 UTC](https://discourse.nodered.org/t/optional-gpio-input-debounce/12131/12 "2019-06-13T20:12:28Z")

</div>

I made the changes to the code as you did above. I can confirm that a debounce time of 0 no longer causes the flow to stop.

However, it still does not catch my pulses.

I will put my pulses on a scope tomorrow and come back with more exact information of my setup.

In the meantime, a quick question. Does the GPIO node make use of the interrupt functionality of the pin? Or is it simply polling the pin on a regular basis? I can get it to work with the node-red-contrib-opi-gpio library. It uses the interrupt to trigger the change. The difference might be with how the two gpio nodes are triggered...

---

_[View the full topic](https://discourse.nodered.org/t/optional-gpio-input-debounce/12131)._