No coding necessary. Just select the time to ignore multiple triggers from the same source. Where do I find that option?
Thank you!
Your topic title implies there was new functionality added to Home Assistant in 2021 specifically for debouncing. I’m unfamiliar with any such addition. Can you elaborate where you read such a thing was added this year?
What has been available for a long time is the for
option and it is supported by at least three kinds of triggers: Numeric State, State, and Template.
You can use
for
to have the state trigger only fire if the state holds for some time.
However, its usage for debouncing is largely dependent on the entity’s behavior.
Thank you for the reply. For instance if a binary sensor is noisy while in the state ‘on’ the trigger seems to accumulate and store multiple triggers even with for xx:xx:xx, then when ha is able to catch up seemingly random instances of that automation happen for quite some time after the fact. So I was hoping I was correct about reading of a new trigger option that makes these issues a thing of the past. I do see plenty of coded solutions per type of sensor like for the esphome. Thank you again
But where did you read this?
Again, where did you read about a “new trigger option”.
I assume you know that esphome and automation triggers are two separate concepts and a “coded solution” for one is unusable by the other.
You are correct that all of the different integrations have there own methods of coding a debounce. For instance ESPhome, SonOff, MQTT methods, NODRED, and so on. The For x time does not work as de bounce. Thank you for your help.
You don’t appear to be using the word ‘integration’ correctly because the examples you listed aren’t all Home Assistant integrations.
I would explain how but I feel it would be a waste of time, just like asking you where you read about a “new trigger option”.
Granted the grammar in the first two sentences is misleading, but it should be clear that Joe3 wouldn’t be asking a question at all, if it isn’t “where do I find that option?”
And I also think it would be a useful feature, because the current workaround of using templates involves using a named reference, which is less than ideal even from a software engineering standpoint.
You’re a year and a half late to the discussion. The topic’s original title was misleading.