What should a normal HiLook online handover include?

A proper HiLook handover should include local recorder health, the right owner account, platform access online, the recorder added correctly into the app, live view and playback tested on mobile data, and alerts tested properly if alerts were part of the brief.

Do I add the recorder or each camera to the app?

On most HiLook jobs the recorder is the better device to hand over, because it gives the user one clean path for live view and playback across the whole site.

Why are HiLook notifications often missing on the phone?

Usually because the event rule, push linkage, phone permission, or battery restrictions were not fully tested after the app was added.

Should a family or business share one admin login?

Usually no. Cleaner user sharing avoids confusion when phones change or access needs to be removed later.

Can the wrong timezone make the app feel broken?

Yes. The app may still connect, but playback and event review become confusing if the recorder clock is wrong.

What should I photograph before asking for support?

The recorder network screen, platform or cloud screen, QR label, and the exact app error or offline state on the phone.

Commercial

How to Get HiLook CCTV Online

Most HiLook systems are handed over around HiLookVision. Some Hikvision-backed paths may still reference a Hik-Connect style workflow depending on the exact model family or firmware, so the safer approach is to confirm the app path during commissioning instead of assuming it after the install.

App and Remote Access

HiLook network video recorder — Most HiLook support problems begin at the recorder, the app handover, or the event setup, not with the camera body by itself.

What this guide covers

What a healthy HiLookVision handover should look like on a normal site
How to bind the recorder or camera properly instead of only half-finishing the app setup
Why push notifications fail even when live view appears to work
Two worked examples showing the actual online setup path and what fixed the handover

What the app should do on a normal job

On a healthy HiLook system, the app should do four basic things reliably: show live view, allow playback, stay linked to the correct device account, and deliver the notifications the client was promised. If one of those pieces is weak, the problem is usually not just the phone app by itself. It is normally a mix of recorder setup, platform access, phone permissions, event linkage, and account handover.

What to check before adding the device

The recorder or camera is online locally and has the correct time and timezone.
The site has a stable path to the internet through the modem or router.
The platform access or cloud P2P setting can be enabled on the recorder and shows healthy status.
The installer knows whether the client needs one owner account first and then shared users, or whether the site is simple enough for one ordinary end-user account.
The phone has permission for notifications, background activity, mobile data, and local network access where required.

If those items have not been checked, the phone handover is usually guesswork. A device that is offline locally, on the wrong timezone, or blocked from the internet will often look like an app fault when the real fault is still at the recorder. SecurityWholesalers also has a shorter support article on this process at How can I set up remote viewing on a HiLook system? if you want the FAQ version alongside this guide.

Step-by-step online setup

Step 1: connect the recorder properly before touching the app

On most HiLook jobs, the NVR is the main device that should go online first. If the recorder is not healthy locally, the phone app is not the real issue yet.

Connect the recorder to the modem or router with an Ethernet cable.
Confirm the cameras are visible at the recorder.
Check live view on the local monitor.
Run a playback search by time and date so you know the recorder is saving footage properly.
Confirm the date, time, and timezone are correct before moving on.

Step 2: download the app and choose the correct region

Install the HiLookVision or Hik-Connect path used by that model family and firmware, then set it up on the phone that should genuinely own the system first.

Download the correct app from the Apple App Store or Google Play.
Open it and select the correct country or region.
Allow notifications and basic phone permissions when prompted.
If the wrong region is chosen, the recorder can be pointed at the wrong cloud path and the rest of the setup becomes messy very quickly.

Step 3: create the actual end-user account first

Register the account using the client email address or mobile number and make that the real owner account where possible.

Complete the verification code process by SMS or email.
Log in properly before trying to bind any device.
On a home, this is usually the main homeowner first.
On a business, it is usually the owner, manager, or site supervisor first.
Do not leave the whole system permanently tied to one installer login if the client is meant to own it later.

Step 4: enable platform access on the recorder and wait for online status

At the recorder, turn the cloud path on before scanning any QR code into the app.

Go to Configuration > Network > Advanced Settings > Platform Access on many HiLook and Hikvision-backed recorders.
Enable Hik-Connect or Cloud P2P, depending on what that recorder shows.
Apply the settings and wait for the status to show Online.
If it stays offline, stop there and check gateway, DNS, and the general internet path before doing anything else.
A common support step is to try DNS servers such as 8.8.8.8 and 8.8.4.4 if the recorder is reaching the network but not the platform service.

Step 5: create or note the verification code and then add the recorder

Once platform access is online, record the verification code properly and only then bind the recorder into the app.

Note the verification code exactly as shown if the recorder requires one.
Keep it with the site notes or handover paperwork.
In the app, add the device by QR code, serial number, or the correct brand binding path.
On most ordinary sites, add the recorder rather than each separate camera, because the user then gets one cleaner path for live view and playback across the whole site.

