Automations based on motion sensors not working correctly
Automations based on motion sensors not working correctly
![](/avatar/avatar-24.png)
Hi,
I already posted this issue in the motion sensors thread, not really sure if its an issue with motion sensors or the hub so I'm posting it here as well.
When dealing with Automations, if the trigger is a motion sensor and the action is to turn on a light using the "on duration" function, for example if a motion detected in the hallway, the hallway light should turn on for 30 seconds. Sometimes the action is not taking place at all. Some other times, there is an extreme delay (30 sec till 2 minutes). It happens at random times during the day.
I'm not sure if this is an issue with the hub (H100) or the motion sensors. Sometimes they work without problems and the action is triggered instantly, other times it doesn't work or the action is delayed.
When the motion is triggered but the action is not talking place, I take a look at the tapo app, the motion is registered with a time stamp, but the action (turning on the light bulb for 30 sec) doesn't take place. Does that mean that the motion sensor did it's job just fine by reporting the trigger but the hub failed for some reason to turn on the light? Or could it be a bug in the automation script?
The sensors and the hub are very close to each other (2-4 meters).
Any suggestions would be great!
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
![](/avatar/avatar-20.png)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
![](/avatar/avatar-20.png)
- Copy Link
- Report Inappropriate Content
Hi, yes, it seems now I do not have delays, though I still have some concerns.
1. What do you mean "some optimization has been done"? What exactly this means? I did not see any FW changes in the hub, or in the motion sensor. Where this optimization was done?
2. The hub activity log is still empty. How can I make the hub logs again the activities?
- Copy Link
- Report Inappropriate Content
![](/avatar/avatar-20.png)
Hello @NyGabor
Thank you so much for sharing the update, glad to know now the delay is gone!
As far as I know, our team has pinpointed the cause and adjusted some parameters in regard to Automation, so that can be solved directly without a need to update the firmware.
Btw, the hub activity log is for the Alarm feature on the hub, in Explore Smart Action section, you could set up the hub as an Alam and check the log there.
How to Check Alarm Logs/Activities of Tapo Hub
For a different topic, feel free to Start a New Thread and let us know~
- Copy Link
- Report Inappropriate Content
![](/avatar/avatar-20.png)
Hello everyone,
Thank you for feedback in regard to the between Tapo senors and Tapo Wi-Fi product in an Automation/Smart Action.
Here we'd like to share some details about the fix, so the new community users can see the information in full and provide feedback in the correct channel
Applies to:
Tapo Smart Sensors/ Smart buttons with T100 hub.
Phenomenon:
Some users may notice there is delay in up to 2-4 minutes or even longer in the automation:
Tapo sensor (Trigger Device)senses the motion creates the motion-triggered log instantly, but it takes 2-4mins before the Tapo Wi-Fi product (Trigger Device) to execute the action.
Solution:
Fixed by TP-Link R&D team since Oct 24th,2022
This topic will be closed for further comment soon, if you have additional feedback with sensors, please Start a New Thread in the community and detailing your concern. Thank you.
Related Articles:
New Tapo SubGHz Family- Tapo Smart Sensors, Smart Switches, Smart Buttons and More on the Way
TP-Link Sub-GHz Technology
- Copy Link
- Report Inappropriate Content
Seems to be working correctly now. Thank you and everyone invloved in fixing it :)
- Copy Link
- Report Inappropriate Content
![](/avatar/avatar-20.png)
- Copy Link
- Report Inappropriate Content
![](/avatar/avatar-24.png)
Information
Helpful: 1
Views: 2827
Replies: 18
Voters 1
![voter's avatar](/avatar/avatar-24.png)