ESP8266 Community Forum

- Mon Apr 04, 2016 8:32 pm #44838 NODEMCU Board Running NodeMCU

I am controlling a relay. I can tun on the relay by interrupt into a pin or by UDP server /client. Regardless of what of the two ways turn it on (or off), the ESP sets an output that drives the relay.

GPIO setting for input pin:

gpio.mode(6, gpio.INT, gpio.PULLUP)
gpio.trig(6, 'both', debounce(onChangeLight) )

All works well.

I have an alarm set to 'timeout' after 30 minutes. At this time, the relay is switched off.

For some reason, it then ignores the GPIO input pin from that point forward (until I reset the device).

The only way to turn the relay on (or off) from that point forward is by the client /server (over the network).
The input pin is ignored.

- Tue Apr 05, 2016 10:08 am #44873 What's your debounce code??

Please see my Developer FAQ for Q&A on nodeMCU Lua before asking a question here that's already been answered. This and the other official documentation should be your first reference for developing Lua Apps

- Tue Apr 05, 2016 8:38 pm #44923

What's your debounce code??

function debounce (func)

return function (...)
now = tmr.now()
if now - last < 200000 then
return end

last = now
return func(...)
end
end

function onChangeLight ()

buttonIn = gpio.read(6)

if(buttonIn == 0) then

if (_G.LightStatus == 1) then
TurnOff()
else
dofile("ON.lua")
SetTimer()

end

end
end

- Wed Apr 06, 2016 5:25 pm #45006 Same reason as another GPIO Q that I just answered. Triggers are now delivered at user task level not ISR. The old ISR approach broke all the rules. Use a recent dev build either your own make or a cloud builder one and don't state in a loop for 200mSec. You have to return control to the SDK for any triggers to be delivered. Have a read of my FAQ below to seee how the event system works.

Please see my Developer FAQ for Q&A on nodeMCU Lua before asking a question here that's already been answered. This and the other official documentation should be your first reference for developing Lua Apps