Push Notifications

Push notifications let a Supracontrol server alert you about important events - such as alarms - even when the app isn’t open. This page explains how your device registers to receive them and how that’s tied to each account.

Registering your device

At startup, on iOS and Android, the app asks for notification permission. If you grant it, the app registers with the platform’s push service and receives a device token - the address the server uses to reach this specific device.

Binding to a server

To receive alerts from a server, the app tells that server which device belongs to you by sending a push binding. It includes the device token plus identifying details - platform, device name, manufacturer, model, OS version, and a unique device identifier - so the server can format and route notifications correctly. Each saved account keeps its own registration.

Staying registered

Device tokens can change over time, so the app re-registers automatically when the token is new, changes, or the stored registration is more than about a week old. This keeps delivery working without you having to do anything.

Logout and cleanup

When you log out of a server, the app removes that device’s push binding from the server before clearing your session, so you stop receiving that account’s notifications on this device. See Managing accounts.

Note: Whether alarms generate push notifications depends on your Supracontrol Enterprise configuration. The app handles registration; the server decides what to send.