@dschaible
This is what I thought I would do. But then the controllers with the handled setpoints also need to be connected to the UPS, as well as the network switches between them if they are connected over the network. And in a typical installation, with controllers installed on each floor, It can be complicated and expensive to wire all the controllers through UPS, and even a large expensive UPS lasts a limited time.
I was thinking of partly workaround this by placing a single controller next to the mango and connecting both to the UPS, setting all controllers to constantly read the values from that controller. Needless to say, this is not possible in every controller, especially a not programmable one. Still in case of a longer power outage, when the UPS goes out of battery, and meantime the schedule needs to be inactive, for example, and then the power comes back the setpoint will be in the status it was in when the schedule was active because the mango does not trigger the handler when it is turned on.
Another option is to check out what I saw in the forum regards syncing a schedule with a BACnet schedule, although I'm not entirely sure I understood what needed to be done, and whether exceptions also sync, which is essential.
And overall, what if the handler is not a setpoint handler at all? Such as email, etc? UPS will not help in those cases.
Basically, the thing here is an activated schedule triggers the handler only once, at the start time, and not again. For example, someone can accidentally turn off the lights using a wall switch while the schedule is active. To prevent that handler types should be can be configured, only once or repeated, meaning "repeat all the time when the trigger is active", So the lights soon turn on after accidentally manual override (except higher BACnet priority, safety, etc.) or power outage.
This is my first experience with Mango and I hope this issue is resolved so I can use it.
