Mobile Application

The Supracontrol Mobile Application is the companion app to Supracontrol Enterprise. It puts live camera feeds, sensor readings, active alarms, and event history on a phone or tablet, so an operator away from the control room can see what is happening on a site and act on it.

The app connects to one or more Supracontrol servers - each typically a customer site. A single device can hold several accounts across different servers and switch between them in a tap, without logging out.

[IMG — The app on a phone showing the Locations dashboard with the bottom tab bar]

What the app is for

The web platform is where a deployment is configured; the app is where it is watched and answered. It deliberately covers the things that matter when you are not at a desk: confirming an alarm is real, checking a camera, operating a door, and pulling up the recording of what just happened.

Configuration stays in Supracontrol Enterprise. The location hierarchy, users and roles, notification rules, and automation are all defined there, and the app reflects them - including your access rights, which decide what you are allowed to operate rather than just view.

The five tabs

The bottom tab bar is the app’s spine. Each tab is one of the five things you do most:

TabWhat you do there
LocationsBrowse the site as a tree of locations - building, floor, room - and drill into the cameras and sensors in each
FavouritesKeep the sensors you check often one tap away
VideoWatch live camera feeds in an adaptive, paged grid
AlarmsSee only the sensors currently in alarm, with a live count badge on the tab itself
EventsReview a timeline of alarms, access activity, and sensor events, and play back the video attached to them

Everything else - account switching, the Device List, Settings, What’s New, and About - lives in the side menu. See App layout for the full map.

What the app gives you

Live video that recovers by itself

Mobile networks drop. The app is built for it: streams retry with increasing back-off delays instead of hammering the server, a stalled feed is detected and re-established, and brief network flaps are ignored. Grid tiles use a standard-definition stream to save bandwidth and switch to high-definition when you open a camera fullscreen, where you can pinch to zoom and pan.

Sensors presented by type

Sensors fall into two families, and the app renders each accordingly - a value plus a historical chart for analog types like temperature, humidity, air quality, tilt, and electrical metering; a state plus controls for digital ones like inputs, outputs, locks, doors, smoke, and flood. Several types get purpose-built detail views: grouped CO₂ and TVOC readings for air quality, per-axis values for tilt, reader position for card readers. See Sensors overview.

Doors you can actually open

Access-control hardware is modelled as a door assembly - a parent door grouping its locks, readers, presence sensors, and buttons. You can operate a lock from its detail view where your rights allow it, and the app is careful about alarm state: a door counts as in alarm only when a meaningful child is, so buttons and presence sensors do not create noise.

One device, several sites

Saved accounts live side by side in the side menu. Switching is instant while a session is still valid, and the app rebuilds every page for the new account’s data. Logins can be protected with a one-time password, and the app itself with a biometric screen lock that guards it on resume without signing you out.

Alerts that arrive when the app is closed

Push notifications are bound per account: each saved server gets its own device registration, re-registered automatically when the token changes, and removed on logout so you stop receiving that site’s alerts on that device.

Note: The app handles registration; your Supracontrol Enterprise configuration decides which alarms actually generate a notification.

The hardware inventory

The Device List is the equipment view rather than the alarm view. It presents the same site in four modes - Devices, Bus devices, Peripherals, and Cameras - each with live status, its own filters, and a displayed-versus-total count.

Behaviour that respects the battery

The app stops polling and pauses video when you background it, and resumes when you return. When the device goes offline it says so plainly instead of showing stale data, and picks up on its own once connectivity is back. See App lifecycle & offline behaviour.

Filters that follow context

Every list page shares one filter and search toolbar. Filter values are built from the data actually present, so you never see an option that matches nothing - and when you drill into a page scoped to one location or sensor, the irrelevant filters disappear and the relevant one is already applied.

How the pieces fit together

PieceRole
Supracontrol serverCollects device data, evaluates rules, stores events and recordings, and sends push notifications. The app is a client of one or more of these
The appPresents that data live and lets you act on it - operating locks and outputs, reviewing what happened, downloading evidence
Your accountDecides what you can open and what you may operate. Your favourites, language, and unit preference are stored against it on the server, so they follow you to any device

For the platform this app connects to, see Supracontrol Enterprise. For the controllers and sensors it reports on, see Devices.

Good to know

Where to start

Use the sidebar to jump into any area of the app.