Solution Smart Action: T310/T315 Temperature or Humidity Automation Doesn't Take Effect
This Article Applies to:
Tapo T310
Tapo T315
Issue Description/Phenomenon:
If you are experiencing issues with the automation created using Tapo T310/T315 and it is not functioning as expected, please check if you fall into one of the following situations.
To ensure a proper understanding of the activation logic employed in Tapo Automation for the Temperature and Humidity sensor, it is essential to take note of the following:
If you are utilizing temperature or humidity changes from the Tapo T310/T315 sensor as a trigger for your automation, please make sure that the changed value must cross the set threshold to activate the automation as intended. If the value is equal to the threshold or the changed behavior does not match the set Trigger condition (e.g., Goes “Above" or “Below"), the automation will not be activated.
For example, creating an Automation with Trigger: When T310 temperature goes above 20℃.
| Changes | Automation Activated? | Note |
| Rise from 18℃ to 22℃ Rise from 20℃ to 21℃ |
Yes | / |
| Rise from 18℃ to 20℃ | No | The changed value (20℃) equals the set threshold, it does not go above (cross) 20℃. |
| Rise from 21℃ to 25℃ | No | 1. The initial value is already above 20℃, any subsequent increases will no longer trigger the automation. 2. No "goes above 20℃" behavior occurs. |
| Drops from 25℃ to 19℃ | No | The change is not the preset behavior: "Goes Above". |
Note: If you're not in one of the mentioned situations here below, please refer to Common Troubleshooting Tips at the end to check and ensure all settings are being configured correctly.
1. Case One:
- Effective time: Always
- Current value is already reached the set threshold or range when creating the automation.
E.g. Automation: When T310 temperature goes above 20℃, turn on P100.
If the current temperature is already 25℃ when creating the automation, the automation will not be activated immediately since there is no value change after the rule is created.
Solution:
1. Update Tapo APP to Android 2.16.110 or iOS 2.16.103, or higher version.
2. Create a new automation rule. Or make a slight adjustment to the current automation then save it again.
2. Case Two:
- Effective time: Custom (e.g. 8:00 am - 15:00 pm)
- Detected value reaches the set threshold or range before the effective start time.
E.g. Automation: From 8:00 am to 15:00 pm, when T310 humidity goes below 70%, turn on P100.
If the humidity drops to 60% before 8:00 am and maintains below 70%, P100 will not be turned on after 8:00 am because the humidity does not go below 70%.
Solution:
<08/08/2023 Updated> The automation logic has been optimized, update Tapo APP to Android 2.16.110 or iOS 2.16.103, or higher version.
Common Troubleshooting Tips <Tapo T310/T315 Automation Is Not Working>
1. Ensure device firmware, Tapo hub, and Tapo APP are updated.
2. Check if the automation rule is set correctly. (Trigger and Action device, trigger value, Above/Below, Effective time, etc)
3. Check if the detected value is updated in time in the APP or on the screen (For T315 only).
4. Check if there are any disconnection issues, such as the sensor disconnecting from the Tapo hub, or the Tapo hub disconnecting from the router network. If there is, ensure you're getting a good and reliable connection by modifying the wireless settings on the router or adjusting the location of the T310/T315 and the Tapo hub.
5. Try to create a new automation rule, or edit and save the existing rule again. The newly saved automation will check the current status of the device and make an immediate evaluation. If the temperature or humidity at that moment meets the triggering conditions of the automation, the corresponding automation rule will be activated immediately.
