Wait for input setup is not intuitive

Things to come.
Post Reply
crane
Posts: 24
Joined: Sun Apr 07, 2013 9:42 am
Bot?: No

Wait for input setup is not intuitive

Post by crane »

If I enable an exit condition and set it to "web Input" it will say that it couldn't save the setting. It seems that I just enable the exit condition, leave source blank, and then set the next state to wait for input. This is not very intuitive. Does it matter what I set the rest of the fields to when I set the next state to wait for input? I would suggest having the source be "wait for web input" and then the rest of the fields to the right be grayed out to avoid any confusion.
JonW
Site Admin
Posts: 1726
Joined: Sun Jul 18, 2010 7:51 am
Bot?: No
Location: Huntington Beach, CA
Contact:

Re: Wait for input setup is not intuitive

Post by JonW »

I believe this is a bug. "Web Input" should not be listed there as it is the WIN button functionality that was removed.

The "Wait For Input" next state option can be triggered by a temp probe, timer or DIN.
brahn
Posts: 543
Joined: Thu Dec 13, 2012 11:01 am
Bot?: No

Re: Wait for input setup is not intuitive

Post by brahn »

JonW is right, there should be no Web Input option listed. You would use one of the other options to trigger the waiting for input status.
Post Reply