Alarms & Messaging
Alarm rules on tags, communication loss and forecasts; then who is told and how — gateways, contacts, escalation lists, acknowledgement by reply — with Telegram set up step by step.
Two parts work together. Alarm rules decide when something is wrong; they live on the equipment. Messaging decides who is told and how, and keeps telling the next person until someone acknowledges. The alarm service checks the rules every few seconds, whether or not anyone has the platform open.
Alarm rules on a tag
In Equipment → Monitoring & Alarms → Tag alarms, each mapped tag can carry several rules. Each rule has:
- Name and severity — Critical, Warning or Info, shown wherever the alarm appears; and an alarm category.
- Value type — Numeric (compare with a threshold), Digital (a rising 0→1 or falling 1→0 edge) or Totaliser (the amount over a period).
- Condition — an operator (
<,<=,=,>,>=,!=) and a threshold. - Hysteresis — once raised, the alarm stays raised until the value is back past the threshold by this margin, so a noisy signal sitting on the limit does not flap.
- Delay (optional, numeric rules, live sources) — the condition must hold this long before the alarm is raised, for example a value at 0 for more than 10 minutes. Up to 7 days.
The delay is offered only for equipment read live (Modbus TCP, OPC UA, IEC 104, MQTT). A datalogger delivers its readings in batches, often hours later; a condition that started and ended inside one file would be invisible to a check that waits for it to hold. On file-based equipment, use a plain threshold, with hysteresis if it chatters — every crossing inside a delivered file still raises its alarm, stamped with the time of the reading.
A new or changed rule applies to values received after the change.
Other kinds of alarm
- Communication lost. Each equipment has a communication timeout (days, hours, minutes). With the communication-lost alarm on, a silent device raises an alarm that clears by itself when data comes back. The same timeout greys the device in the asset tree and on the map.
- Operating curves. A curve rule watches the relationship between two tags — a pump’s flow against its pressure — and alarms when the point leaves a tolerance band around the expected curve: an early sign of wear or fouling. A curve can be a template shared by many identical pumps.
- Site KPIs. A site-level virtual tag with a target and a tolerance can raise an alarm when it leaves its band.
- Forecast alarms (Forecasting module). A rule on the forecast fires when the forecast crosses a threshold within a window ahead — before the measured value gets there. It carries when the crossing is predicted and the predicted peak, and lives in the same alarm list, acknowledgement and Messaging as every other alarm.
Acknowledging
Acknowledging tells the system — and your colleagues — that someone is on it, and it stops the escalation. It does not clear the alarm: an alarm stays active until the value is back to normal.
- In the platform: per alarm, per device (Ack all on the device), or everything (Ack all at the top of the asset tree), and from the Dashboard’s alarm list.
- By replying on Telegram:
ack,ok,sim,confirmo, ✅ or 👍 in the chat the alert was sent to, or a reply to the alert message itself. - By replying to an alert from the SMS gateway with the code in the message (
ACK-…).
Messaging: the pieces
Everything is in the Messaging Center.
Gateways (Configuration tab)
The channels SyncTide sends through. Add one with Add gateway, mark it active (and optionally the default), save, and use Test send to check it.
| Gateway | Channel | What it needs |
|---|---|---|
| SMTP | Host, port, TLS, user name, password, sender address | |
| Telegram Bot | Telegram | The bot token from @BotFather |
| Twilio or Meta WhatsApp | The account’s credentials and sender number | |
| Teltonika RUT router | SMS gateway | The router’s address, user name, password and modem |
| Generic HTTP | Your own gateway | URL, method, headers and a body template |
For Gmail, use an app password (Google Account → Security → 2-Step Verification → App passwords) with smtp.gmail.com, port 587 and TLS — not the account password. Scheduled reports are emailed through the SMTP gateway too.
Contacts
The people who are told: a name, a phone number, an email address and a Telegram chat ID, and an active switch — inactive contacts are skipped.
Escalation lists
The order in which contacts are told. Each member has a priority and a delay: members are told in priority order, each after their delay, until someone acknowledges. A list can escalate to another list (another team) when nobody on it answers — for example a night-shift list that escalates to the supervisors.
Alarm rules (Messaging)
A messaging rule links alarms to an escalation list:
| Setting | What it does |
|---|---|
| Scope | One device and tag, a whole alarm category, or a site KPI |
| Escalation list | Who is told, in which order |
| Channel type | Force one channel, or Any to use each contact’s |
| Cooldown (min) | The least time between two messages for the same alarm |
| Max escalations | How many steps to go through before stopping |
| Require acknowledgement / Ack timeout (s) | Wait this long for an acknowledgement before moving on (300 s by default) |
| Message template | The text, with $device_name, $tag_name, $value, $unit, $operator, $threshold, $timestamp |
Forecast alarms can also use $predicted_for, $lead_time, $predicted_peak and $confidence.
The History tab lists every message with its status — pending, sent, delivered, failed, acknowledged — and messages that fail to send are retried.
Telegram, step by step
Telegram costs nothing per message and needs no SIM card.
- Create the bot (once). In Telegram, open @BotFather, send
/newbot, choose a display name and a user name ending inbot. Copy the token it gives you (1234567890:ABC…) — treat it as a password. - Each recipient installs Telegram, finds their chat ID (for example with
@userinfobot), opens your bot and taps Start — a bot cannot write to someone who never started it. The guide for recipients walks them through it. - Add the gateway: Messaging Center → Configuration → Add gateway, type Telegram Bot, paste the token, keep the parse mode HTML, active.
- Add a contact per recipient with their chat ID.
- Link them in an escalation list and a messaging rule, then send a test message.
For a shared on-call group: add the bot to the group, send a message there, open https://api.telegram.org/bot<TOKEN>/getUpdates and copy the group’s chat ID — group IDs are negative, keep the minus sign.
| Telegram error | Cause | Fix |
|---|---|---|
Forbidden: bot can't initiate conversation with a user |
The recipient never started the bot | They open the bot and tap Start |
Bad Request: chat not found |
Wrong chat ID, or a person’s ID used for a group | Check the ID with the recipient |
Unauthorized |
Wrong bot token | Copy it again from @BotFather (/mybots → API Token) |
Bad Request: can't parse entities |
The message template breaks the HTML parse mode | Remove the offending characters from the template |
The full administrator guide is in the Telegram setup download.