Most OGLAS sensors report a number. A camera reports a scene — and once you can process that scene on site, it becomes another sensor in the same pipeline: Video → Hubs → Local → Cloud, with the footage staying yours.
This is its own area because video has its own demands — power, storage, processing, and privacy — that set it apart from a battery node reading a voltage.
What it does
- Motion sensing — tell the difference between “something moved” and “the wind moved a branch”, and raise an alert only when it matters.
- Marked-area monitoring — draw the zones that count (a gateway, a trap line, a shed door, a tank stand) and watch only those, ignoring the rest of the frame.
- Animal-type detection — on-site recognition of what it’s looking at: a fox, a rabbit, a deer, stock, a person, a vehicle. A pest crossing a boundary is a different event from a sheep doing the same.
- Trigger the rest of the system — a detection can ring a bell, open or lock a gate, or deter pests via a Smart Switch.
Processed on site, footage stays yours
The recognition runs on the hub at the edge, not in someone’s cloud. What leaves the camera is an event — “fox at the trap line, 02:14” — not a stream of your property. Keep the full footage local, and send only the events (and the clips you choose) to the optional Cloud. This is Your data is your data applied to the camera.
Off-grid realities
Video asks more of a site than a sleepy sensor node — more power, more storage, more compute. We size it for the site: solar-and-battery where it has to be, mains where it can be, on-site storage tiered so the clips that matter are kept and the rest rolls over.
Cameras and detection are almost always a custom build — the species, the zones, and the triggers are specific to your site. Tell us what you need to see.