Hi,

A few weeks ago, I bought several Tapo P110M, 1x T315, 1x H100, and a dehumidifier that restarts after a power outage. All of this was to control the humidity of a room based on the humidity and the temperature of the same room.
 

However, I have noticed a major problem in the automation logic that makes it nearly impossible to do anything:

When I set a humidity trigger on the T315 and a temperature condition (if statment), the automation never triggers.


 

Examples:

I place the T315 and the H100 right next to my router to eliminate any communication problems (I am 100% sure that this is not the issue).
*In the following examples, the automations are always effective (without time restrictions) and obviously enabled.
*H100 firmware: 1.5.12 Build 240320 Rel.123648
*H100 and T315 hardware version: 1.0
*Tapo app version: 3.4.512

 

1. Automation that works 100%:

• Room condition before creating the automation: 20°C, 60% RH
• Trigger: humidity > 65%
• Condition: none
• Action: send a notification

-> I increase the room humidity to 70% (temp still ~20°C)
-> Notification received
 

I modify the automation:

• Room condition before modifying the automation: 20°C, 70% RH
• Trigger: humidity < 65%
• Condition: none
• Action: send a notification

-> I decrease the room humidity to 60% (temp still ~20°C)
-> Notification received

I repeated these two steps several times, the notifications were always received.

 

2. Automation that does not work:

• Room condition before creating the automation: 20°C, 60% RH
• Trigger: humidity > 65%
• Condition: Temperature < 30°C
• Action: send a notification

-> I increase the room humidity to 70% (temp still ~20°C)
-> No notification sent.
 

I redo the automation:

• Room condition before creating the automation: 20°C, 70% RH
• Trigger: humidity < 65%
• Condition: Temperature < 30°C
• Action: send a notification

-> I decrease the room humidity to 60% (temp still ~20°C)
-> No notification sent.
 

I repeated these two steps five times in a row, so I should have received 10 notifications. None were received.

 

3. If I add an on/off trigger on a P110M:

• Room condition before creating the automation: 20°C, 60% RH
• Trigger: humidity > 65% or P110M on/off
• Condition: Temperature < 30°C
• Action: send a notification

-> I increase the room humidity to 70% (temp still ~20°C)
-> No notification sent by the humidity trigger.
-> After that, when I turn the P110M on or off -> notification received every time, so temp condition works as intended with another trigger.

 

It seems that it's not the temperature condition that's not working, but rather that the mere presence of a temperature condition prevents the humidity trigger from functioning, even when the temperature condition is met, and the humidity crosses the trigger threshold in the correct direction.
 

I have been pulling my hair out for two days trying to understand why it doesn't work. My automations were more complex initially, but after many attempts, I discovered this simple scenario that demonstrates the malfunction.
 

My main question is whether it's only my device that has this problem, or if it is widespread?
In the latter case, I really hope we get a quick fix... Because I am left with all this equipment that is useless to me currently.



On a side note: If only there were a "run every x minutes/hours" trigger, I'm almost certain I could manage by adding humidity and temperature conditions that would be tested at regular intervals (every 10-15 minutes for example). Unfortunately, this feature is greatly missing for many other scenarios as well. But this would not eliminate the current logic problem either...