Tapo T100 motion sensors fails to trigger “when no motion is detected”

Tapo T100 motion sensors fails to trigger “when no motion is detected”

Tapo T100 motion sensors fails to trigger “when no motion is detected”
Tapo T100 motion sensors fails to trigger “when no motion is detected”
Friday
Hardware Version: V1
Firmware Version: 1.13.0

When using a motion sensor to trigger lights, the no motion detected works fine to turn lights off.


When you use the app or any other trigger to turn the same light on, the motion sensor will fail to use "when no motion detected" trigger in automations.

 

Once the sensors detects motion the when no motioned detected trigger works to turn the lights off...

 

This isn't mentioned anywhere and really hurts the usefulness of the motion sensors... when you create an automation it should at very least warn you that it must first detect motion for the when no motion is detected to work..

 

I have a ton of tapo devices and bought four motion sensors before I realized this flaw... it's making it hard to make reliable automations and have lights turn off when I want.

0
0
#1
2 Reply
Re:Tapo T100 motion sensors fails to trigger “when no motion is detected”
Yesterday

  @RJB91 

 

The ‘No Motion’ trigger does not work as a standalone timer that can activate “out of nowhere.” Without that initial motion,the automation would have no valid starting point. In practice, this could cause it to fire immediately and repeatedly, or at random intervals, in an illogical loop. For example, it might endlessly trigger actions like turning a light or fan on and off.

 

If you want the light to automatically turn off when it is turned on by other means, create separate automation rules for those actions.

CES 2026 Meet TP-Link AI Assistant and More New Products!
0
0
#2
Re:Tapo T100 motion sensors fails to trigger “when no motion is detected”
Yesterday - last edited Yesterday

  @Wayne-TP An action that lets me trigger the motion sensor from automation could easily solve my issue. 
 I have made a work around for the two issues I was having but one of then isn't as reliable as this would be.

0
0
#3