Wasp in a Box: "Door Closed" grace period to prevent exiting false positives

[Adavidebaba]

Hi,

I'm using the Wasp in a Box (WiB) feature, and I've identified a common scenario that leads to a false positive, especially with PIR sensors that have a built-in cooldown period.

The Problem / Scenario

The current logic triggers incorrectly when I exit an area quickly. Here is the sequence:

1. I enter the room: The Box (door sensor) state becomes on (open). The Wasp (motion sensor) state becomes on.
2. I leave the room quickly and close the door: The Box (door) state becomes off (closed).
3. In my personal setup, this happens consistently. Both my motion and presence sensors (Wasp) are located very close to the door. When I exit, they detect this movement and remain active for a few seconds after the door (Box) is already closed.
4. When the Wasp sensor finally changes to off (motion stops), the integration checks the Box state. It sees the door is off (closed).
5. This (incorrectly) triggers the WiB logic. The integration starts its delay timer because it assumes someone stopped moving inside the closed room, when in reality, the person has already left.

Proposed Solution

My suggestion is to add a new optional setting, perhaps a "grace period" or arming_delay_after_door_close (e.g., 15 seconds).

This new delay would change the logic as follows:

The WiB integration should only "arm" itself (i.e., start monitoring for a Wasp that stops moving) after the Box (door) has been in the off (closed) state for this new grace period.

How this would fix the problem:

1. I enter (Door=on, Motion=on).
2. I exit and close the door (Door=off, Motion=on).
3. The integration sees the door is now off, and it waits for the new arming_delay_after_door_close (e.g., 10 seconds) before it starts monitoring.
4. During this 10-second grace period, my motion sensor's cooldown finishes (Motion=off).
5. The 10-second delay ends. The integration now arms itself, but since the motion sensor is already off, the WiB logic is not triggered.

This would effectively ignore any "stale" motion from the act of exiting and only trigger if motion is detected (and then stops) after the room has truly been closed for a few seconds.

This would make the feature much more reliable for those of us with standard PIR/presence sensors located near doorways.

Thank you for considering this improvement!

[jseidl]

This is what the delay option is for. It will ignore new motion events until that grace period has passed.

When the door opens or closes, WIAB will clear the wasp and wait until delay seconds before considering the wasp again. If there is movement the WIAB will be on again but will be set back to off after delay.

How long do you have your delay set to?

[Adavidebaba]

ok now i get it, the logic is perfect!
i was ignoring my presence entity, didn't realize it was included, and looked only my moving entity, so i didn't get the cause.
Increasing by 30 second the dalay solved the problem.
Sorry, my fault!