Using PLEG for closing gate.

I have also seen security sensors resend their current status during a restart. In my applications, I only react to triggers from them when they constitute a status change. You can probably solve your issue simply by setting Repeats off.

I was trying to explain earlier that Repeats is required for some Conditions and should not be used as the default. Really you have to consider how each Condition will change in response to Inputs and how often you need the Actions to be fired.

A small question , Don’t want to start another thread for this.

For my heating system I also use PLEG. For the floorheating pump I have 4 schedules in PLEG 2x on , 2x off

Untill now I had for example as a condition:

floorheating_on_1 AND Automatic_set_temp_on That was with 1 schedule to have the pump on about half the day. now I want to turn off the pump some hours in the middle of the day. So the condition must be something like:

Automatic_set-temp_ on AND (floorheating_on_1 OR floorheating_on_2) (one of the 2 mus be true )) How should I put this in a condition?

many thanks,
Cor

For my heating system I also use PLEG. For the floorheating pump I have 4 schedules in PLEG 2x on , 2x off

Is there a reason why you don’t have two Schedules each with an on and off time? This would make the logic slightly easier.

Schedules
floorheating1 OnType: Weekly Days: … Time:…, Offtype: Weekly Days: … Time: …
floorheating2 OnType: Weekly Days: … Time:…, Offtype: Weekly Days: … Time: …

Conditions
floorheatingOn Automatic_set-temp_on and (floorheating1 or floorheating2)
floorheatingOff Automatic_set-temp_on and !floorheating1 and !floorheating2

Ohhh… there is a very good reason not just having 2 schedules … because i didn’t know this was possible :-X

I just changed it, as per your example.
For my information and saying it in simple words what is happening in the second condition:

(floorheatingOff Automatic_set-temp_on and !floorheating1 and !floorheating2)

Automatic_set_temp_on AND NOT floorheating1 AND NOT floorheating2 ( meaning floorheating 1 and 2 must both be false) is this correct?

Thanks,
Cor

Automatic_set_temp_on AND NOT floorheating1 AND NOT floorheating2 ( meaning floorheating 1 and 2 must both be false) is this correct?

Yes that is correct. This could also be written as not (floorheating1 or floorheating2) which might more obviously be the inverse of the expression in the on Condition.

A smart chap called DeMorgan gave us a theorem that tells us that in Boolean logic, NOT ( A OR B ) is the same as ( NOT A ) AND (NOT B).

The important thing is that you turn on your heating when either of the Schedules are true but turn it off when both of the Schedules are false (== neither are true).

WOA!!! PLEG is going crazy!!!

I must have done something wrong :-s but what!!!

The setup has been working flawlessly for over a year,last week I inserted another virtualswitch ,this one does the same for te gate , it just does not open the garage.

I thought it was all fine , but when I select the old virtualswitch (gate and garage open and close) the gate keeps on opening and closing again , untill I bypass PLEG.

This virtual switch was working normally untill the changes last week
I setup another virtual switch ( gate open and close) , this one now works normally.

Attached the LOG, at 1847 I clicked on the “faulty” virtual switch. It opens , 90 seconds later it closes , and than at 1850 it starts all over again …

I also attached the “status log” from PLEG.

“Gate open and close is turned on” >>Gate & Garage open and close: this one was the original one ( which is faulty now)
“Come_and_leave_gate_only” Gate open and close is turned on: this virtual switch I inserted last week.

Theses are the 3 conditions I inserted for the extra virtualswitch ( the last 3) :
open_gate_only / Ignore_VS_gate_for_gate_only / gate_lights_on1

Anyone can tell me what’s wrong, and why the new virtual switch is fine , and the previous one is now acting up.

many thanks,
Cor