@cnj85bcn I have the exact same problem. If there is more than one condition for an automation, they are treated as 'any', even though they are set up as 'all' must be met. This started somewhere over the Easter weekend. I haven't found a solution, this seems to be a bug on Tapo's end. 

  @cnj85bcn 

I have exactly the same problem. It started doing this yesterday. Did not change a thing and all my automations started triggering completely disregarding the conditions. It's behaving as described, instead of applying the rule "all conditions must be met" it applies the rule "any condition is met". It's a server side bug.

I can't believe they made a buggy commit without thorough testing, what a joke. A rookie mistake.

I'm using TAPO P110M + TAPO T315.

  @Wayne-TP Thanks for getting back to me.

I believe this is rather a software problem since actions can be trighered by switches, sensors and other devices. The hardware devices involved are behaving normally otherwise.

My situation:

I use several automations regarding lights, temperature (heating), enabling and disabling devices and lights with motion sensors etc.It took a while to figure out why some of the automations started misbehaving.

Simplified example scenario I programmed to test this (in reality my automations are more complex and involve shortcuts/groups of devices and times of day/sunrise/sunset etc., but the principle is the same):

Button S200B acts as an advanced light switch for several lamps that are plugged into P100 plugs ('lamp 1', 'lamp 2', 'lamp 3'); button is connected to Tapo hub H100.

Automations:

1) Single tap | if lamp 1 is off | switch on lamp 1

2) Single tap | if lamp 1 is on | switch off lamp 1, 2, 3

3) Rotate clockwise | if lamp 1 is on AND lamp 2 is off AND lamp 3 is off | switch on lamp 2

4) Rotate clockwise | if lamp 1 is on AND lamp 2 is on AND lamp 3 is off | switch on lamp 3

5) Rotate anticlockwise | if lamp 1 is on AND lamp 2 is on AND lamp 3 is on | switch off lamp 3

6) Rotate anticlockwise | if lamp 1 is on AND lamp 2 is on AND lamp 3 is off | switch off lamp 2

Up until recenty, this set of automations would work like a 'dimmer', i.e. turning clockwise would switch on additional lamps 2 and 3, turning anticlockwise would switch them off in reverse order. Clicking once would turn on the first lamp, clicking again would turn off everything. Turning the button in any direction while no lamp is on would do nothing (as intended, since none of the conditions are ever met).

Now: Automations 1) and 2) work normally. Automations 3) and 4) fire at the same time when turning the button, likewise 5) and 6). They even fire when no lamps are on. All this can only be explained logically when the if-conditions are treated as 'any' instead of 'all'.

Testing:

• switched to 'any', then back to 'all' for conditions in existing automations in case something is 'stuck'
• restarted and re-paired the button
• signed out of the app and in again
• re-installed the app

• restarted the phone
• restarted the router
• restarted the hub

• restarted the plugs

Tapo app 3.10.232, iPhone 12 mini, iOS 18.4.1. All devices have the latest firmware.

  @cnj85bcn 

Good afternoon. My automations rely on a base one called "Alarm," which triggers if the door sensor is activated while I'm away. This also activates a "hub" automation that makes a sound, like a "check." I have other automations that depend on whether this one is active. For example:

1. If my motion sensors detect movement AND the "Alarm" automation is active AND the "hub" automation is not (meaning the alarm didn't go off—for example, the camera and alarm were activated due to inactivity [another automation], or I left but family members are still inside [another automation])—then it disables the "Alarm" automation and runs several shortcuts to disarm the camera.

2. S200B button: If pressed AND the "Alarm" automation is inactive AND a light is on, it turns it off, and vice versa.

3. When running a shortcut, I dim the lights and disable several automations, enabling a new one that sets a sensor into standby to turn on a room LED for only 2 minutes. This also activates another "check" automation. If movement is detected AND that automation is active AND the previous sensor also detects motion, the routine is executed.

I could go on—I have several automations that depend on others and various sensors, and others that depend on two sensors in sequence. As fellow users ChrisHitarori and Miroshi mentioned, the issue doesn't come from a specific sensor or automation. Like them, I've tested countless setups and on different devices. The problem lies in the execution logic. As a workaround, I've had to break down multiple subroutines so that my conditions only involve a single IF, until support or someone here confirms the issue has been resolved.

Good news. Update 3.10.502 has fixed the issue for me. 

  @Wayne-TP 

Yes the issue seems to have been resolved.

  @Wayne-TP 

Sorry for the delay. I've redone the automations and yes, it seems everything is now working as it should. Thanks!