Rule issue with timing

---

@xCite86 Ah, that’s the way ruling works. A rule get’s only triggered when item in the IF clause changes (trigger) where I thought they were evaluated in a loop again and again.
In that case it should not be possible that my original rule evaluates twice on just one PIR activation as I noticed: two emails in 5 seconds where the PIR was still on from the original detection. This means in my situation I should not need a check on double emails on one PIR activation.
Something else is wrong then.

Thanks for clearing this for me.

@Petjepet to be sure you can add trigger: in front of it. So it only executes at the moment the pir changes.

To compare:

if trigger: pir1 is present and xx is turned on

If pir1 is present and xx is turned on

If xx is turned on, and the pir1 gets present it will mail. If xx gets turned off and turned on again while pir1 is still present it won’t mail. While in the second rule it mails again.

@Petjepet said:

In that case it should not be possible that my original rule evaluates twice on just one PIR activation as I noticed: two emails in 5 seconds where the PIR was still on from the original detection. This means in my situation I should not need a check on double emails on one PIR activation.

did you use a resetTime in combination with your pir too? maybe your pir sends a Signal twice while off-going so maybe your resettime was not enough?

{
  "id": "homeduino-pir",
  "name": "PIR",
  "class": "HomeduinoRFPir",
  "protocols": [{
    "name": "pir1",
    "options": {
      "unit": 0,
      "id": 17
    }
  }],
  "resetTime": 6000
}

@sweebee Thanks for explaining.
@xCite86 That’s also interesting but not applicable to me. I use MySensors and the potmeter on the PIR to adjust the reset time. I’m not aware of a kind of ‘resetTime’ in the MySensor’s PIR device. For battery savings an option like this would be interesting: on hardware side choose for minimal uptime (potmeter) to manage this aspect in the software.