[206] Event Controller Door Opened/Closet event action 2 inconsistent behavior

Engi shared this bug 21 days ago
Not a Bug

With AND gate OFF:

Action 1 does not require all doors to be opened to fire action 1.

Action 2 requires all monitored blocks to meet requirement to fire action 2 even with the AND gate off.

1. place 3 doors on a powered grid with antenna

2. place an event controller on the grid and setup to monitor all 3 doors (do NOT check AND gate)

3. have action 1 close 2 of the doors (one door will be left open)

4. place broadcast controller on grid and have message one say Door Closed

5. open either of doors one or two that will be closed by the EC. Result: they are auto closed after they open and the BR says Door Closed. Normal

6. now open the third door that does not get closed so that it stays open.

7. repeat step 5 so that one of the 2 doors that close is opened and closed automatically. Result: the BR does not send Door Closed message.


The AND gate is NOT on, it should not require all doors to be closed in order to send the door closed message with action 2.

Replies (2)

photo
1

Hello Engi,

Thank you for reaching our forum with this.

We have reproduced this issue on our side and put it into our internal system.

Kind Regards,

Keen Software House: QA Department

photo
1

Hello Engineer,

Thank you for the report! We internally reviewed the behavior, and it’s not a bug — it’s actually how OR gate logic works when the AND gate is disabled.

Here’s what’s happening under the hood:

With the AND gate off, the Event Controller uses OR logic. That means it checks each input individually, and as long as one or more inputs are true, the output stays true.

To give you a simple logic example:

  • If Input A is false and Input B is false → Output is false
  • If Input A is true and Input B is false → Output is true
  • If Input A is false and Input B is true → Output is true
  • If both inputs are true → Output is also true

The output only becomes false if all inputs are false at the same time. So if even one input remains true, the output stays true, and the system won’t reset the condition or re-trigger the action.

That’s why Action 2 doesn’t trigger again when one of the inputs is still active. From the logic’s point of view, the condition was never fully turned off.

If you'd like to dive deeper into how OR gates work, here’s a short external explanation:

👉 https://logic.ly/lessons/or-gate/


Best Regards,

Keen Software House

Leave a Comment
 
Attach a file