Ajax Doorbell Constant Notifications — How to Stop the Spam Alerts (Complete Fix Guide 2026)
Your Ajax Doorbell is sending 300–400 notifications a day and you’re ready to uninstall it. You’re not alone — this is one of the most-discussed issues in the Ajax installer community. This complete guide covers every cause and every fix, from motion sensitivity settings to detection zone masking to firmware updates. If you’d rather have a Sipko Security technician fix it on-site, call us on 0406 432 691.
🔔 Quick Diagnosis: Match Your Notification Type
Doorbell fires motion alerts constantly — cars, trees, shadows, everything?
Every vehicle on the street triggers a notification?
Constant “doorbell disconnected” then “doorbell connected” notifications?
Repeated “high temperature” alerts even in mild weather?
AI keeps detecting animals, shadows, or moving objects as humans?
Same event generating multiple notifications to the same phone?
1. Why the Ajax Doorbell Spams Notifications — The Root Causes
The Ajax Doorbell is a capable device — but out of the box, its default settings are configured for maximum sensitivity rather than maximum usability. This means it will detect and alert on virtually everything that moves within its field of view: cars, pedestrians, cyclists, animals, blowing leaves, and shadows. For a doorbell mounted on a busy street-facing position, this can generate hundreds of notifications per day.
The good news: every one of these causes is fixable through settings adjustments, and most can be resolved in under 15 minutes without any hardware changes. The bad news: the fixes are not obvious from the app interface, and many installers and homeowners never find them. This guide walks through every cause and every fix in order of impact.
Why Your Doorbell Won’t Stop Alerting
- Motion sensitivity set to maximum — the default setting detects everything
- Detection zone covers the street — every passing car triggers an alert
- AI human detection sensitivity too high — animals and shadows classified as humans
- No cooldown period between alerts — continuous motion generates continuous notifications
- WiFi instability — disconnect/reconnect cycle generates its own notification spam
- Doorbell facing direct sunlight — thermal changes trigger motion detection
- Outdated firmware — older firmware has less refined detection filtering
Every Fix, In Order
- Motion sensitivity reduction — the fastest fix
- Detection zone masking — the most effective fix
- AI human detection settings
- Notification cooldown / alert frequency settings
- WiFi stability and power supply fixes
- Sun exposure and temperature warning fixes
- Firmware updates
- App notification management
- Advanced: scheduling quiet hours
- When to call a professional
⚠️ Don’t Just Turn Off All Notifications
The temptation when facing notification spam is to disable all doorbell notifications entirely. Resist this. The doorbell’s notification system is its primary security function — disabling it entirely means you won’t know when someone actually rings the bell or approaches your door. The goal is to reduce false notifications while keeping genuine alerts. Every fix in this guide is designed to achieve exactly that.
2. Fix #1 — Reduce Motion Sensitivity (Do This First)
Motion sensitivity is the single most impactful setting for reducing Ajax Doorbell notification spam. The default sensitivity is set high — which means the doorbell detects and alerts on virtually any movement in its field of view. Reducing sensitivity is the fastest fix and should be the first thing you try.
The Ajax Doorbell uses a combination of pixel-change detection and AI object classification to identify motion events. High sensitivity means even small pixel changes — a shadow moving, a leaf blowing, a car passing at the edge of frame — trigger the detection pipeline. Reducing sensitivity raises the threshold for what counts as a motion event, filtering out minor changes while still catching significant movement like a person approaching the door. This is similar to how you’d configure any Ajax security system for optimal performance.
How to Reduce Motion Sensitivity — Step by Step
- Open the Ajax app → tap your Hub → tap the Doorbell
- Tap the gear icon (Settings)
- Navigate to Motion Detection or Detection Settings
- Find Motion Sensitivity — it is likely set to High or Maximum
- Reduce to Medium as a starting point
- Save the settings and monitor for 24 hours
- If notifications are still excessive, reduce to Low
- If notifications stop entirely (including genuine ones), increase back to Medium-Low
What You Get
Detects everything — cars, pedestrians, animals, shadows, leaves, insects near the lens. Generates 100–400+ notifications per day in a typical street-facing installation. Appropriate only for very low-traffic locations where any movement is significant.
The Starting Point
Detects significant movement — people approaching, vehicles stopping, large animals. Filters out minor background movement like distant traffic and blowing vegetation. Appropriate for most residential installations. Start here.
For Busy Locations
Detects only close, significant movement — a person within 3–4m of the doorbell. Filters out most background traffic and distant movement. Appropriate for doorbells facing busy streets or high-traffic areas. May miss some genuine approach events at distance.
💡 The 24-Hour Test
After changing sensitivity, wait 24 hours before adjusting further. Notification patterns vary significantly by time of day — a setting that seems perfect in the morning may generate too many alerts in the afternoon when traffic increases. Give each sensitivity level a full day before deciding whether to adjust further. Keep a note of how many notifications you receive at each setting to find your optimal level.
3. Fix #2 — Detection Zone Masking (Most Effective Fix)
Detection zone masking is the most powerful tool for eliminating Ajax Doorbell notification spam — and it is the fix that most users never find. The detection zone editor in the Ajax app lets you draw a polygon that defines exactly which part of the camera’s field of view triggers motion detection. Anything outside that polygon is completely ignored.
For a doorbell facing a street, the default full-frame detection zone means every car, cyclist, and pedestrian on the street triggers an alert. By masking out the street and focusing the detection zone on the path leading to your door, you can reduce notifications by 80–90% while still catching everyone who actually approaches your property. At Sipko Security, detection zone configuration is the first thing we do on every Ajax doorbell installation — it takes 3 minutes and eliminates the majority of false alerts before the client even uses the system.
How to Configure the Detection Zone
- Open the Ajax app → tap your Hub → tap the Doorbell → tap Settings
- Tap Detection Zone — you’ll see a live or recent frame from the doorbell camera
- The default zone covers the entire frame — this is why you’re getting spam
- Drag the zone boundary inward to exclude the street, footpath, and any public areas
- Focus the zone on the path leading directly to your door — typically a 2–4m wide corridor from the gate or footpath to the door
- Exclude the sides of the frame where passing traffic appears
- Save the zone
- Test immediately: walk through the zone yourself to confirm you still trigger a detection. If you don’t, expand the zone slightly.
- Monitor for 24 hours and refine further if needed
Why You’re Getting Spam
The entire camera frame is active. Every car on the street, every pedestrian on the footpath, every cyclist passing by triggers a notification. This is the default setting and the primary cause of notification spam for street-facing doorbells.
What You Want
Only the path leading to your door is active. Street traffic is excluded. Notifications fire only when someone actually approaches your property. This is the correct configuration for virtually every residential doorbell installation.
⚠️ Don’t Make the Zone Too Small
The most common mistake when configuring the detection zone is making it too small in an attempt to eliminate all false alerts. A zone that is too small will miss genuine visitors — someone approaching from the side, a delivery driver walking up the path, or a visitor who approaches from an unexpected angle. The goal is to exclude public areas (street, footpath) while keeping the full approach path to your door within the zone. Always test by walking through the zone yourself after configuring it.
4. Fix #3 — AI Human Detection Settings
The Ajax Doorbell includes AI-powered human detection — it attempts to classify detected motion as human or non-human and can be configured to only notify you when a human is detected. When working correctly, this dramatically reduces false notifications from cars, animals, and environmental movement. When misconfigured, it can either generate too many false positives (animals classified as humans) or miss genuine visitors.
If you are receiving constant notifications for non-human movement — cars, animals, blowing vegetation — enabling or tuning the AI human detection filter is the fix. If you are receiving constant false human detections (animals or shadows classified as humans), reducing the AI sensitivity is the fix. These are different problems with different solutions.
Enable Human Detection Filter
If you’re getting alerts for cars, animals, and general movement — not just humans — enable the human detection filter to restrict notifications to human-only events.
Path: Settings → Detection Settings → Object Detection → Enable Human Detection → set to “Humans Only” for notifications
Reduce AI Sensitivity
If the AI is classifying animals, shadows, or vehicles as humans — generating constant false human detection alerts — reduce the human detection sensitivity from High to Medium.
Path: Settings → Object Detection → Human Detection Sensitivity → change from High to Medium
The Report Button — Use It Every Time
Every time the Ajax Doorbell generates a false human detection, tap Report on the notification clip and select “Not a human.” This submits the clip to Ajax’s AI training pipeline and directly improves the model’s accuracy over time. Consistent reporting from multiple users accelerates the fix. See our detailed guide on fixing Ajax AI false human detections for the full picture — the same principles apply to the doorbell as to the TurretCam.
✅ The Recommended Configuration
For most residential doorbell installations: enable human detection filter (notifications for humans only), set sensitivity to Medium, and configure the detection zone to exclude the street. This combination eliminates the vast majority of notification spam while ensuring you are alerted when a real person approaches your door. If you still receive excessive notifications after this configuration, the next step is the notification cooldown setting covered in the next section.
5. Fix #4 — Notification Cooldown and Alert Frequency
Even with correct sensitivity and detection zone settings, a busy doorbell location can generate multiple notifications for a single event — a person walking slowly up the path, for example, may trigger 3–4 motion detections as they move through the detection zone. The notification cooldown setting controls how long the doorbell waits after sending a notification before it can send another one for the same type of event.
This is one of the most underused settings in the Ajax Doorbell configuration. A cooldown of 30–60 seconds means that even if the doorbell detects continuous motion, it will only send one notification per minute rather than one every few seconds. For most residential installations, a 30-second cooldown is the right balance between responsiveness and spam prevention.
How to Set the Notification Cooldown
- Open the Ajax app → tap your Hub → tap the Doorbell → tap Settings
- Navigate to Notification Settings or Alert Settings
- Find Alert Delay, Notification Cooldown, or Re-trigger Delay
- Set to 30 seconds as a starting point for residential installations
- For very busy locations (facing a main road), increase to 60 seconds
- For low-traffic locations where every event matters, keep at 10–15 seconds
- Save and monitor for 24 hours
The Spam Problem
Every motion event generates a notification immediately. A person walking slowly up the path generates 4–6 notifications. A cat sitting in the detection zone generates continuous notifications until it moves. This is the default behaviour and a major contributor to notification spam.
The Recommended Setting
One notification per 30 seconds maximum. A person walking up the path generates 1–2 notifications. A cat in the zone generates one notification then silence until it moves significantly. Dramatically reduces spam while maintaining responsiveness to genuine events.
💡 Combining All Four Fixes
The most effective approach combines all four fixes covered so far: (1) reduce motion sensitivity to Medium, (2) configure detection zone to exclude the street, (3) enable human detection filter at Medium sensitivity, and (4) set a 30-second notification cooldown. Applied together, these four changes typically reduce notification volume by 90–95% for a typical street-facing residential doorbell — from hundreds of alerts per day to a handful of genuine ones. If you’re still getting excessive notifications after applying all four, the remaining causes are covered in the sections that follow.
6. Fix #5 — WiFi Stability and the Disconnect/Reconnect Spam
A distinct category of Ajax Doorbell notification spam is the disconnect/reconnect cycle — the doorbell repeatedly drops its WiFi connection and reconnects, generating a “doorbell disconnected” notification followed immediately by a “doorbell connected” notification. This can happen dozens of times per day and has nothing to do with motion detection settings.
The Ajax Doorbell connects via WiFi (not the Jeweller protocol used by other Ajax wireless alarm devices). This means its reliability is entirely dependent on the quality and stability of your WiFi signal at the doorbell’s mounting location. A doorbell mounted near the front door — often the furthest point from the router — is frequently at the edge of the WiFi coverage area, making it susceptible to signal drops.
Why the Doorbell Keeps Dropping
- Weak signal at mounting location — doorbell is too far from the router or access point
- 2.4GHz vs 5GHz band issues — the doorbell uses 2.4GHz; if your router prioritises 5GHz, the doorbell may struggle
- Router channel congestion — too many devices on the same WiFi channel causing interference
- Router firmware issues — outdated router firmware can cause intermittent disconnections
- Power supply instability — insufficient power to the doorbell causing it to reset
- Thick walls or metal obstacles — between the router and doorbell mounting location
How to Stop the Disconnect Spam
- Add a WiFi access point or mesh node near the front door — the most reliable fix for weak signal
- Check signal strength in the Ajax app — Settings → Doorbell → Signal. Aim for 3+ bars
- Switch to 2.4GHz band — ensure the doorbell is connecting to 2.4GHz, not 5GHz
- Change WiFi channel — use a WiFi analyser app to find a less congested channel
- Check power supply — ensure the doorbell is receiving the correct voltage (12–24V DC)
- Update router firmware — check your router manufacturer’s site for updates
💡 The Ajax Doorbell’s 500m WiFi Range Claim
Ajax claims up to 500m WiFi range for the doorbell — but this is in open-air conditions with no obstacles. In a typical Melbourne home with brick walls, the effective range is 15–30m. If your router is at the back of the house and the doorbell is at the front, you may be at or beyond the effective range. A WiFi mesh system or a dedicated access point near the front door is the professional solution. See our guide on smart home security integration for network planning advice.
7. Fix #6 — Sun Exposure and Temperature Warning Spam
The Ajax Doorbell generates “high temperature” warnings when its internal temperature exceeds a threshold — typically around 50°C. In Melbourne’s climate, a black doorbell mounted in direct afternoon sun can easily reach this temperature even when the ambient air temperature is only 20–25°C. The result is repeated temperature warning notifications that have nothing to do with security events.
This is a hardware placement issue rather than a settings issue — the fix requires either relocating the doorbell to a shaded position or adding a sun shield. The temperature warning cannot be disabled in the app, as it is a safety feature designed to alert you to potential hardware damage.
The Sun Exposure Problem
The Ajax Doorbell’s black housing absorbs solar radiation efficiently. In direct afternoon sun, the housing temperature can reach 50–60°C even when the air temperature is mild. The doorbell’s internal temperature sensor detects this and generates a warning notification.
This is most common on west-facing doorbells in Melbourne’s afternoon sun, and on doorbells mounted on dark-coloured walls that reflect heat onto the device.
How to Stop Temperature Warnings
- Add a sun shield or visor — a small overhang above the doorbell blocks direct sun while maintaining the camera’s field of view
- Relocate to a shaded position — if possible, move the doorbell to a position that receives less direct sun
- Use a white doorbell housing — white reflects more solar radiation than black; if you have a black unit in a sunny location, consider swapping to white
- Check the power supply voltage — insufficient power can cause the doorbell to run hot; ensure you are supplying the correct voltage
💡 Melbourne-Specific: West-Facing Doorbells
West-facing doorbells in Melbourne receive intense afternoon sun from approximately 2pm to sunset, particularly in summer. Properties in Brighton, Hampton, and other bayside suburbs with west-facing frontages are particularly affected. If your doorbell faces west and generates temperature warnings in summer, a sun shield is the most practical fix. A simple 3D-printed or commercially available doorbell visor costs under $20 and eliminates the problem entirely.
8. Fix #7 — Firmware Updates and Detection Improvements
Ajax ships detection algorithm improvements and notification filtering enhancements in doorbell firmware updates. Running outdated firmware means running an older, less refined detection pipeline that may generate more false positives than the current version. Updating firmware is one of the easiest fixes and should be done before making any settings changes — the issue may already be resolved in the latest version.
The Ajax Doorbell firmware is separate from the Hub firmware — both need to be updated. Hub OS (Malevich) updates can also affect how doorbell events are processed and filtered at the system level. Always update both together.
How to Update Ajax Doorbell Firmware
- Open the Ajax app → go to Devices → tap the Doorbell → tap the gear icon
- Scroll to Firmware — the current version is displayed. If an update is available, an “Update” button appears
- Tap Update — keep the doorbell powered throughout. The update takes approximately 5–10 minutes
- The doorbell will reboot automatically after the update completes
- Also update your Hub firmware — go to Hub → Settings → Firmware
- After updating both, re-test your notification settings — some settings may reset to defaults after a firmware update
- Check the Ajax release notes for mentions of “detection improvements” or “false positive reduction” — these confirm the update addresses your specific issue
Detection Improvements
- Improved AI human/non-human classification
- Better motion filtering for environmental movement
- Reduced false positive rate for animals and vehicles
- Improved notification cooldown logic
- Better WiFi reconnection handling
- Reduced disconnect/reconnect notification frequency
Hardware Limitations
- Weak WiFi signal at the mounting location
- Detection zone covering the street (must be configured manually)
- Sun exposure causing temperature warnings
- Insufficient power supply voltage
- Physical placement issues (facing busy road, etc.)
9. Fix #8 — App Notification Management and Per-User Settings
Beyond the doorbell’s own settings, the Ajax app provides per-user notification controls that allow you to customise which events generate notifications for each user. This is particularly useful in households where different family members have different notification preferences — one person may want all motion alerts while another only wants to know when the bell is actually pressed.
The Ajax app also allows you to configure notification types separately — push notifications, SMS, and phone calls can each be enabled or disabled independently for different event types. If you are receiving duplicate notifications (the same event generating multiple alerts), this is almost always a per-user notification configuration issue.
Per-User Notification Configuration
- Open the Ajax app → tap your Hub → tap Users
- Select the user whose notifications you want to configure
- Tap Notification Settings or Alert Settings
- For each event type (motion detected, doorbell pressed, human detected), choose: Push notification, SMS, Phone call, or None
- To reduce spam: disable motion detection notifications for secondary users; keep doorbell press notifications enabled for all users
- For the primary user: keep human detection notifications enabled; disable general motion notifications if human detection is configured
- Save settings for each user separately
What to Enable
- ✅ Doorbell pressed — always
- ✅ Human detected — if AI detection is configured
- ✅ System malfunctions — always
- ⚠️ Motion detected — only if human detection is not configured
- ❌ General motion — disable if human detection is active
Minimal Notification Profile
- ✅ Doorbell pressed — always
- ❌ Motion detected — disable
- ❌ Human detected — disable (primary user handles this)
- ✅ System malfunctions — optional
- ❌ Temperature warnings — disable for secondary users
💡 Critical Alerts on iPhone
iPhone users may experience Ajax notifications bypassing Do Not Disturb mode — this is because Ajax uses Apple’s “Critical Alerts” feature for alarm events. If you are receiving doorbell notifications at night despite having Do Not Disturb enabled, check your iPhone Settings → Notifications → Ajax → Critical Alerts. You can disable Critical Alerts for the Ajax app without affecting regular notifications. Note: this will also disable critical alarm notifications — only do this if the notification spam is severe enough to justify the trade-off.
10. Fix #9 — Scheduling Quiet Hours and Time-Based Automation
If your Ajax Doorbell notification spam is concentrated at specific times — morning rush hour, school pickup time, or late at night when any movement triggers an alert — time-based automation rules can significantly reduce the problem. Ajax’s scenario and automation system allows you to create rules that modify doorbell behaviour based on time of day, day of week, or system arm state.
This is an advanced fix that requires some familiarity with the Ajax automation system, but it is extremely powerful for managing notification patterns that vary by time. For example: reduce motion sensitivity automatically during peak traffic hours, or disable motion notifications entirely between midnight and 6am while keeping doorbell press notifications active.
Setting Up Time-Based Notification Rules
- Open the Ajax app → tap your Hub → tap Automation (or Scenarios)
- Tap Add Scenario or Create Rule
- Set the trigger to a time condition — e.g., “Every day at 7:00am” and “Every day at 9:00am”
- Set the action to modify doorbell sensitivity or notification settings
- Create a second rule to reverse the change at the end of the quiet period
- Test the rules by checking the doorbell behaviour at the scheduled times
Practical Automation Examples
- School run hours (7:30–9am, 3–4pm): reduce sensitivity to Low during peak pedestrian traffic
- Night hours (11pm–6am): disable motion notifications; keep doorbell press active
- Work hours (9am–5pm weekdays): enable full notifications when property is unoccupied
- When system is armed: enable all notifications; when disarmed, reduce to doorbell press only
Linking to Your Alarm State
The most elegant solution for many households: link doorbell notification intensity to the alarm arm state. When the system is armed (no one home), enable full motion notifications. When the system is disarmed (someone home), reduce to doorbell press only — you don’t need motion alerts when you’re already home.
This requires the Ajax alarm system to be installed alongside the doorbell. See our guide on setting up a complete Ajax alarm system for the full configuration.
11. Fix #10 — Power Supply Issues Causing Erratic Notifications
An underpowered Ajax Doorbell is one of the less obvious causes of notification spam. When the doorbell receives insufficient voltage, it can behave erratically — generating spurious motion detections, disconnecting and reconnecting repeatedly, or sending notifications for events that didn’t actually occur. This is particularly common when the doorbell is wired to an existing doorbell transformer that was designed for a simple chime, not a smart doorbell with a camera and WiFi radio.
The Ajax Doorbell requires 12–24V DC at a minimum of 1A (ideally 2A for reliable operation). Many existing doorbell transformers supply only 8–12V AC at low current — insufficient for the Ajax Doorbell’s power requirements. If you are experiencing erratic behaviour that doesn’t respond to settings changes, check the power supply first.
What Underpowering Looks Like
- Frequent disconnect/reconnect notifications with no WiFi issues
- Doorbell reboots randomly — you see it go offline and come back
- Erratic motion detections that don’t correspond to actual movement
- Poor video quality or frequent buffering in live view
- Doorbell works fine in cool weather but struggles in summer heat
- Notifications stop entirely for periods then resume
How to Ensure Adequate Power
- Replace the transformer — install a 16–24V AC or 12–24V DC transformer rated at 2A minimum
- Use a dedicated power supply — a quality 12V DC 2A power supply eliminates transformer compatibility issues
- Check cable resistance — long runs of thin wire increase resistance and reduce effective voltage at the doorbell
- Measure voltage at the doorbell terminals — use a multimeter; should read 12–24V DC under load
- Consider a PoE adapter — if you have a nearby network cable, a PoE-to-12V adapter provides clean, stable power
💡 The Existing Doorbell Transformer Trap
Many installers wire the Ajax Doorbell to the existing doorbell transformer to save time. This works in some cases but fails in others — particularly with older transformers that supply AC rather than DC, or transformers rated below 1A. If you are experiencing erratic behaviour after wiring to an existing transformer, replace it with a dedicated 16V AC or 12V DC 2A supply. The cost is under $30 and eliminates an entire category of reliability issues. Sipko Security always installs a dedicated power supply on Ajax Doorbell installations — it is a small cost that prevents a large number of post-installation support calls.
12. Doorbell Placement — How Position Drives Notification Volume
The physical position of the Ajax Doorbell has a direct and significant impact on notification volume. A doorbell mounted in the wrong position will generate excessive notifications regardless of how well the settings are configured — because the fundamental problem is what the camera can see, not how it processes what it sees.
The ideal doorbell position captures the approach path to your door without including the street, footpath, or neighbouring properties in the primary field of view. This is not always possible given the constraints of the mounting location — but understanding the relationship between position and notification volume helps you make the best choice available.
Optimal Doorbell Positioning for Minimal Notification Spam
- Mount height: 1.2–1.5m — at this height, the camera’s field of view is focused on the approach path rather than the street. Higher mounting angles the camera toward the street, increasing traffic-triggered notifications.
- Angle toward the door, not the street — the camera should face the path leading to the door, not the street. If the doorbell faces the street directly, every passing vehicle is in the primary field of view.
- Avoid mounting on a corner — corner positions expose the camera to two streets simultaneously, doubling the traffic-triggered notification volume.
- Use the detection zone to compensate for imperfect position — if the ideal mounting position is not available, use detection zone masking to exclude the street from the active detection area.
- Consider a recessed or angled mount — a wedge mount that angles the camera away from the street can significantly reduce traffic-triggered notifications without changing the mounting location.
- Avoid direct sun exposure — as covered in Section 7, direct sun causes temperature warnings and can also affect motion detection accuracy through thermal changes.
Avoid These
- Facing directly onto a busy street
- Corner position with two street views
- Mounted high (2m+) with shallow downward angle
- Facing west in afternoon sun
- Near a tree or garden with moving vegetation
Aim For These
- Facing the approach path, not the street
- Recessed position with limited street view
- 1.2–1.5m height with slight downward angle
- Shaded from direct afternoon sun
- Plain wall or fence as background
13. Ajax Doorbell Storage — NVR vs Cloud and Notification Behaviour
The Ajax Doorbell does not have an internal SD card slot — all video storage requires either an Ajax NVR or a cloud subscription. This storage configuration affects notification behaviour in ways that many users don’t expect — specifically, the doorbell’s notification frequency can be influenced by whether it has a storage destination for the video clips it generates.
When the doorbell detects motion and has no storage destination (no NVR, no cloud subscription), it still generates notifications — but the clips may not be saved. This can create a situation where you receive notifications but cannot review the footage that triggered them, making it harder to diagnose and tune the notification settings.
Best Configuration
All motion clips are saved to the NVR. You can review every notification clip to understand what triggered it — essential for tuning detection settings. The NVR also enables continuous recording, so you have footage even for events that didn’t trigger a notification.
Notification tuning benefit: reviewing saved clips lets you identify exactly what is triggering false notifications and configure the detection zone and sensitivity accordingly.
Notification-Only Mode
Notifications are sent but clips may not be saved. You receive alerts but cannot review what triggered them. This makes it very difficult to tune the detection settings because you cannot see what the doorbell is detecting.
Recommendation: if you are experiencing notification spam and don’t have an NVR, temporarily enable cloud storage to review the clips and identify the trigger source before tuning settings.
💡 Using Saved Clips to Tune Settings
The most efficient way to tune Ajax Doorbell notification settings is to review the clips that triggered false notifications. Open the Ajax app → Doorbell → Events → review the last 10–20 notification clips. Note: (1) where in the frame the triggering object appears, (2) what type of object it is (car, pedestrian, animal, shadow), and (3) what time of day the false notifications are most frequent. This information tells you exactly how to configure the detection zone and sensitivity to eliminate the false triggers while keeping genuine ones. See our guide on CCTV storage planning for NVR sizing guidance.
14. Ajax Doorbell vs Ring vs Eufy — Notification Spam Comparison
The notification spam problem is not unique to the Ajax Doorbell — it affects virtually every smart doorbell on the market. Understanding how Ajax compares to the alternatives helps set realistic expectations and informs the decision about whether to stick with Ajax or consider a different platform.
The key difference between Ajax and consumer doorbells like Ring and Eufy is the ecosystem: Ajax is designed as part of a professional alarm system, while Ring and Eufy are standalone consumer products. This affects both the notification capabilities and the configuration options available.
The bottom line: the Ajax Doorbell’s notification spam problem is not worse than Ring or Eufy — it is the same problem that affects all smart doorbells. The difference is that Ajax provides more powerful configuration tools (detection zone polygon editor, per-user notification settings, alarm system integration) that allow more precise tuning once you know how to use them. See our Ajax Doorbell vs Ring comparison for a full feature analysis.
15. Melbourne-Specific Notification Challenges
Melbourne’s residential environment creates specific notification challenges for Ajax Doorbell installations. Properties in the suburbs Sipko Security services most frequently share common characteristics that affect doorbell notification volume in predictable ways.
Brighton, Hampton, Kew
Properties on busy streets in Brighton, Hampton, and Kew face the highest notification volumes — every passing car, cyclist, and pedestrian triggers the doorbell if the detection zone is not correctly configured. Detection zone masking to exclude the street is essential for these properties. A correctly configured detection zone reduces notifications from 200+ per day to under 20.
Toorak, Malvern, Camberwell
Properties in Toorak, Malvern, and Camberwell often have dense garden vegetation near the front door. Moving leaves and branches in wind trigger constant motion detections. The fix: exclude vegetation areas from the detection zone, and reduce sensitivity to Low if vegetation movement persists.
Portsea, Sorrento, Mount Martha
Holiday homes on the Mornington Peninsula face a different challenge: when the property is unoccupied, any movement at the door is significant and should generate a notification. When occupied, the doorbell generates constant notifications from family activity. The arm state-based automation rule (Section 10) is the ideal solution — full notifications when armed (unoccupied), minimal notifications when disarmed (occupied).
✅ Sipko Security’s Melbourne Doorbell Configuration Standard
On every Ajax Doorbell installation, Sipko Security configures: detection zone excluding the street and footpath, motion sensitivity set to Medium, human detection filter enabled at Medium sensitivity, 30-second notification cooldown, and per-user notification profiles. This standard configuration eliminates notification spam for the vast majority of Melbourne residential installations. If you’re having your Ajax system installed by Sipko Security, this configuration is included as standard — you won’t experience notification spam from day one.
16. When the Ajax Doorbell Is the Wrong Tool for the Job
Not every notification problem is a settings problem. Sometimes the Ajax Doorbell is simply the wrong device for the location — and no amount of sensitivity tuning will produce a usable result. Recognising this early saves significant time and frustration, and leads to a better security outcome.
The Ajax Doorbell is designed for residential front doors with moderate foot traffic and a clear approach path. When installed in environments it was not designed for, notification spam becomes structurally unavoidable — the device is doing exactly what it is supposed to do, but the environment makes that behaviour unworkable.
Cafes, Retail, Offices
A doorbell at a cafe entrance that sees 200+ customers per day will generate 200+ notifications per day — even with perfect settings. The device is working correctly; the environment is wrong for it. For high-traffic commercial entrances, the right solution is an Ajax retail security system with a dedicated entry sensor and CCTV, not a doorbell.
Better solution: Ajax MotionCam or DoorProtect on the entry, with CCTV for visual verification. Notifications only when the alarm is armed (after hours).
Apartments, Townhouse Complexes
A doorbell at a shared building entrance used by 10+ residents generates constant notifications for every resident’s comings and goings. The detection zone cannot be configured to exclude legitimate residents while still catching genuine visitors — everyone uses the same path.
Better solution: An intercom system with per-unit call routing, or an access control system that logs entries without generating notifications for authorised users.
Corner Properties, Open Frontages
Corner properties where the doorbell has a wide-angle view of two streets, or properties with open frontages where the public footpath runs directly past the door, cannot be effectively masked. The detection zone cannot exclude the public area without also excluding the approach path.
Better solution: Reposition the doorbell to a side entrance with a defined approach path, or use a different doorbell platform with more granular zone masking.
Poolside, Beachfront, Windy Locations
Properties where the doorbell faces a pool (water reflections trigger motion), a beach (constant movement), or a very exposed location with persistent wind-driven vegetation movement will generate constant environmental notifications regardless of sensitivity settings.
Better solution: Relocate the doorbell to a sheltered position facing the approach path only, or use a PIR-only sensor (no camera) for the exposed location and a separate camera for visual verification.
⚡ The Honest Assessment
If you have applied every fix in this guide and are still receiving unacceptable notification volumes, the problem is likely the installation location rather than the settings. Sipko Security offers a free site assessment for clients experiencing persistent notification issues — we will tell you honestly whether the doorbell can be made to work in your location, or whether a different solution is needed. Call 0406 432 691 to book.
17. Complete Fix Checklist — Ordered by Impact
Work through this checklist in order. Each fix is ranked by how much it typically reduces notification volume. Most users resolve the problem within the first three items. If you reach the bottom of the list and notifications are still excessive, call Sipko Security for an on-site assessment.
Fixes 1–4: Eliminate 80–90% of Spam
- Configure detection zone masking — exclude the street, footpath, and any public areas. Focus the zone on the approach path to your door only. This single fix eliminates the majority of notification spam for street-facing doorbells. (Section 3)
- Reduce motion sensitivity to Medium — change from the default High/Maximum to Medium. Monitor for 24 hours. If still excessive, reduce to Low. (Section 2)
- Enable AI human detection filter — set notifications to “Humans Only.” This filters out cars, animals, and environmental movement. Set sensitivity to Medium. (Section 4)
- Set notification cooldown to 30 seconds — prevents the same event from generating multiple notifications. Reduces burst spam from slow-moving subjects. (Section 5)
Fixes 5–9: Address Specific Causes
- Fix WiFi stability — if you are receiving disconnect/reconnect notification spam, move the router closer, add a WiFi extender, or switch the doorbell to a 2.4 GHz network. (Section 6)
- Update firmware — check for and install the latest Ajax firmware via the app. Newer firmware has improved detection filtering. (Section 8)
- Configure per-user notification profiles — disable doorbell motion notifications for household members who don’t need them. Keep them enabled only for the primary security contact. (Section 9)
- Set up quiet hours automation — disable motion notifications overnight (e.g., 11pm–7am) using Ajax automation rules. Bell press notifications remain active. (Section 10)
- Check power supply — if the doorbell is running on battery, low battery causes erratic behaviour including false motion detections. Ensure the doorbell is wired to a stable power source. (Section 11)
Fixes 10–14: Fine-Tuning and Edge Cases
- Reposition the doorbell — if the current position faces the street directly, relocate to a side wall or recess that limits the field of view to the approach path. (Section 12)
- Add sun shading — if the doorbell faces direct afternoon sun, add a physical shade or hood to reduce thermal-triggered false detections. (Section 7)
- Add an NVR for clip review — if you cannot identify what is triggering false notifications, add an Ajax NVR to save clips. Review the clips to identify the trigger source, then tune settings accordingly. (Section 13)
- Use arm-state automation — configure full notifications when the alarm is armed (property unoccupied) and minimal notifications when disarmed (property occupied). (Section 10)
- Report false human detections — tap “Report” on every false human detection clip. This trains the AI model and improves accuracy over time. (Section 4)
⚠️ If None of These Work
If you have worked through this entire checklist and are still experiencing unacceptable notification volumes, the issue is almost certainly the installation location rather than the settings. See Section 16 for guidance on when the Ajax Doorbell is the wrong tool for the location, and contact Sipko Security on 0406 432 691 for an on-site assessment.
Frequently Asked Questions — Ajax Doorbell Notifications
Why does my Ajax Doorbell send so many notifications at night?
Night-time notification spam is usually caused by the doorbell’s IR night vision mode triggering on insects, moths, and spiders attracted to the IR illuminators. The IR light is invisible to humans but extremely attractive to insects — a moth flying past the lens at night looks like significant motion to the detector. Fix: reduce sensitivity to Low for night hours using an automation rule, or add a physical insect deterrent near the doorbell. Also check that the IR illuminators are not reflecting off a nearby wall or surface, which creates a bright zone that amplifies small movements.
Can I set different notification settings for different family members?
Yes — this is one of the most useful and underused features of the Ajax app. Each user account can have its own notification profile for the doorbell. Go to Hub Settings → Users → select the user → Notification Settings → configure which events they receive notifications for. For example: the primary security contact receives all motion and bell press notifications; other household members receive bell press only. This eliminates the situation where every family member’s phone is buzzing with every motion event.
My Ajax Doorbell keeps disconnecting and reconnecting — is this a notification problem?
Yes — disconnect/reconnect cycles generate their own notification spam entirely separate from motion detection. Each disconnect and reconnect generates a system notification. If you are seeing this pattern, the cause is almost always WiFi instability: the doorbell is at the edge of your WiFi coverage and drops in and out. Fix: move your router closer, add a WiFi mesh node or extender near the doorbell, or switch the doorbell to a 2.4 GHz network (better range than 5 GHz). Also check that the doorbell’s power supply is stable — power fluctuations can cause the same disconnect/reconnect pattern. See our guide on preventing Ajax false alarms for related connectivity troubleshooting.
Does the Ajax Doorbell work without a subscription?
Yes — the Ajax Doorbell works without a subscription for basic functionality: bell press notifications, motion detection notifications, and live view. A subscription (Ajax Cloud or NVR) is required for video clip storage and review. Without storage, you receive notifications but cannot review the footage that triggered them — which makes it very difficult to tune the detection settings. If you are experiencing notification spam and don’t have an NVR, temporarily enabling cloud storage to review clips is strongly recommended before adjusting settings blindly.
Will reducing sensitivity mean I miss genuine visitors?
At Medium sensitivity, no — you will still detect any person who approaches within 5–6m of the doorbell. At Low sensitivity, you may miss detections at the outer edge of the field of view (6–8m range), but you will still detect anyone who comes close enough to ring the bell. The key is to combine sensitivity reduction with detection zone masking — the zone ensures the doorbell is focused on the approach path, and the sensitivity ensures it detects anyone on that path. Always test by walking through the detection zone yourself after any sensitivity change.
How do I stop Ajax Doorbell notifications when I’m home?
The cleanest solution is an automation rule that disables motion notifications when the alarm is disarmed (i.e., when you are home) and re-enables them when the alarm is armed (when you leave). In the Ajax app: Automation → Create Rule → Trigger: Hub Disarmed → Action: Disable Doorbell Motion Notifications. Create a second rule: Trigger: Hub Armed → Action: Enable Doorbell Motion Notifications. Bell press notifications remain active regardless of arm state — you will still know when someone rings the bell. This is the professional standard configuration for residential doorbells and eliminates the “constant notifications while I’m home” problem entirely.
Is the Ajax Doorbell better or worse for notifications than Ring?
Out of the box, both generate similar notification volumes — both default to high sensitivity and full-frame detection. Ring has a slight edge in AI human detection maturity (larger training dataset, longer on the market), but Ajax has better alarm system integration and a more granular detection zone editor. After proper configuration, both can be tuned to a manageable notification level. The key difference is that Ajax is part of a professional alarm ecosystem — when configured correctly by a professional installer like Sipko Security, it outperforms Ring significantly as a security device. See our full Ajax Doorbell vs Ring comparison for a detailed breakdown.
Can Sipko Security fix my doorbell notification problem remotely?
Many notification issues can be resolved remotely — we can walk you through the settings changes over the phone or via a remote session. For issues that require physical repositioning, detection zone reconfiguration based on a live camera view, or power supply work, an on-site visit is needed. Call 0406 432 691 or email sipkosecure@gmail.com — we will assess whether a remote fix is possible before booking a site visit. We also offer ongoing security system maintenance and support for all our clients.
Where We Service in Melbourne
Sipko Security provides Ajax Doorbell installation, configuration, and notification tuning across Melbourne and the Mornington Peninsula. If your doorbell is spamming alerts and you want it fixed properly, we cover:
Not on the list? We cover all of Melbourne metro and surrounds. Call 0406 432 691 to confirm coverage for your area.
Still Getting Spammed With Notifications?
Sipko Security fixes Ajax Doorbell notification issues on-site across Melbourne. One visit. Properly configured. No more spam.
Still Getting Notification Spam?
We fix it on-site. One visit. Properly done.
📞 Tap to Call — 0406 432 691 ✉️ Email Sipko SecuritySources & Further Reading
Australian Government & Regulatory Sources
