Keeping the building running

Recipes for the things that break quietly. Some of these Omaya already does by itself. A critical battery, a device anomaly and a gateway that goes offline each raise their own work order or alert. Do not build rules that duplicate those. The recipes below add a channel or an earlier warning.

A cold room or server room warming up

The question: Tell the on-call engineer when the server room passes 27 °C, and keep a record for the auditor.

Part	Setting
Hardware	A fixed temperature sensor on the wall or in the rack, not a tag someone carries
Data table	Temperature excursions: temperature number · room zone · sensor device
Rule watches	The sensor (or a label on every cold room's sensor)
Condition	Temperature greater than 27, held for 15 minutes
Repeat at most every	1 hour
Actions	SMS to on-call: {{zone.name}} at {{value}} °C; Add a row to a data table → temperature = {{value}}, room = {{zone_uid}}, sensor = {{device_mac}}

Because the rule writes one row an hour while it is too warm, count Records grouped by room and Date is "hours out of range per day", which is what a food safety or data-centre audit asks for. For a cold room, the condition is greater than 8.

Pitfall. Temperature comes from the hourly roll-up, so it can be a few minutes behind. For seconds, use Sensor reading (any field) temperature instead; it is checked as each reading arrives.

A water leak becomes a job

The question: When water reaches the floor under the pantry sink, a plumber should be on the way before anyone slips.

Part	Setting
Hardware	A leak sensor on the floor at the lowest point: Milesight EM300-SLD (spot), EM300-ZLD (rope along a run of pipe), WS303, or a toilet-supply leak probe
Rule watches	The leak sensor
Condition	Sensor reading (any field) leak_detected Becomes 1 (every leak sensor Omaya reads uses this field: the Milesight probes, Home Assistant moisture sensors and the toilet-supply probe)
Actions	Raise a work order: work type plumbing, priority urgent, title Leak at {{zone.name}}; SMS to the building manager

A work order is never raised twice for the same rule and place while one is open, so a leak that stays wet does not flood the Facility app with jobs. The job then follows the Facility app.

Page someone when a gateway drops

The question: A gateway went offline on Friday night and nobody knew until Monday.

Omaya marks the gateway offline and tells every active admin in the app. To reach someone who is not looking at the app:

Part	Setting
Rule watches	The venue or location (any gateway in it), or one gateway
Condition	Gateway status equal to offline
Actions	Telegram to the support group: {{gateway_name}} is offline; a second rule with online says when it is back

It fires once per change, so a gateway that flaps sends one message each way, not one a minute. The record is Reports → Gateway Availability, which can be emailed weekly under System › Schedule Report.

A noise log

The question: Residents complain about noise from the loading bay at night. We need evidence: when, and how loud.

Part	Setting
Hardware	A noise sensor that reports noise_dba (Milesight H4 Pro or a LoRaWAN sound sensor), away from fans and compressors
Data table	Noise events: dba number · place zone
Rule watches	The sensor
Condition	Sensor reading (any field) noise_dba greater than 70
Between	22:00 → 07:00
Repeat at most every	5 minutes
Action	Add a row to a data table → dba = {{noise_dba}}, place = {{zone_uid}}

The report: max dba and count Records by Date and Hour. The continuous picture, every reading, is Reports → Environment and the Noise source in Custom Reports.

A sensor behaving strangely

The question: Tell me before a sensor dies, not after.

Anomaly detection watches every device on its own: a tag that went silent, sends far more or far less than usual, got weaker, or whose battery is falling faster than it should. It raises work orders itself. A rule adds a channel:

Part	Setting
Rule watches	A label (Critical sensors) or a place
Condition	Device anomaly detected equal to battery_drain (or silent, or any)
Action	Email to whoever keeps the spares

For a plain low battery, the Low battery rule template (Battery Level less than 20, checked daily) is the earlier, gentler nudge; Omaya raises the work order itself when the battery is critical.