Limits, alerts, and notifications

An alert means turning a raw number into a state that someone must decide about. In the digital twin system, alerting is not the job of a single page; several complementary mechanisms exist, each with its own place. In this lesson you will learn to define a threshold limit with hysteresis for a continuous quantity (temperature, humidity, pressure), know exactly at what moment an alert is raised and at what value it clears, and send a notification through a channel that actually reaches the recipient in practice.

Three layers of alerting

Before anything else, be clear about which layer your alert is built in. The three layers differ in where they are defined, where and when they run, and how persistent they are:

Why hysteresis

A sensor that hovers near a threshold produces a flood of messages without hysteresis: 65.1 alert, 64.9 clear, 65.2 alert again. Hysteresis creates a return band: entry into the alert band happens on reaching the threshold, but exit only happens once the value crosses the threshold by the amount of the hysteresis.

Each limit can have up to four levels: lowLow, low, high, and highHigh. You don't need to fill in all four levels, but whichever levels you do write must be in ascending order.

Get to know the page

A threshold limit with hysteresis has no dedicated page; creating, listing, editing, and deleting it are all done through the smart assistant. The display and sending channels are project settings on the تنظیمات اعلان (Notification Settings) tab:

At the top of this same page, the فقط محلی (Local Only) label and the text "System configuration saved in the browser" are shown: this tab keeps this specific browser's preferences. The system administrator configures the account and key for the server-side channels; if a test message doesn't go through, check this with them first.

Step by step

1. Open the assistant. On any page in the system, the floating star button at the bottom of the page opens the دستیار هوشمند ARG (ARG (ARG Smart Assistant)) panel. This panel is the only UI path for creating, viewing, and deleting a threshold limit with hysteresis.

   

2. Write the request with five elements. The point's name, the level (high/low), the threshold value, the hysteresis, the channel, and the recipient. Example: "Set a high limit of 65 and hysteresis of 5 for the server room's humidity, and notify me by SMS at the number …". If you don't specify message text, the assistant builds a default text like ""Server Room Humidity" is high: {self} (limit 65)", and for the return it sends a message like ""Server Room Humidity" returned to normal range: {self}".
3. Read the confirmation card and confirm it. Before writing anything, the assistant shows a confirmation card summarizing the limit (point, levels, hysteresis, channel, and recipient). Nothing is saved until you confirm. Compare the summary against what you had in mind, especially the unit and the decimal placement.
4. List the limits. Ask the assistant to list the project's defined limits. This is the only way to fully review the server's limits, and it prevents duplicate work and conflicting limits before defining a new one. Deletion is also done through this same path.
5. Configure the display channel. Go to «تنظیمات» ← «تنظیمات پروژه» ← «تنظیمات اعلان» and, in the تنظیمات نمایش نوتیفیکیشن (Notification Display Settings) card, set whether it's enabled, the sound, the display duration, and the display position.

   

6. Test an external channel. On the Telegram, SMS, or SMPP card, turn on the enabled toggle, fill in the fields, and click تست ارسال (Telegram) or تست اتصال (SMPP). A success message ("Telegram test succeeded!", "SMPP connection established successfully!") or an error is shown right away. Finally, click ذخیره تغییرات (Save Changes).

   

Tips and common mistakes

• The levels must be in ascending order; otherwise it is not saved, and you see the message "Limits must be ascending: lowLow < low < high < highHigh."
• Hysteresis does not accept a negative number ("hysteresis cannot be negative."), and a hysteresis of zero means the same noisy behavior as before.
• Every channel needs its own recipient: SMS without a number, email without an address, and Telegram without a chat ID are not saved.
• The allowed number format: with + and 8 to 15 digits, or with 0 and 10 digits after it. Otherwise the message "The number … is not valid." appears.
• In a limit's message text, the placeholder for the instantaneous value is {self} (with curly braces).
• Recipient groups, message templates, and an escalation policy have no UI page in the current version; write the recipient directly in the limit definition or in the rule's notification action.
• The Telegram and SMS checkboxes on the "Web Notifications" card of the point-definition form do not send an external message; external sending is the job of the threshold limit and the rule's notification action.
• The "Notification Settings" tab, labeled "Local Only", is stored in the browser; it must be set up again on another browser or device.

Summary

• Persistent alerting on a continuous quantity = a threshold limit with hysteresis, built with the assistant and run on the server.
• Entry into a band happens at the threshold, exit at "threshold ± hysteresis"; notification fires only at the moment of a band change.
• Levels must be ascending, and every channel needs a valid recipient.
• The point form's "Limits and Alerts" step is not evaluated in the current version; do not rely on it as an alerting mechanism.
• The "Notification Settings" tab configures display behavior in this same browser; the system administrator configures the server-side channels.