Support

AX PRO Offline or Notifications Not Working

This guide addresses AX PRO shows offline or alarm/fault notifications do not reach the phone in the order technical support would test it: preserve what matters, open the correct screen, correct the proven cause and verify the result.

Alarm Communications

Summary

Follow the four stages below to diagnose AX PRO shows offline or alarm/fault notifications do not reach the phone without losing evidence, configuration or device ownership.

Applies to

  • Hikvision AX PRO communications
  • Hik-Connect alarm notifications

Difficulty and time

Difficulty: Advanced

Estimated time: 25 to 60 minutes

What you will need

  • The exact model and current firmware or app version
  • Administrator access where authorised
  • A photo or screenshot of the current status
  • One controlled test case and its exact time

What this guide covers

  • Preserve and reproduce the fault
  • Open the correct diagnostic screen
  • Correct the proven cause
  • Verify and document the result

Use this page when AX PRO shows offline or alarm/fault notifications do not reach the phone. It includes the menu or screen to look for, the status that matters and a repeatable proof test.

Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.

Before you start

Protect the current system and record a baseline before changing anything.

  • Write down the exact symptom: the app cannot reach the panel, or a controlled event appears in history but no push arrives.
  • Photograph the current status, error text, wiring or timeline as applicable.
  • Record the last known working time and anything changed immediately before the fault.
  • Record owner account, network settings and active faults before rebinding or reinstalling.
Important

Coordinate every live alarm and communications test

Notify monitoring and occupants. Do not deliberately trigger emergency devices or disable communications without an authorised test plan.

If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.

What usually causes this

  • LAN/Wi-Fi/cellular path failed
  • Panel cloud status is offline
  • User notification category is disabled
  • Phone OS suppresses the app

Step 1: Preserve the current state and reproduce the fault

Begin with a repeatable baseline so you know whether a later change genuinely helped.

  • Reproduce the problem once and record: the app cannot reach the panel, or a controlled event appears in history but no push arrives.
  • Note whether every device or user is affected, or only one.
  • Compare one working path with the failing path if a comparison exists.
  • Record owner account, network settings and active faults before rebinding or reinstalling.

Step 2: Open the correct screen and inspect the evidence

The primary diagnostic location is Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings. Do not change anything until the displayed state is recorded.

  • Open Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings. Menu wording can vary by model and firmware; use the nearest equivalent label.
  • Check panel power, current faults and LAN/Wi-Fi/cellular status locally.
  • Prove whether the controlled event appears in panel/app history.
  • Confirm the signed-in owner, shared-user permissions and phone OS notification settings.

Step 3: Correct only the cause you proved

Use the matching correction below. Make one change, save it, then repeat the same test.

  • Restore the primary network, gateway/DNS or configured cellular path.
  • Correct panel time and verify cloud/platform Online status.
  • Enable the required alarm/fault notification categories for the intended user.
  • Allow Hik-Connect background activity, notifications and non-restrictive battery mode.

Step 4: Verify, monitor and document the handover

A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.

  • Create an authorised walk-test event and note the time.
  • Confirm it appears in panel history.
  • Lock the phone and confirm the intended user receives the push.
  • Test the commissioned backup path separately without creating an uncontrolled alarm.
Worked example

Controlled support test

Situation: The reported symptom was: the app cannot reach the panel, or a controlled event appears in history but no push arrives.

Solution used: The current state was recorded in Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings, one matching correction was made, and the same test was repeated.

Why this was chosen: This separated the proven cause from unrelated settings.

Installation notes: The final screenshot and test time were saved with the handover record.

Official reference used for this guide

Menu names differ between releases. Confirm model-specific behaviour in Hikvision AX PRO User Manual before firmware, reset, storage or security-sensitive work.

Common mistakes

  • Changing several settings before repeating the original test.
  • Using a factory reset, initialise or format option as an early troubleshooting step.
  • Treating an app symptom as proof that the local hardware or recording has failed.
  • Failing to record the model, version, exact error and test time before escalation.
  • Assuming similar-looking models use identical menus or features.

Troubleshooting table

Symptom What to check What to do next
the app cannot reach the panel, or a controlled event appears in history but no push arrives panel network offline, cloud binding/account issue, event category disabled or phone background suppression Open the named diagnostic screen, record the displayed state and use the matching correction above.
The named menu is not visible Different firmware, permissions or model capability Do not substitute a destructive menu. Capture the model and version and use its official manual.
The change saves but the fault remains The selected cause was not the root cause Undo the change if appropriate, return to the baseline and compare the failing path with a working one.
Local test works but app or client test fails Account, permission, cloud or remote-network path Keep the proven local configuration and diagnose the remote path separately.
Problem returns later Intermittent power, cable, storage, network or schedule condition Record the new failure time and status; correlate it with logs, events and the last known working interval.

When to contact support

Contact SecurityWholesalers support when the panel is online and records the test event but the verified owner phone receives no push.

Send the order number if available, exact model, firmware or app version, screenshot of Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings, the failure time, and the result of the local proof test.

Related support guides

Related buying guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

  • Where should I click first for AX PRO notifications not working?

    Start at Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings. Record the existing state before changing it because labels and available options can vary by model and firmware.

  • What should I look for on that screen?

    Look for panel network/cloud Online status, event history, owner/user permission and notification category.

  • What must I avoid changing during the first check?

    Notify monitoring and occupants. Do not deliberately trigger emergency devices or disable communications without an authorised test plan.

  • How do I prove the correction worked?

    One controlled event should appear in panel history and reach the locked phone with matching time and zone.

  • Why might my menu names look different?

    Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.

  • Should I factory-reset the device?

    Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.

  • What should I send technical support?

    Send the exact model and version, screenshot of Hik-Connect > AX PRO > Settings/Network Status and Notification Settings, plus panel Communication settings, exact error text, failure time, what changed before the fault and the result of the controlled local test.

  • Can configuration changes recover data or events that were never recorded?

    No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.

Further Reading
Guide Page Hikvision AX PRO Alarm Support Overview Overview Guide Page Hikvision Support Guides Guide Page HiLook Support Guides

We make product support and ordering easy! Reach out to our help team :)
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Send Cart Email
Your cart email sent successfully :)