“Ajax offline” can mean three different things. The hub may have lost its service connection, one detector may have lost contact with the hub, or the system may work while your phone receives no notifications. Treating these as one fault can lead to unnecessary setting changes and false reassurance.
Record the exact message and time, inspect only what you can see without opening or reconfiguring equipment, and contact the installer. This page cannot see your Ajax system or certify that your premises are protected. Serralleria Catalana offers Ajax alarm installation in Lleida; support for someone else’s existing installation should never be assumed.
What does the app actually identify?
A warning naming the hub concerns its central connection or power. One named detector points to that device or its link, not automatically to a complete outage. If the hub appears online but your phone has no alerts, phone permissions and user-level notification settings may be involved. The available status and terminology depend on the model and app version.
Do not trigger a detector merely to see whether an alert arrives unless you know the correct test procedure, siren behaviour and monitoring arrangements. Do not remove devices or reset the hub just to clear a warning; its event history and configuration may be essential to the installer.
SEPARATE THE CHANNELS
What is actually offline?
Observe the app and accessible indicators; do not dismantle or restart the system because of this guide.
Record the exact message and time; do not assume the sensor is at fault.
This cannot test your alarm or send data. If the property is unprotected, use an alternative measure and contact the installer.
If the hub appears offline
Check whether power failed and whether the router shows a general service problem. Observe visible connections without pulling cables or opening the hub. A phone with working internet does not prove that the hub’s own path is working. Some Ajax hubs support Ethernet and mobile-data channels, but the actual channels and redundancy depend on the exact model and setup.
Ask the installer which channel your unit uses, whether its SIM service is active, and who receives supervision events. Do not infer battery runtime or restoration time from a generic guide. If the property may be unprotected, take a proportionate alternative security measure while the responsible professional confirms the status.
If one device is offline
Record its exact name, approximate location and when the warning first appeared. Power, obstacles, distance or configuration may be relevant, but none is confirmed without inspecting the installation. Do not move or open a sensor blindly: an anti-tamper alarm or changed positioning could complicate the fault. Treat that zone as unverified until function is confirmed.
If the hub is online but alerts are missing
Check whether other phone notifications arrive, whether the Ajax app has notification permission and whether your user account has the expected event categories enabled. The manufacturer’s documentation distinguishes channels such as push and SMS in relevant settings. A recent phone change, new account or altered notification preference is important context for support. Do not use a real incident as a test.
A four-signal incident log
Turn “it stopped working” into observable facts for the installer. Never include passwords, alarm codes or full SIM numbers.
1. Message and time
Copy the warning exactly, the hub or device name, and approximate first-event time. Distinguish an active warning from one that has cleared.
2. Power and recent changes
Note electrical outages, router replacements, building work, moved sensors or a new phone. Do not touch equipment solely to complete the note.
3. Known connection path
State whether you know the hub uses a cable, mobile data or both. “Unknown” is better than guessing based on a nearby router.
4. Responsible contact
Record the installer, system administrator or contracted monitoring centre. Ask when supervision can be considered restored.
When to escalate and what to ask
Contact the responsible person promptly if the property may be unprotected, a critical entrance is not verified or tampering is reported. A recurring fault merits inspection even when it resolves itself; restored connectivity does not explain why it failed. Send the log, hub model and recent changes so the professional can plan safe tests and parts.
For a new installation, ask how connection failures are detected, which events each user receives and what procedure applies during an outage. Physical doors and windows matter too. An electronic alarm cannot repair a weak lock, just as a good lock cannot notify you about an incident. A locksmith in Lleida should assess the actual access without promising that an app eliminates all risk.
Start with the exact screen, not a general description
People often say that an alarm is offline when they are looking at different screens. One person may see a warning naming the hub; another may be reading the status of a single detector; a third may see no warning at all but notice that a phone has stopped displaying messages. These observations lead to different questions. A hub warning concerns a central connection. A device warning concerns that device or its link to the hub. Missing phone notifications concern the user’s delivery path until the system’s own status is checked. None of these observations alone establishes the condition of every part of the installation.
Preserve the wording before it disappears from the main screen. Note whether the app says that a fault is active or that a connection has already returned. If an event list is available to your user account, record the first relevant time and any later recovery time. Avoid interpreting an icon from memory when you can give the installer the actual text. A screenshot can help, provided you remove account details, codes and other sensitive information before sharing it privately with the verified support contact.
Who saw the message matters as well. A system administrator and another user may have different permissions and notification choices. If one household member receives an event and another does not, that difference is useful evidence about recipients or phones, but it does not prove that every hub communication channel is healthy. Ask the administrator which event categories each person is expected to receive. Do not exchange passwords to compare accounts. Report the observation and let the responsible person check permissions through the appropriate process.
Build a timeline without assuming a cause
The time of the first warning can narrow an investigation. Perhaps the building lost power, the internet provider reported an interruption, a router was replaced, building work occurred near a detector, or a phone was changed. Record these as events, not conclusions. Two things happening on the same day do not prove that one caused the other. An installer can compare your timeline with the system’s records and the actual configuration. The distinction is especially valuable with intermittent faults, which may not be visible by the time someone arrives.
For each episode, note the start time, the affected name as displayed, whether other devices showed warnings, and the approximate time the status changed. If you only learned about the problem later, say so rather than inventing a precise start. Mention a power cut even if power has returned. Mention a router replacement even if ordinary web browsing works. These facts do not diagnose the alarm, but they help the professional decide which questions to investigate first.
A recovered connection is worth documenting. It may mean that a temporary condition ended, while the reason remains unknown. Do not erase the incident from your notes because the screen now looks normal. Repeated short interruptions may deserve attention, especially when they affect the same critical entrance. Compare episodes by date and context, then agree with the installer how recurrence will be monitored and when a site visit is warranted. The aim is to understand what happened, not merely to make a warning disappear.
What a hub warning does and does not tell you
Begin with external observations. Is there electricity in the property? Does the router show a general problem? Can other equipment on that network reach the internet? Has the provider, router or cabling recently changed? You can relay these facts without opening the hub, pulling a connector or changing the alarm configuration. A lit indicator is not a certificate that all messages are being delivered. Equally, a working phone connection says nothing conclusive about a hub’s own cable or mobile-data service.
Different Ajax hubs and installations can have different communication arrangements. Some support more than one path, but a possible feature is not proof that it was installed, activated or available during the event. Ask for the exact hub model, the channels specified for that installation, and which of them were operating at the relevant time. A router beside the hub does not establish that Ethernet is in use; the presence of a SIM does not establish active service. Avoid publishing a SIM number, network credentials or identifying details when asking for assistance.
If the building lost power, tell the installer when the interruption began and when supply returned. Do not borrow a battery-duration figure from another model or assume that one illuminated component means the entire system behaved as intended. The professional can inspect the appropriate events and assess the installed equipment. Until the status is confirmed, decide on a proportionate temporary measure for the property with the responsible person. A guide cannot calculate the protection available in a particular building during an outage.
Keep monitoring arrangements separate from phone alerts
Where a monitoring centre is contracted, use the contact method stated in that contract to ask what status it recorded. Do not assume that the centre sees the same display as your app or that a push notification on your phone proves professional receipt. Conversely, a phone that stays silent does not prove that the contracted monitoring service has stopped. Ask the centre or system administrator what they can actually confirm, record the answer, and pass it to the installer. That makes the subsequent investigation more precise.
The responsibilities also differ. The installer may maintain devices and configuration; an administrator may control users; a monitoring centre may have its own procedures for receiving events. Find out who is responsible for each part before changing anything. If you are not the account owner, explain the warning to the person who is. For an installation fitted by another company, its original provider may have documentation, permissions and a maintenance agreement that a new contractor does not have. Contacting that provider first is usually the clearest route to a reliable diagnosis.
Ask what the monitoring arrangement covers rather than assuming that all warnings follow the same route. An alarm event, loss of a connection, power issue and maintenance notice may have different recipients under the chosen settings and contract. The relevant question is not simply, “Did somebody get a message?” It is, “Which event, through which agreed channel, reached which responsible recipient?” Record the answer without sharing private account information in a public forum.
When a single detector is named
A named detector changes the scope of the problem. The hub may still show a connection while one device’s communication is not verified. Tell the installer the device name displayed in the app and the broad function of its zone, such as an exterior entrance or an internal room. You need not publish a detailed floor plan. The practical priority depends partly on what that zone is meant to protect. Treat an important affected opening as unverified until the responsible professional confirms its operation.
Several factors can be relevant to a device warning, including its power condition, the surrounding environment, obstacles, position or configuration. A screen message does not choose among them. Do not shift a sensor toward the hub, open its cover, replace parts or pair it again without the appropriate installation procedure. Doing so can alter coverage or create a new fault and may also trigger an anti-tamper event. The installer can check the model-specific information, link condition and recorded events in context.
Intermittent device warnings deserve a timeline of their own. Does the same detector reappear each time? Did the warning begin after building work or a change near that area? How long did it remain visible? Give the technician observations, not a verdict about radio conditions or batteries. When a controlled check is completed, ask whether the affected zone itself was verified. A normal-looking hub icon does not answer that question on behalf of the detector.
When only the phone seems silent
First establish whether the phone displays notifications from other applications and whether Ajax has notification permission in the phone’s settings. A new device, account change, focus mode or power-saving behaviour may be relevant. These are user-visible checks that do not require opening the hub. Tell support when the phone or account changed, and whether another authorised user received the same kind of event. A comparison between users is a clue about delivery, not a substitute for checking the system record.
Notifications are not one undifferentiated stream. The manufacturer’s guidance describes different kinds of events and delivery methods, including push and, where configured and supported, other routes. Ask the system administrator which categories your account should see and how each is meant to arrive. Receiving one kind of notification does not establish that you will receive every other kind. A missing push alert does not tell you whether the underlying event was registered by the hub or a monitoring centre.
Do not manufacture a real incident to test the phone. If a test is needed, arrange it with the installer and any monitoring centre involved. Agree beforehand on its start, the expected event, the people who should receive it and how the test will be closed. Afterwards, record the separate outcomes: what the hub logged, what a particular phone displayed and what the professional channel confirmed. A test of one recipient at one moment cannot certify every device or future message.
Prioritise risk while the status is uncertain
The urgency of a warning depends on the building and the area affected, not just the colour of an app label. A critical exterior entrance whose detection cannot be confirmed, an anti-tamper warning or a property left unattended with an active issue should be reported promptly through the agreed support channel. Describe exactly what is known and unknown. “The entrance detector has shown offline since approximately nine” is more actionable than “the entire alarm has failed” when the latter has not been established.
If there is an immediate threat to people or an incident in progress, follow the appropriate emergency procedure. A technical support request is not a replacement for urgent help. For a less immediate connectivity problem, consider a temporary security measure suitable for the actual property with the responsible person. This might involve checking that normal doors close correctly or arranging appropriate supervision, but it must not obstruct safe exit or rely on an unverified system state. Do not improvise changes to equipment or access hardware while the fault is being assessed.
Make a note of who decided on the temporary response and when it will be reviewed. That matters if the warning clears before the professional calls back. A temporary arrangement should end because the relevant function has been checked, not because everyone has become accustomed to the message. Where an affected area remains unverified, say so plainly to other authorised users who rely on the system. Avoid both alarmist claims about a total outage and reassurance that has no evidence behind it.
Make the first support call efficient
Begin with four facts: the exact warning, the named component, the approximate first time and whether it remains active. Then add only relevant changes you actually observed: power loss, router work, a moved detector, a new phone or a change of user. If you do not know the hub model or communication path, say “unknown”. The incident log above keeps these details together and helps the installer decide whether a remote review is possible or a visit is needed. It also reduces the chance of repeating risky guesses during the call.
Say who installed the system, who administers it and whether there is a maintenance or monitoring agreement. Use the verified contact in your records rather than sending a screenshot to an unconfirmed number or a public group. If a screenshot is necessary, remove codes, addresses and full account identifiers that the recipient does not need. Ask which information the professional needs next; do not provide credentials merely because someone claims they can help. Secure handling of the incident record is part of maintaining the installation responsibly.
Ask what will count as a successful outcome. “The red label went away” is an observation, but may not cover the device, communication path and notification route that prompted the call. The professional should explain what was checked, by whom and under which procedure. If one part is still pending, keep it on the follow-up list. A clear conclusion can also be honest about uncertainty: the system may currently appear connected even though the cause of repeated dropouts has not yet been established.
Plan a new installation for an eventual outage
When considering a new Ajax installation, ask more than how many detectors will be fitted. Ask which communication channels the proposed hub can support, which ones the quotation actually includes, and how loss of a path would be reported. Model capability, a paid service and an installed configuration are not interchangeable. Ask what the user will see and, if a monitoring centre is part of the plan, what it will receive. Any claim that the system is “always connected” needs qualification because power, networks and external services can fail.
Agree responsibilities in advance. Who will administer user permissions, keep the model and service documentation, receive detector warnings and arrange checks after a router change? Who will explain the expected behaviour to a new occupant? These are operational questions, not decorative extras. An app is useful when people know how to respond to its messages. Written contact details and a simple escalation process can prevent a minor warning from becoming days of uncertainty about who should act.
Include physical entrances in the assessment without confusing them with connectivity. A detector cannot make a weak door close properly; a strong lock cannot send an electronic alert by itself. Their roles are complementary. A locksmith should inspect actual doors, windows and use patterns, while the alarm design addresses detection and reporting. The proposal should separate equipment, installation, configuration, user guidance and any maintenance that is genuinely offered. Do not assume that every feature associated with the Ajax name is present in the particular model being quoted.
Questions to resolve before closing the incident
Does an offline warning mean the whole alarm is off?
Not necessarily. The warning may refer to the hub, one detector or the delivery of phone alerts. The installed model and channels also matter. It is equally wrong to conclude from that uncertainty that the whole property is protected. Identify the named element and ask the responsible person what is actually verified. If a critical entrance cannot be confirmed, use a proportionate temporary response until a professional checks it.
Will restarting the router be enough?
A general internet problem might be relevant, but it does not establish that the hub uses that path or that it is the only fault. Preserve the warning and time before any agreed maintenance action. Follow the procedure supplied for your installation with the responsible person. Do not reset the hub, remove devices or change security settings merely to clear an icon. A transient improvement after a restart is not an explanation for an intermittent failure.
Why does one user receive an alert and another not?
Permissions, event categories, phones and notification settings may differ. That difference is a lead for investigation, not proof of a particular fault. Each user can report what appeared and when without exchanging passwords. An administrator can check the intended recipients; a coordinated test can then separate an event recorded by the system from its delivery to each authorised phone. Do not extrapolate from one successful alert to every category.
When can the issue be called resolved?
When the responsible professional has either identified the cause or clearly documented what was verified, what remains uncertain and how recurrence will be handled. Keep the result alongside the original timeline. If a component or setting was changed, ask what behaviour should improve and how it will be checked without an improvised alarm. If the fault returns, compare the new episode with the earlier one. Resolution is a documented conclusion about a specific installation, not a universal period after an app indicator turns green.
In a shared building or business, agree who can review the full event record and who may authorise a controlled test. One user may see only part of the system’s information. Collect each person’s observation without asking them to exchange credentials, then give the installer a common timeline. State which zone was expected to be supervised and when, without circulating detailed access patterns publicly. After the review, tell affected users what was verified, what remains open and who will respond if the warning returns. That closes the communication gap as well as the technical ticket.
Planning an Ajax installation? Tell us about the accesses and areas you want to monitor. For a fault on an existing system, contact its installer first.
Technical reference: official Ajax Systems support. Features and channels depend on the exact model and configuration.
Reviewed content
Professional experience behind this guide
Serralleria Catalana reviews this content against real work with openings, locks, cylinders, doors and safes in Lleida. When price depends on the door, time, hardware or diagnosis, we explain that before giving a fixed figure.
- Published
- 14/11/2026
- Updated
- 11/11/2026
- Reviewed by
- Serralleria Catalana
- Standard
- Local experience, proportionate security and clear pricing.