A template trigger fires when the template changes from false
to true
:
So it’s not quite what you need here.
A template trigger fires when the template changes from false
to true
:
So it’s not quite what you need here.
Thanks for the hint. Indeed, this is not what I need.
Hoping you still have a bit of patience for me, I will ask what I think is the last question. How do you mitigate the switching in boundary conditions, i.e. when the PM2.5 value fluctuates between, say, 29 and 31? I am leaving aside the issue of the fan, the buzzer is very annoying.
You could employ the for:
feature in the state trigger, to only fire when it’s been in the same state for, say, 5 minutes.
I will.
Many thanks, sincerely. Cheers!