HC3 Device Notifications

[Anssi 0]

Could someone explain the device notification intervals in HC3? I have a temperature sensor from which I'd like to have a notification when the temp drops below a defined low level.

 

In device notifications I've ticked the "Low temperature" and selected the interval of "Once per day".

 

Now, once the temperature goes below the low temperature limit I start receiving notifications every single time the device sends a new temperature. That happens several times per hour, depending on how fast the temperature changes. That is not once per day. What am I not understanding?

Edited February 9 by Anssi

[Fabir 65]

@Anssi The notifications are meant to be used for rare events, like an oven overheating or a room with water pipes, that shouldn't be freezing when the temp falls below a defined degree Celsius. Every time the condition becomes true, you will get another notification.  As you have experienced, this can become disturbing.

 

I recommend you to use a scene, where can set multiple trigger conditions. Like the bandwith < low > high of degrees, this scene should be triggered.

And also a scene can be disabled / enabled when needed. With notifications, you would have to go into the settings in order to stop it. 

Edited February 12 by Fabir

[Anssi 0]

Sure, I can make a scene for the same thing, but that's not the point. The point is that we have this option of setting an interval for a notification, but it doesn't do anything. To me this looks like a bug.

[m.roszak 533]

It is an interval for re-sending again the notification if condition is still true.
It will send it once a day in your case if temperature drops and stays there

[Anssi 0]

On 2/13/2024 at 6:28 PM, m.roszak said:

It is an interval for re-sending again the notification if condition is still true.
It will send it once a day in your case if temperature drops and stays there

That's what I thought, but it doesn't work that way. HC3 will resend notifications regardless of the interval while the condition is still being true. Sorry, I didn't emphasize that enough in the beginning.

 

Example:

1. Set freezing temp warning to 5.0 and interval to 24 h

2. The temp goes down from 5.5 to 4.9 --> notification, as expected

3. 15 minutes after that the temp goes to 4.8 --> new notification

3. 30 minutes after that the the temp goes to 4.5 --> new notification

...and so on.

Edited February 18 by Anssi

[m.roszak 533]

Ah, yep - it was designed to work with life danger sensors (binary ones) at the beginning and it stayed like this, I understand what you mean now - I will put a task to the team in a backlog to change this behaviour in the future. 

[Anssi 0]

Thanks @m.roszak for taking it to the dev team.