What's wrong with this picture?

[quote=“Bulldoglowell, post:20, topic:179776”]“I just dropped by to see what condition my condition was in” Kenny Rogers

yeah, it is cool. Plus, you can use inputs from other PLEG devices. I noticed that with name conflicts and didn’t realize it worked that way until I saw Richard’s recent remarks.[/quote]

OK there Lebowski :wink:

I have tried a few times to use an input from one PLEG in another and it straight up doesn’t work for me. I plain copy and paste the input name to no avail.

Are you sure inputs can be shared between PLEG instances?

If not, this would be a GREAT feature. Hell. I’d just have one instance for inputs!

Are you sure inputs can be shared between PLEG instances?

An input (or condition) defined in one PLEG/PLTS can NOT be referenced in another. You can define it with the same name in both!

PLEG will keep it’s condition to itself :slight_smile:

Well this still isn’t working for me. Checking the Repeats check box is the equivalent of the previous leading underscore, correct?

Again: I have conditions like

I_Entered and !Mrs._Home

With the check box checked.

Works great. I enter my PIN and nothing happens. That is until she leaves the house. Then the message gets played. On the status report the last PIN entered remains True until new PIN is entered.

What am I missing here?

you have to constrain the I_Entered to reflect that you want to do this if she isn’t home when you came home and not you are home and she left

Does that make sense?

DoSomething = I_Entered AND !Mrs._Home AND (!Mrs._Home;I_Entered)

it will DoSomething if you come home and your wife is out and your wife was out before you came home.

Is that what you are looking for?

Yeah I see what you’re saying.

But then WTF is the check box for?

I’m profoundly confused.

Some triggers, schedules, and conditions once true, will remain true. They do not change state if they were actuated second time. In that case, you want to use the _ or check the box.

Using a pin code to unlock the door, or a schedule, are the most common of these examples.

Right. That’s what I thought. The action fires because the last PIN entered is still true. So why doesn’t checking the check box nullify that?

If the event occurs again it will trigger, even though the state doesn’t change.

Oh Snap!

Got it.

Thanks.