Hello!
I have a setup with a universal node which measures temp/hum, luminosity and presence by a PIR-sensor.
My goal is a battery powered node, so I put the esp into deepsleep and wake it every 15min für temp updates etc.
The PIR-sensors is connected through a monostable multivibrator to the resetpin to wake it up (interrupt like) und a GPIO.
So everytime it wakes up, it reads a high state from the PIR-pin und goes into deepsleep again.
But because there is no change in the PIR-state when the esp is active, it never publishes the PIR-state.
So, where is the best position to modify the code, so it publishes the state of the input on every bootup no matter what state it had the last time?
Thanks in advance
Michael
Send GPIO state on every bootup
Moderators: grovkillen, Stuntteam, TD-er
Re: Send GPIO state on every bootup
i'd love to know that too.
Re: Send GPIO state on every bootup
+1 feature request for that?
as i actually dont know, too. i would be nice to have.
besides that i personally would like to see individual send-timeouts for each sensor/device,
i would maybe a general good idea to have a (univeral) plugin like "level-control" in the device-section,
wich could show up some drop-down menues to configure such functions as a callbacks.
i could show a drop-down with "on booting up" -> "send GPIO states, check ..., do this..."
if i were a coder i would search the github-code in the boot-code sections..
as i actually dont know, too. i would be nice to have.
besides that i personally would like to see individual send-timeouts for each sensor/device,
i would maybe a general good idea to have a (univeral) plugin like "level-control" in the device-section,
wich could show up some drop-down menues to configure such functions as a callbacks.
i could show a drop-down with "on booting up" -> "send GPIO states, check ..., do this..."
if i were a coder i would search the github-code in the boot-code sections..
Who is online
Users browsing this forum: Bing [Bot] and 1 guest