Monitoring and alerts

Sensors are only useful if someone notices the readings. OGLAS does both halves: a live picture of what’s happening right now, and an audible nudge when something needs your attention.

Real-time monitoring

The hub confirms every sensor message as it comes in, so you can see at a glance which sensors are healthy and which ones haven’t checked in.

• Large display — a wall-mount dashboard that pages through every sensor on your network.
• Small display — a desktop unit showing your two most important sensors at a glance.
• Local dashboard — if you’d rather use a phone or laptop, Local exposes a full web UI on your own network.

All three read from the same on-device log. Nothing leaves your site.

Alerts you’ll actually hear

The OGLAS bell is the sharp end of the alert system. It rings when:

• A gate opens — the bell pattern-matches gate activity and rings immediately. Rate-limited, so a flaky link can’t replay the same event into a buzz-storm.
• A direct command is sent — a ring or alarm instruction from the hub, a script, or another OGLAS device.
• A threshold is crossed — tank low, battery flat, or any other rule you’ve configured on the hub.

A single command can ring every bell on site at once, so the homestead bell and the shed bell go off together.

Missed-checkin

The hub tracks the last time it heard from each sensor. If a node goes silent — flat battery, dead radio, knocked off its mount — it gets flagged. No “everything’s fine” right up until the day it isn’t.

Off-site alerts (optional)

If you want a phone notification rather than just a buzzer in the kitchen, that’s a configuration on the hub plus the optional Cloud half — not a precondition. See No telco dependency for the philosophy: the system works without internet, and you choose what (if anything) to push beyond your site.