#Ok I'm going crazy trying to figure out

1 messages · Page 1 of 1 (latest)

lone hornet
#

This flow for example, I can never get the 10min timer to trigger

fiery anvil
#

in the trigger node you have it reset when you it receives a message with payload = on

#

and your current state node is outputing payload = on

#

so the trigger node is never starting, it's just being reset every time

lone hornet
#

that's the same way I use it elsewhere - is there some other way it should be started vs reset?

#

I would think reset would start/restart the timer

fiery anvil
#

reset just stops the timer

lone hornet
#

That's now how I read it...but ok. So then how should the timer be started?

#

It seems like any message should

#

I don't see anything about a specific start message needed

fiery anvil
#

as you currently have it any message will start the timer expect if msg.reset exists or msg.payload = on

#

so either remove the custom payload value to reset in the trigger node or change the output of the current state node

lone hornet
#

I have other flows where payload:on starts the timer

#

slightly more complicated flow, but you'll see where I have the debug6 node I was checking to compare exactly that

#

debug6 gets a payload:on every time and the timer works great

fiery anvil
#

that's because off payload is starting the timer

#

the button flow is your current problem where there is only one ouput msg.payload = on

lone hornet
#

the "off" in the old_state is triggering it?

fiery anvil
#

when living room motion goes to off that is what is starting the timer of the trigger node

#

the "door open" node is reseting the trigger node but that is probably happening before the motion sensor goes to off

lone hornet
#

ahhh, interesting ok

#

I guess I didn't realize that "off" hiding in there was doing the triggering

#

that makes much more sense