@Wayne-TP 

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. 🥴

  @Wayne-TP 

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?

  @Wayne-TP 

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? 

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.

  @Wayne-TP 

Hey,

I just jumped in the TP-LINK/TAPO ecosystem with multiple devices and H200 hub. I am trying to create temperature based automatizations with T315 sensor, P110M plug and it does not seem to work. I have 2 shortcuts HOME and AWAY which I use when I get home or go away and I want to use temperature sensor to control smartplug with heater plugged in ONLY when I am home. I created 2 automatizations: TURN ON when temperature falls bellow threshold and TURN OFF when it exceeds threshold. Now I turn on or off these automatizations with home and away shortcuts but when i turn automatizations on it DOES NOT register current temperature and fire respective automatization like when I turn it on manually. It only fires when it reaches threshold temperature while already active.

Is there any way to make this work without making billion automatizations for each temperature treshold possible as some suggestions above?

If not is there any ETA on patch to fix this in my opinion HUGE oversight?

Hello @Masl0,

I am trying to tune these automations for almost a year and my conclusion is that TPLINK solution really is not reliable and you have to setup several workarounds.
Except of the facts described here, that temperature trigger fires only when the temperature is crossing the value, the automation procedures sometime simply does not start or do not execute all the steps.
My recommended solution for your case:
- TURN ON: add more activation triggers in the automation, like temperature below 21 + below 20,5 + below 20,0 + etc.

- TURN OFF: add more activation triggers in the automation, like temperature above 22 + above 22,5 + above 23 + etc.

Next workarounds: As the temperature triggers often does not work, I highly recommend to add safeguard procedures:
- SAFEGUARD ON: Add automation triggered not by temperature sensor but day time, starting e.g. 01:00 + 02:00 + 03:00 + ... 23:00

add condition : IF temperature below 21 / action: turn plug ON

- SAFEGUARD OFF: same like above, just IF temperature above 22 / action: turn plug OFF

In case you need more precise control create safeguard timestamps more frequent, e.g. I defined the timestamps every 20 minutes, this method is more reliable, although it requires three automation procedures for each SAFEGUARD ON / OFF, because you need to workaround the limit for maximum count of the the activation triggers.

Despite of my request the application still does not support triggers like every hour or every 10 minutes, so you have to create many trigger points.

I personally completely gave up the triggers based on the temperature sensor and I use activation based on the day time only. 

The actions originaly expected to be defined as activation triggers are defined in the "if condions" sections.
It is quite clumsy, but at least it works somehow.

BR, Frantisek.