i use GPIO 5 as a switch(i use it to control a relais)
in rules i use
on Brink#Ventilator=1 do
xxxxxx
now i was expecting that this rule was only triggered on change but it seems it is being triggered all the time
eg when gpio 5 =1 this rules gets executed everytime instead on only a change
is this normal for GPIO ports
should i use monitor GPIO5 to avoid this
the reason i want to use the eventhasndler is that monitor is resource intensive
at the moment i am not monitoring GPIO5 but i am checking the Brink device
i use a HTTP command to set this GPIO 5 to either 0 or 1 (set to 1 will trigger the relais)GPIO triggering all the time
Moderators: grovkillen, Stuntteam, TD-er
Re: GPIO triggering all the time
You should either use it as shown for an input (e.g. with a button connected to it) or solely interact with the GPIO via rules.
To receive events when acting on it via rules, you should indeed call "monitor" for that GPIO pin.
To receive events when acting on it via rules, you should indeed call "monitor" for that GPIO pin.
Re: GPIO triggering all the time
ok, clear. i thought i fgured out something smart (which it is becauswe i can monitor a gpio state without using monitoring) but aparently it does not work all the way.
i will implement the monitor function which should do the trick
i will implement the monitor function which should do the trick
Who is online
Users browsing this forum: Bing [Bot] and 28 guests