I’ve just been alerted three times in rapid succession that the temperature is low. I do not think there is any need to send the same alert so often in any use case I can think of. If there is a use case where you need frequent notifications that I haven’t thought of then we should be able to set a maximum frequency. It must be utilising your server extra too.
Do you mind my merging this request with another one? The universal solution should solve such issues.
It’s roughly the opposite of what they want there. They want an extra notification if a device state is beyond a time limit. I want less of the current notifications, as currently it lets me know several times when the temperature crosses the set value, presumably when it is oscillating around the set temperature. After the first notification it is redundant to keep sending me more notifications. If it were in Node Red I’d just add a “Delay” node set to Maximum Frequency of 5 minutes and to delete extra messages. Bit stupid of them to call a maximum frequency Node “delay”.
Notifications should be an optional feature along with scenes.
While the “ongoing trigger” is the mechanism behind the need.
Yes, I think we mean the same thing with different words now. I have no problem with notifications but the choice is no notifications or too many notifications. With the older devices I guess the memory is too small for anything but Yes or No but with ESP 32 devices I think the memory is sufficie fly big to include a maximum frequency.