That’s why both profiles exist. And indeed the two different debounce profiles and the rule template each individually address different use cases as well.
| Approach | Reduces | Purpose |
|---|---|---|
| round profile | changes | rounding the value before updating the Item, the Item still updates |
| debounce count | updates | throw away every count-1 updates and only posting the count one regardless of what the values are |
| debounce time | updates | throw away every update that happens within the time period of the last posted update regardless of their values or how many there are |
| filter JS Scripting profile | changes | require a change above a given amount from the last posted update; if the change isn’t large enough post the last posted value |
| debounce rule template | updates | works with any Item, not just Items with a link to a Channel and can be used when you only want to debounce one or more possible states (e.g. debouce OFF but immediately process ON) |
If you ever need to do both a rounding and a debounce, you’d probably need to use the round profile and the Debounce [4.0.0.0;4.9.9.9].
I’m glad you are getting to a working point. I too have added the round profile to a few of my sensor Items to lower how often a few of my rules run as well. I wasn’t seeing any performance or load problems or anything like that but it seemed an easy thing to do to reduce the load a bit just because I could.