Alarms judge every change against the values it was written with
v0.2.12
•Platform
Bug Fixes
Alarms: a change to a limit or another value an alarm compares against is judged together with the value it was written alongside, so a burst of writes no longer raises a false activation.
Alarms: enabling, disabling, shelving and acknowledging an alarm each take effect once. An alarm no longer logs a spurious Unshelved when its monitoring restarts, and a shelving set or ended while monitoring was moving is still logged and announced.
Alarms: an alarm reads every value it evaluates from its own live feed, so it never mixes a fresh value with a stale one.
Integrations: a service that takes over part of the work receives exactly the changes made after it took over, in the order they were made, even while it is still picking up more work. A leftover assignment is reclaimed only by the service that held it.
Demo: a fresh demo install opens its Building Operations dashboard for a guest without an Access denied message.
Config Manager: generating a deploy key while the configuration service starts or moves no longer leaves the public key blank or showing the previous key.
Performance
Alarm sounds: the alarm sound player checks which alarms to play with a few batched queries instead of several reads per alarm and per session, which cuts its load on a node with many alarms.
Scripts: permission checks on the calls a script makes reuse a cached copy of the type definitions, so each call no longer fetches them again.