Hi. I'm using TP-link tapo t310 and tapo p100 devices for this automation. I checked the forums about the issue, but those fixes didn't work.
Attached are the YAML of both automations
#Automation conditions don't seem to work.
tardy edge
i am not sure if it's an issue regarding the type of device or something else to be honest... the actions seem to work fine, it's just the conditions that aren't
slow furnace
a) The conditions are redundant, the trigger should be sufficient for that.
b) Does the actual value cross the trigger value? Meaning: does it rise from below 63 to above 63? Or does it drop from above 55 to below 55? The trigger will only fire once when crossing that threshold, not if it already happened.
Example: humidity rises from 62 to 64 - trigger fires. Humidity is 64 and rises further - trigger does not fire.
I would also recommend, to use the numeric_state trigger with the humidity entity instead of device trigger. Those cause less problems when changing the humidity sensor for example.
tardy edge
oh i just used the template trigger
slow furnace
The ones you showed are device triggers
tardy edge
so if i use the numeric state one for the humidity %, it will trigger ?
and does it have an equal or >= condition?
slow furnace
Only if it goes from below 63 to above 63 or for the other one from above 55 to below 55.
It is a greater than condition, not greater equal.
slow furnace
For an equal condition, a state_condition could be used. But that fires only at the exact value, not above, below or when crossing it.
tardy edge
do i remove the and if condition ?
?
"e se"
got an atribute slider after i put the hygrostat entity, do i leave it empty?
slow furnace
got an atribute slider after i put the hygrostat entity, do i leave it empty?
Yes, if you want to use the entity state itself. That attribute selector lets you use an attribute value, if needed.
slow furnace
If you use a trigger for a numeric_state above lets say 63, it is not necessary to add a condition to check, if it is really above 63 - otherwise it wouldn't have triggered.
In another situation, it might be needed. Let's say, you want that to trigger when it gets above 63 and when it is above 63 when you start HA.
In that case you would have one trigger for the numeric state and one for the HA start. It would fire when the value rises above 63 (good) and on every HA start (not good). In that case you would add that numeric state condition to filter out the unwanted triggers.
I hope that explaination was understandable 
slow furnace
You can use the state page of the developer tools (https://my.home-assistant.io/redirect/developer_states/), search for the entity and select it. When selected you can manipulate the state of that entity.