Motion Detection Automation – Plug Turns On Only After Second Trigger
Hi,
I’ve been experiencing an issue with automation using the Tapo T100 motion sensor and the P100 plug. My automation is set so that when motion is detected, the plug should turn on.
If there is continuous movement in the room, everything works fine – the plug turns on immediately after the first detection.
However, if there’s no movement for about 10 minutes, the plug only turns on after the second detection. After that, it again reacts properly to the very first detection. I also tested this with an LED strip instead of the plug, and the result was the same.
The event history shows that the first detection already triggered the automation to turn on the plug, but in reality, it wasn’t executed.
This function used to work fine, but something must have changed some time ago. Unfortunately, I don’t know exactly when the problem started.
Since I use this automation as night lighting, the fact that it only switches on after the second detection makes it too late.
Could you please advise what might be wrong?
Thank you,
Pavel
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello,
I feel like a fool. Didn’t TP-Link make some server-side changes in my case? If not, then the solution is simply replacing the battery in the T100. The app didn’t report a low level, everything looked fine, but after replacing the battery everything works perfectly.
Pavel
- Copy Link
- Report Inappropriate Content
Hello,
I am running into an issue with automation reliability and would appreciate any suggestions.
Troubleshooting steps I’ve already tried:
-
Reassigned the T100 to a different HUB.
-
Connected the P100 to a different WiFi network.
-
Tested using the T100 to switch on the L930 LED strip (instead of the P100 socket) → the behavior is identical, the LED strip turns on with the same delay.
Test results (motion detection → automation trigger):
-
10 minutes – works correctly, responds to the first motion
-
20 minutes – works correctly
-
30 minutes – works correctly
-
60 minutes – responds only on the second motion detection
Other automations with the T100 work instantly (e.g. rotating a camera upon motion detection).
Additional tests:
-
Created a shortcut to turn on the P100 and set the T100 to trigger that shortcut → same delayed result.
-
Verified there is no power-saving mode or similar feature enabled on my network.
This automation used to work without issues, but I believe the problem started approximately two months ago.
Does anyone have any ideas on what could be causing this behavior, or possible workarounds?
Thank you,
Pavel
- Copy Link
- Report Inappropriate Content
What's the signal strength of this P100 and the L930? Which Tapo hub do you use? Hardware and firmware version?
From your test results, it seems like once the automation is created, if the sensor stays 'inactive' for over 60 minutes, its automation linked with the plug or light strip only takes effect in the second activation?
What's the detection interval set for the sensor?
- Copy Link
- Report Inappropriate Content
Hello,
it is exactly as you described. After about an hour, when I enter the room, I see the LED on the T100 blink, but the automation does not trigger (in the app log, however, it is recorded as executed). I thought the response might be delayed, but it isn’t. Only the second motion detection turns on the LED strip or the P100 socket. After that, everything works correctly on the first detection for roughly another hour.
I know this automation used to work correctly, but it stopped working some time ago. Unfortunately, I don’t even have an approximate idea of when that happened, as I didn’t pay attention.
I also notice that some automations should be managed by the HUB (indicated by the house icon on the right of the automation). I only see this icon on some automations, but not on this one, so it appears to be managed remotely.
I assume there is some issue with sending the request from the TP-Link server to activate the socket or LED strip on my device.
My hardware setup:
-
Sensor T100 – signal -42, firmware 1.12.0, response time 8s, sensitivity normal
-
LED strip L930 – signal -53, firmware 1.2.5
-
P100 socket – signal -51, firmware 1.5.5
-
Originally used HUB H100 – signal -34, firmware 1.5.2.3
-
Newly tested HUB H500 (connected via LAN) – firmware 1.3.1
Thank you,
Pavel
- Copy Link
- Report Inappropriate Content
Hello,
I feel like a fool. Didn’t TP-Link make some server-side changes in my case? If not, then the solution is simply replacing the battery in the T100. The app didn’t report a low level, everything looked fine, but after replacing the battery everything works perfectly.
Pavel
- Copy Link
- Report Inappropriate Content
PavelV wrote
Hello,
I feel like a fool. Didn’t TP-Link make some server-side changes in my case? If not, then the solution is simply replacing the battery in the T100. The app didn’t report a low level, everything looked fine, but after replacing the battery everything works perfectly.
Pavel
Did you email the support team? If not, then the battery is the savior this time. I recommend continuing to monitor the performance of your devices.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 637
Replies: 5
Voters 0
No one has voted for it yet.