Step 6: confirm live view and playback on mobile data, not just on Wi-Fi

Do not stop at the point where the recorder merely appears in the app list.

Open live view and make sure the camera streams load properly.
Open playback and search by date and time.
Turn Wi-Fi off on the phone.
Repeat the same checks on mobile data.
If the app only works on local Wi-Fi, the remote-viewing handover is not finished yet.

Step 7: share access properly instead of passing around one password

Once the main owner account is working, then move to sharing.

Use the proper device-sharing or user-sharing path.
Give the owner account control first, then share to family members, reception staff, managers, or other users as needed.
This is cleaner than leaving everyone on one login, and it makes later changes easier if a phone is replaced or a staff member leaves.

Step 8: turn on notifications only after the event logic is working

Notifications are never just a phone setting. The recorder or camera has to be set up correctly first.

The event has to be enabled on the recorder or camera.
The schedule has to be correct.
The event must be linked to push.
The phone must allow notifications, mobile data, and background activity.
If the client only wants after-hours alerts from the rear gate or side path, test that exact condition rather than assuming push is working because the app shows live view.

Step 9: test the final workflow and leave the client with the right reference

Run one real test before leaving so the customer is not discovering the problem later on their own.

Walk through the front gate, cross the rear line after hours, or trigger the exact scene the customer wants to be notified about.
Confirm the phone receives the alert.
Confirm the app opens and playback can be found.
Then leave the client with the short support reference as well: How can I set up remote viewing on a HiLook system?.

Why notifications usually fail

Most notification complaints are not caused by the app store version alone. They usually come from one of five causes: the smart event rule was never properly enabled, the schedule is wrong, the event was not linked to push at the recorder or camera, the phone is blocking background activity, or the device is bound to the wrong account. That is why the better handover tests push events deliberately rather than assuming they will work because live view is online.

Sharing access without creating confusion

For homes and small businesses, it is better when each user has the right level of access instead of everyone sharing one admin login. That keeps the handover cleaner and makes later support easier if a phone is replaced, a staff member leaves, or a family member only needs viewing access. If the site is larger, document which account is the owner account and which logins are ordinary operators.

Worked Example

Home system that recorded perfectly but never sent alerts

Situation: The client could see live video on the app, so they assumed the phone setup was finished. Two weeks later they realised no-one had received a single after-hours alert from the driveway or side gate.

Solution used: The recorder event schedule was corrected, push linkage was enabled on the correct camera rules, and the phone battery restrictions were turned off for the app.

Why this was chosen: The real problem was not remote view. It was that the handover never tested a push event end to end. Once the recorder logic and phone permissions were both fixed, the app behaved normally.

Installation notes: The client was shown how to trigger a test event and how to recognise the difference between a network problem and an event-linkage problem later.

Worked Example

Small business with a new manager and a replaced internet service

Situation: The original installer login was still the only working account, the site internet had recently changed, and the new manager could not get playback on the app even though the recorder was still recording on site.

Solution used: The platform status on the recorder was confirmed, the device was rebound into the correct user handover path, and the new manager received their own clean account access.

Why this was chosen: The goal was not just to get one phone working again. It was to leave the site with a proper owner account and a cleaner long-term support path.

Installation notes: Playback, live view, and one real event were all tested before the handover was signed off, and the manager was told what to check first if the site ever changes modem or ISP again.

Common mistakes

Scanning the QR code before platform access is actually enabled and healthy.
Using one installer login forever instead of handing over proper user access.
Assuming live view means alerts are already configured.
Ignoring phone-level notification restrictions.
Replacing the app before checking recorder time, event linkage, or account binding.

When to ask for help

If the device shows offline, the QR handover is unclear, playback is unreliable, or notifications still do not work after basic phone-permission checks, take photos of the recorder network screen and the app error state before changing more settings. That usually saves time and prevents the original fault from being buried.

Relevant SecurityWholesalers pages

Frequently Asked Questions

What should a normal HiLook online handover include?
A proper HiLook handover should include local recorder health, the right owner account, platform access online, the recorder added correctly into the app, live view and playback tested on mobile data, and alerts tested properly if alerts were part of the brief.
Do I add the recorder or each camera to the app?
On most HiLook jobs the recorder is the better device to hand over, because it gives the user one clean path for live view and playback across the whole site.
Why are HiLook notifications often missing on the phone?
Usually because the event rule, push linkage, phone permission, or battery restrictions were not fully tested after the app was added.
Should a family or business share one admin login?
Usually no. Cleaner user sharing avoids confusion when phones change or access needs to be removed later.
Can the wrong timezone make the app feel broken?
Yes. The app may still connect, but playback and event review become confusing if the recorder clock is wrong.
What should I photograph before asking for support?
The recorder network screen, platform or cloud screen, QR label, and the exact app error or offline state on the phone.