UI behavior when Notifications are None

[thom_smith]

Red is bad. Except when I don't care and it is not. I have several outputs, both real and virtual, which have a maximum on time but notification is none because they are just timers to make something happen after some other action or they are just plain unimportant. Since exceeding max run time is expected/accepted behavior which happens routinely, I find it annoying that status tiles appear red typically indicating an alert condition. Is there any way to change the UI behavior to simply highlight (like they are on if Run Past Max On Time is enabled) or grey (if Run Past Max On Time is not enabled) if Notifications are None rather than turning red.

 

[BR260354]

Same boat. I'm trying to figure that out. I want to run a motorized ball valve for just 20 seconds. I set max run time and do not exceed. It powers on for 20 seconds and turns off BUT I have the RED exceeds. Well, it really didn't exceed if the power is now off!

 

[Sole83]

The red status is the default alert behavior in Hydros when max run time is set, even if Notifications are None. Currently, there’s no built-in way to change it to grey or just highlight without triggering red. You can provide feedback to CoralVue for a UI update, or as a workaround, avoid setting max run time on outputs where red alerts are not meaningful.

 

[thom_smith]

Same boat. I'm trying to figure that out. I want to run a motorized ball valve for just 20 seconds. I set max run time and do not exceed. It powers on for 20 seconds and turns off BUT I have the RED exceeds. Well, it really didn't exceed if the power is now off!

It did exceed the max on time. That is what triggered the output to turn off. If, for instance, you had run past max on time toggled then tile would be red BUT output would still remain on and valve would be open.

The red status is the default alert behavior in Hydros when max run time is set, even if Notifications are None. Currently, there’s no built-in way to change it to grey or just highlight without triggering red. You can provide feedback to CoralVue for a UI update, or as a workaround, avoid setting max run time on outputs where red alerts are not meaningful.

There is a difference between red tile and red notifications/alerts. Notifications are individually enabled below the input or output and then you set the notification level. Red would typically have an audible notification associated. With the notification level set to none, there is no notification nor audible alert. It is just the slightly annoying red tile. As for avoiding max run time, it is necessary in cases when you want to dynamically turn on an output or perform some action based on the state of another output which doesn't go by a fixed schedule.