Solution Smart Action: T310/T315 Temperature or Humidity Automation Doesn't Take Effect
05/15/2024 Update Delete solutions for the special cases where the automation does not take effect immediately if T310/T315's current value has already reached the set threshold or range when creating the automation.
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., "Over" or “Below"), the automation will not be activated.
For example:
Creating an Automation using Tapo T310 as the Trigger device: When T310 temperature over 20℃.
| Changes | Automation Activated? | Note |
| When creating/saving the automation (Current temperature 25℃) |
Yes |
When saving settings, the Tapo App verifies the current temperature/humidity data against the automation settings.
If the current values meet the trigger conditions, a pop-up window will prompt you to either execute the action immediately or skip it. |
| 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 cross over 20℃. |
| Rise from 21℃ to 25℃ | No | Not the set behavior: Temperature (cross) over 20℃. No temperature crossing behavior occurs.
|
| Drops from 25℃ to 19℃ | No | Not the set behavior: Temperature (cross) over 20℃. |
Troubleshooting Tips
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, Over/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 the signal strength on both Tapo sensor and the hub. Adjust device's location if the signal is weak.
- For the Tapo sensor and H100: go to device's settings page ->Device's Info -> Click the signal icon to show the RSSI rate.
- For the Tapo H200: go to device's settings page ->Network Connection -> Click the signal icon to show the RSSI rate.
- Switch H200 to ethernet connection if it was wirelessly connected.
|
Connection Diagram of Tapo SubG Devices in the Network
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Why don't we get any answer anymore? It seems like many people asking for the same and u might be the only one that can help us getting our request fixed by the tp-link staff. 🥴
- Copy Link
- Report Inappropriate Content
The feedback has been recorded already. At this time, we have not received any news on this matter so we cannot provide further information.
You may keep an eye on our official website or community for the latest product developments.
- Copy Link
- Report Inappropriate Content
Hi,
I'm trying to use the T310 to control a fogger in my greenhouse.
Using Auto-Humidity Control in the App:
Effective Time
10:00am - 5:00pm
Every day
When
Humidity below 85%
Temperature over 25.0 C
Then
Fogger
Turn on for 3 min
Last "On" State
Delay Action
10 min
Fogger
Turn on for 3 min
Last "On" State
This is not working. I want it to come on for 3 minutes every 10 minutes if the conditions are met but cant get it to work.
Any suggestions?
- Copy Link
- Report Inappropriate Content
Phil-S wrote
Hi,
I'm trying to use the T310 to control a fogger in my greenhouse.
Using Auto-Humidity Control in the App:
Effective Time
10:00am - 5:00pm
Every day
When
Humidity below 85%
Temperature over 25.0 C
Then
Fogger
Turn on for 3 min
Last "On" State
Delay Action
10 min
Fogger
Turn on for 3 min
Last "On" State
This is not working. I want it to come on for 3 minutes every 10 minutes if the conditions are met but cant get it to work.
Any suggestions?
Please note that ANY rules in the "When" section can start the automation. Is the current setup what you want? Do you need to move any rules to the If section?
The action settings does not loop, once all the actions included in this automation have been executed, the automation will end. Therefore, if your automation setup consists of only the three actions mentioned in your description, nothing further will occur once those actions are complete.
- Copy Link
- Report Inappropriate Content
I found this thread after an automation did not trigger once the temperature dropped past my trigger for some reason and with only the one threashold, it did not trigger as the temperature continued to drop. It sounds like it would be recommended that you always should add multiple triggers at several temperatures below (or above depending upon the application) your target to guarantee that the automation triggers.
To make sure that I understand the multiple triggers solution and how it operates. The approach is to add multiple triggers to the same automation, not create multiple automations with different trigger temperatures? Correct? Each of the "When" triggers are OR operations and not AND operations? Correct?
- Copy Link
- Report Inappropriate Content
I have similar troubles for auto temperature control.
Even if now in the recommended automations from the tapo app
you can find an auto humidity control, (see picture below)
This automation most probably always verifies the low and the high range, and supposely automatically checks also the current humidity during the automation activation, and for example if you need between 30 and 60, and you are now at 20 and you start it, the automation will not wait that there is a low threshold violation before starting the humidifier. In the same way for the upper threshold.
I didn't try this automation, but if the implementation is in the right way, should do the things I mentioned.
But now, I'm astonished that tapo implemented this auto humidity control but no auto temperature control.
Come on guys, which automation do you think would be mostly used?
I believe the temperature one.
So unless tapo creates this kind of automation,
You always need to use two automations to check the high and low threshold Plus you always need to make sure when you turn on or turn off the automation that you are in the right state with the heater.
So this is really poor.
And by the way, I don't know why tapo don't offer a complex scriptic automation implementation, so that people who have more complex stuff to manage would poorly write a code or pseudocode so that we are not limited to tour three possible conditions from the app.
- Copy Link
- Report Inappropriate Content
DumbAu wrote
I found this thread after an automation did not trigger once the temperature dropped past my trigger for some reason and with only the one threashold, it did not trigger as the temperature continued to drop. It sounds like it would be recommended that you always should add multiple triggers at several temperatures below (or above depending upon the application) your target to guarantee that the automation triggers.
To make sure that I understand the multiple triggers solution and how it operates. The approach is to add multiple triggers to the same automation, not create multiple automations with different trigger temperatures? Correct? Each of the "When" triggers are OR operations and not AND operations? Correct?
For such a situation, you can indeed consider adding multiple triggers within the same automation. "When" trigger operates in OR logic, the automation runs when any trigger is activated.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5513
Replies: 27
Voters 0
No one has voted for it yet.