If you are not receiving Alarm.com notifications from your Qolsys system, or notifications arrive much later than expected, first determine whether the problem affects one notification type or all system activity.
These instructions apply generally to:
Alarm.com can provide different types of notifications, including push notifications, text messages, and emails depending on your account and notification settings.
Identify exactly what you expected to receive.
Examples include:
Knowing which event is missing helps determine whether the problem affects one notification rule or the entire system.
Open Alarm.com and check whether the event appears in the system history.
For example, if you armed the system but did not receive a notification, check whether Alarm.com recorded the arming event.
If the event appears in history but no notification was received, the problem may involve the notification settings or delivery method.
If the event itself is missing, there may be a communication issue.
Look for communication trouble on the Qolsys panel.
If the panel cannot communicate normally, Alarm.com may not receive events promptly.
Check for messages involving:
Contact CommTech Systems if a communication trouble remains.
If Alarm.com push notifications are missing, check your phone's notification permissions.
Make sure Alarm.com is allowed to send notifications.
Also check whether the phone has:
Exact phone settings vary by device.
If you normally receive Alarm.com notifications by text message but they have stopped:
If the settings appear correct but messages still do not arrive, contact CommTech Systems.
If Alarm.com email alerts are missing:
If the email address has changed, update your normal account information or contact CommTech Systems.
For example:
This usually indicates that system communication itself may be functioning and the issue is more specific to the affected notification method.
Check the settings for that notification type.
If push, text, and email notifications all stop at approximately the same time, check whether Alarm.com is receiving current system events.
Also check whether the Qolsys panel is reporting communication trouble.
If Alarm.com event history is also not updating, contact CommTech Systems.
If one authorized user receives notifications normally but another does not, the problem is more likely associated with the affected user's notification settings or device.
Check the affected user's:
Do not share Alarm.com passwords between users.
If every authorized user stopped receiving expected notifications at approximately the same time, check:
Contact CommTech Systems if the system is not reporting events normally.
Compare:
This helps determine where the delay may be occurring.
For example, if an event happened at 3:00 PM, Alarm.com history shows 3:00 PM, but the notification arrived at 3:20 PM, the system recorded the event on time but notification delivery was delayed.
If the event itself does not appear in Alarm.com until much later, the problem may involve system communication rather than only notification delivery.
Check the Qolsys panel for communication trouble.
If the problem began after getting a new phone:
If you recently removed and reinstalled Alarm.com, verify that notification permission is still enabled for the app.
Your phone may treat the reinstalled application as a new installation.
Phone operating-system updates can sometimes change notification behavior or permissions.
Check that Alarm.com still has permission to send notifications.
If notifications stopped around the same time as a property Internet or router change, check whether the Qolsys system also went offline.
Verify:
After a power outage, allow the Qolsys panel and network equipment time to reconnect.
Check for:
If events do not begin reporting normally again, contact CommTech Systems.
If Alarm.com records arming and disarming correctly but you do not receive alerts, check the notification rule associated with those events.
Make sure the appropriate users are included as recipients.
If you expect notifications when a particular door or window opens, first make sure the Qolsys panel correctly detects that sensor.
Open and close the door while watching the panel.
If the panel does not recognize the sensor correctly, troubleshoot the sensor rather than the notification.
An actual security alarm may involve monitoring-center procedures in addition to Alarm.com notifications.
Do not rely solely on a phone push notification as the only indication of an emergency.
Treat fire and carbon monoxide events as life-safety conditions.
If you receive a fire or CO alarm notification and there may be an actual emergency, move to a safe location and contact emergency services as appropriate.
Do not wait for additional app notifications before responding to a possible emergency.
If you receive the same event multiple times, determine whether they are actually different notification methods.
For example, the same event could generate:
This may appear to be a duplicate even though multiple delivery methods are enabled.
If you receive true duplicate alerts through the same method, contact CommTech Systems.
If you are receiving more notifications than you want, review your normal Alarm.com notification settings.
Notification preferences can often be adjusted by event type.
Be careful when disabling notifications related to important alarm or trouble conditions.
If one notification type is unwanted or malfunctioning, do not disable every system notification.
Adjust only the appropriate notification settings or contact CommTech Systems for assistance.
Do not factory reset the Qolsys panel because Alarm.com notifications are delayed or missing.
The communication or notification issue should be diagnosed directly.
Contact CommTech Systems if:
When requesting assistance, provide:
For your security, do not provide alarm codes, passwords, WiFi passwords, or other private account credentials through the support chatbot.