@rockinghawk 

In automation, it's quite common to use the same device in different automation rules as both the Trigger or Action device, which often leads to repeated triggering or activation. Conflicts are unavoidable. In fact, they often align with the requirements of many automation scenarios, where the device status needs to be toggled whenever the trigger activates.

In your case, I believe you've set the action to "Turn on/off device," which results in the device returning to its initial state when this action is executed twice, making it seem like it's redundant.

In fact, both scenarios you described involve turning on the light. You can set the action command to "Turn on" instead. Even if both automations are triggered simultaneously (press button and sensor movement detected), they will execute the same action, turning on the lights, without canceling each other out.

  @rockinghawk 

Actually, a new Trigger "No Motion Detected for a Set Time" will be implemented shortly for the Tapo T100 motion sensor. Creating another automation with this trigger to turn off the light will be the ideal solution to your concerns.

Smart Action 2.0: Unlock Next-Level Smart Home Automation