Support
Access Control Controller or Door Is Offline
Controller Connectivity
Summary
Follow the four stages below to diagnose an access controller or managed door shows offline in the software without losing evidence, configuration or device ownership.
Applies to
- Networked access controllers
- Single and multi-door managed systems
Difficulty and time
Difficulty: Advanced
Estimated time: 20 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 an access controller or managed door shows offline in the software. 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 controller is unreachable, changes will not apply, or live door events have stopped.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Export configuration and record controller identity before deleting/re-adding it.
Offline access control may affect life-safety and site security
Do not bypass locks, egress devices or fire interfaces. Maintain safe exit and follow the site emergency/security procedure.
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
- Controller power/backup battery failed
- Network cable or switch port is down
- IP address conflicts or changed subnet
- Management service/communication settings changed
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 controller is unreachable, changes will not apply, or live door events have stopped.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Export configuration and record controller identity before deleting/re-adding it.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Access-control client > Device Management > Online Status, then controller Network/Communication settings. Do not change anything until the displayed state is recorded.
- Open Access-control client > Device Management > Online Status, then controller Network/Communication settings. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Check enclosure power, battery/PSU indicators and network link LEDs.
- Record the controller IP, subnet, gateway and last-online time.
- From the management server, test whether the controller address is reachable and whether another device now uses it.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Restore stable approved power and network link before software changes.
- Correct IP/subnet/gateway or reserve a conflict-free address.
- Confirm server and controller time and required communication service/port.
- Reconnect or re-add only after recording device identity and existing configuration.
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.
- Confirm Online status remains stable.
- Read a live door contact transition and credential event.
- Apply one harmless test change and confirm successful synchronisation.
- Check offline events have backfilled if the model buffers them.
Controlled support test
Situation: The reported symptom was: the controller is unreachable, changes will not apply, or live door events have stopped.
Solution used: The current state was recorded in Access-control client > Device Management > Online Status, then controller Network/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 Access Control Terminal 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 controller is unreachable, changes will not apply, or live door events have stopped | power failure, network link/IP conflict, wrong server communication settings or controller hardware fault | 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 power and network are proven but the controller will not remain online or door safety behaviour is affected.
Send the order number if available, exact model, firmware or app version, screenshot of Access-control client > Device Management > Online Status, then controller Network/Communication settings, the failure time, and the result of the local proof test.
Related support guides
- Access Control Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- Access Control Buying Guide - Door hardware, credentials and system-planning guide.
Relevant product categories
- Access Control Products - Controllers, readers, locks and credentials.
- Door Strikes - Electric strike hardware.
- Maglocks - Electromagnetic locking hardware.
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 access control controller offline?
Start at Access-control client > Device Management > Online Status, then controller Network/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 Online/Offline, last communication, IP/MAC, firmware, pending changes and synchronisation errors.
-
What must I avoid changing during the first check?
Do not bypass locks, egress devices or fire interfaces. Maintain safe exit and follow the site emergency/security procedure.
-
How do I prove the correction worked?
Hold stable Online status, observe live input and credential events, and complete one successful configuration synchronisation.
-
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 Access-control client > Device Management > Online Status, then controller Network/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.