Getting a “not alarming” fault through can feel urgent, especially when it’s flagged as a high-priority issue.
The good news is that in most cases, it is something simple. These faults are usually caused by small configuration or network issues and can often be resolved quickly without needing a full reconfiguration or return visit.
If you receive a “not alarming” notification from Farsight, run through the checks below before assuming the worst.
First Things First — Don’t Panic
These faults are important and should always be investigated, but they are rarely a major failure.
In most cases, the issue comes down to one of the following:
- A temporary network issue
- Alarm settings are being changed or removed
- SMTP or email configuration problems
- The system is not being armed correctly
Working through a simple checklist will usually get things back up and running in minutes.
Step 1: Restart the System
Start with the basics.
Reboot:
- The NVR or recorder
- Any relevant cameras
- The router or network equipment (if accessible)
A simple restart can resolve temporary glitches, dropped connections, or background service issues that stop alarms from sending.
Step 2: Check the System is Armed
It sounds obvious, but this is one of the most common causes.
Check:
- The system is fully armed
- It is in the correct mode to send alarms
- No one on-site has disabled or altered the schedule
If the system is not armed correctly, it will not generate any alarm events to send through.
Step 3: Trigger a Test Alarm With Farsight
Once the system is confirmed as armed, the next step is to test it.
Call the Farsight support team and:
- Trigger a test event (motion, alarm input, analytics, etc.)
- Ask us to confirm if it has been received
This quickly tells you where the issue sits:
- If we receive the alarm, the system is working correctly
- If we do not receive anything, continue with the checks below
Step 4: Check the Alarming Details
Next, confirm that the alarm configuration is still in place.
Check:
- The correct email or A-number is entered
- SMTP server details are present
- Username and password (if used) are correct
It is not uncommon for these settings to be removed or changed after:
- Firmware updates
- System resets
- Engineer adjustments
If these details are missing or incorrect, alarms will not be sent.
Step 5: Check if Port 25 is Being Blocked
This is one of the most common causes of “not alarming” faults.
Many internet providers now block port 25 by default, which prevents devices from sending emails.
If the system is set to use port 25:
- Try switching to port 587 instead
Port 587 is widely supported and is the recommended alternative for SMTP communication.
Step 6: Send a Test Message
Most systems allow you to send a test email or alarm message directly.
Run a test and check the result:
- If the test sends successfully, the system should now alarm correctly
- If the test fails, it points to a network or SMTP issue
At this stage, you know the problem is not with Farsight receiving alarms, but with the system sending them.
Still Not Working? Give Farsight a Call
If you have worked through the steps above and the system is still not alarming, our support team can help.
We can:
- Confirm your alarming details
- Check if anything has been received at our end
- Help troubleshoot the issue while you are on site
In many cases, it is quicker to resolve the issue live rather than making multiple visits.
Key Takeaway
Most “not alarming” faults are not major system failures. They are usually caused by small configuration or network issues that can be resolved quickly with the right checks.
Taking a few minutes to run through this checklist can save time, avoid unnecessary callouts, and get your system back online faster.
Need Help?
If you are unsure or want to run a quick test, our support team is always here to help.
📞 Give us a call when you are on site, and we will guide you through it.
