Ajax Hikvision Integration: Adding CCTV to the Ajax App

An alarm that tells you a detector has gone off is useful; an alarm that lets you see what set it off from the same app is far more useful. This guide is for UK installers and informed end users who want an Ajax Hikvision integration: Hikvision cameras or a Hikvision NVR showing live in the Ajax app alongside the intruder alarm. It covers which Ajax hubs support it, the two connection methods (RTSP and the EZVIZ cloud route), step-by-step setup, the network work involved, user access, and the problems we see most often. Every limit quoted is linked to the Ajax or Hikvision page it comes from.

Ajax Hikvision integration showing Hikvision cameras and an NVR live in the Ajax app — One app for the alarm and the cameras: Ajax hub, Hikvision NVR and Hikvision IP cameras working together.

What this guide covers

What you get: live Hikvision video in the Ajax app next to arming, alarms and photo verification.
Hub limits: how many cameras each Ajax hub can hold, and why a recorder only uses one slot.
Two methods: RTSP links (Ajax’s recommended route) and the EZVIZ cloud integration.
Setup and network: the RTSP link format for Hikvision, port forwarding and static IP or DDNS.
Access and troubleshooting: who can view which camera, and fixes for the usual faults.

What does an Ajax Hikvision integration actually give you?

It puts live video from Hikvision cameras and recorders inside the Ajax app, so the user can check a camera within seconds of an alarm notification without switching apps. Ajax’s IP camera integration article describes live view from the stream icon, full screen by rotating the phone, pause with a still saved to the phone, and pinch-to-zoom.

What it is not is a replacement for the recorder. The Hikvision NVR still does the 24/7 recording, the AcuSense filtering and the evidence export; Ajax’s own Hikvision integration announcement advises using the official Hikvision or EZVIZ apps when you need to save video. The value of the integration is speed: alarm, look, decide. Pair it with an Ajax hub such as the Ajax Hub 2 Plus and the photo-verifying MotionCam detectors covered later, and the customer has two independent ways to check an event.

For installers this is also a selling point. A customer who already has Hikvision CCTV can add an Ajax alarm and keep their cameras, and a customer buying both gets one app to learn instead of two.

Which Ajax hubs support Hikvision cameras, and how many?

Every current Ajax hub supports third-party cameras, with limits that rise from 10 on the original Hub to 100 on Hub 2 Plus. Ajax’s IP camera integration article gives these per-hub figures for hubs running OS Malevich earlier than 2.42.111; on 2.42.111 or later, Ajax says to check the maximum with its video device calculator instead.

Ajax hub	Camera / stream limit (pre-2.42.111)	Typical job
Hub (2G) / Hub (4G)	Up to 10	Older installs being upgraded
Hub 2 (2G) / Hub 2 (4G)	Up to 25	Homes and small shops with a 4 or 8 channel NVR
Hub 2 Plus	Up to 100	Larger homes, offices, multi-unit sites
Superior Hub Hybrid 2 / Superior MegaHub	Up to 100	Grade-led commercial projects

The detail that matters on site is how the limit is counted. Ajax’s Hikvision and Safire connection article says a linked video recorder occupies one slot within the hub limit, while each individually linked camera takes a slot of its own. The Ajax camera connection FAQ makes the same point: adding a recorder lets you get around the device limit, and each of its cameras still appears separately in the app. On anything bigger than a handful of cameras, connect the NVR rather than the cameras one by one.

Before you start, update the hub to the latest OS Malevich in the Ajax PRO app; the firmware version changes how the limits are worked out. For help choosing between the two Hub 2 variants, see our Ajax Hub 2 vs Hub 2 Plus guide.

Should you connect by RTSP or through the EZVIZ cloud?

Use RTSP for trade installs: Ajax itself recommends connecting cameras and recorders by RTSP link, and it avoids a second cloud account. Ajax’s Hikvision and Safire article states that recommendation and adds that Ajax is not responsible for unstable operation of devices connected through the cloud route, because it relies on a third-party SDK.

Point	RTSP link	EZVIZ cloud integration
How video travels	Direct from the camera or NVR to the app	Camera or NVR to the EZVIZ cloud, then to the Ajax app via the maker’s SDK
Accounts needed	Camera or NVR username and password	A separate EZVIZ account (Hik-Connect logins do not work)
Network work	Port forwarding plus static IP or DDNS for remote viewing	No port forwarding
Brands	Any IP camera that supports RTSP	EZVIZ, Hikvision and Safire
Ajax’s view	Recommended	Supported, but Ajax does not guarantee stability

The EZVIZ route suits a homeowner who cannot open ports on their router. For anything you are signing off and supporting, RTSP gives you fewer moving parts.

How do you add a Hikvision camera or NVR to Ajax over RTSP?

Build the Hikvision RTSP link, then in the Ajax app go to Devices, Add camera, choose RTSP camera, and paste the link with a name and room. The steps below follow Ajax’s IP camera integration article.

Set a static local IP on the camera or NVR. Reserve the address on the router or set it on the device, so the link does not break after a power cut.
Build the link. Hikvision’s own RTSP format article gives rtsp://username:password@IP-address:port/Streaming/Channels/101 for the main stream of channel 1, and 102 for the sub-stream.
Work out the channel number. Ajax’s worked Hikvision example uses port 554 and explains that, through a recorder, the first digit is the camera number and the last digit is the stream, so 201 is the first stream of the second camera.
Test the link first. Open it in a desktop media player on the same network. If it will not play there, it will not play in Ajax.
Add it in the app. Devices, then Add camera (on iOS, Add device then Add camera), then RTSP camera. Enter the name, link and room, and save. Each stream appears as its own camera.

For phone viewing on mobile data, the sub-stream (102, 202 and so on) is usually the better choice: it is lighter and loads faster on a weak signal. Create a dedicated, view-only user on the Hikvision NVR for the RTSP links rather than using the admin password, so that changing the admin password later does not break the integration.

This works with any current Hikvision recorder. On a small job, a DS-7604NXI-K1/4P(E) 4-channel PoE AcuSense NVR or DS-7608NXI-K1/8P(E) 8-channel NVR keeps the cabling simple, and a DS-7608NXI-K1/8P/VPRO AcuSeek NVR adds Hikvision’s natural-language search for finding the clip afterwards.

Ajax Hikvision integration architecture comparing RTSP and EZVIZ cloud connection routes — RTSP direct, EZVIZ cloud, or a whole NVR in one slot: three ways to bring Hikvision video into Ajax.

How do you add Hikvision cameras through the EZVIZ integration?

Log in to an EZVIZ account from the Ajax app, then add the camera or recorder from the list it shows. Ajax’s Hikvision and Safire connection article sets out the sequence.

Get the device onto EZVIZ. The camera or NVR must be added to an EZVIZ account by following the maker’s instructions. Ajax states that a device connected only to Hik-Connect must also be connected to an EZVIZ account, that Hik-Connect logins do not work for EZVIZ, and that the two accounts need different email addresses.
Link the account in Ajax. In the Ajax app, open the menu, then Video Surveillance, choose Hikvision, and sign in to the EZVIZ account.
Add the device. On the Devices tab, Add Device, then Add Camera, then Hikvision. Give it a name and room, and pick the camera or recorder from the list.
Enter the verification code. If the device has a password set, enter it as the verification code, then tap Add.

Ajax notes in its integration announcement that the EZVIZ passwords and video streams are encrypted and not stored by Ajax. Even so, a second cloud account is one more thing for the customer to look after, which is why we default to RTSP on trade jobs.

What network setup does the RTSP route need?

To view RTSP cameras away from the site, you need a reachable public address (static IP or DDNS) and a forwarded port for each camera or recorder. Ajax’s IP camera article recommends a permanent IP address, offers DDNS as the alternative and supports UPnP as an option.

Ports: Ajax notes that IP cameras use port 554 by default but this can differ by manufacturer, and lists ports it does not recommend forwarding, including 80, 443, 3389 and 5900.
One port per device: each camera you link directly needs its own forwarded external port. Linking the NVR instead means one forward covers every channel.
Router: a business-grade router such as the Reyee RG-EG105G-P-V3 cloud PoE gateway makes port forwarding and address reservations straightforward, and a Reyee RG-ES206GS-P smart PoE switch powers the cameras on a small site.
Security: use strong, unique passwords, keep the Hikvision firmware current, and never forward the NVR’s web interface port just to make RTSP work.

One useful behaviour: Ajax says RTSP cameras operate independently of the hub, so if the hub loses its connection to the Ajax Cloud but the cameras or recorder are still running, the streams remain viewable in the app. For a wider look at off-site viewing options, see our remote CCTV monitoring guide.

Who can see the cameras? Setting privacy and access

Camera access is controlled per user in the Ajax app’s privacy settings, so you decide which users, installers and companies can see each camera. Ajax’s IP camera article lists permissions for watching the livestream, viewing and downloading from the archive, watching with sound and PTZ control, each available at any time or only while the system is armed.

The armed-only option is the one to discuss with domestic customers. Indoor cameras that family members can view only while the alarm is set are much easier to live with and keep camera use proportionate to the job. In commercial premises, give staff the cameras they need and nothing more, and document who has access. Remove your own installer access to camera streams at handover unless the maintenance contract needs it.

Can Ajax video scenarios record Hikvision footage?

Not as documented: Ajax’s video scenarios page describes scenarios that need a detector and an Ajax NVR or Ajax camera in the space. The Ajax video scenarios manual covers recording triggered by alarms, with an actuating window of 5 seconds to 60 minutes when all selected devices must trigger, and recording either always or only when the cameras are armed. It does not say Hikvision or RTSP cameras can be used.

So on a Hikvision site, plan it this way. Let the Hikvision NVR record continuously or on its own AcuSense events, and use the Ajax app for live checks after an alarm. Where the customer or the monitoring centre needs a picture tied to the alarm itself, fit Ajax photo-verifying detectors such as the MotionCam U or MotionCam U (PhOD) with photo on demand; our MotionCam photo verification guide explains the options.

What kit makes a good Ajax plus Hikvision build?

A Hub 2 or Hub 2 Plus, a Hikvision AcuSense NVR and cameras, and a mix of Ajax detectors covers most UK homes and small businesses. These are example builds rather than a specification; size them to the site survey.

Part	Home or small shop	Office or larger site
Ajax hub	Hub 2 (4G)	Hub 2 Plus
Hikvision recorder	DS-7604NXI-K1/4P(E)	DS-7608NXI-K1/8P/VPRO
Cameras	DS-2CD2347G3-LIS2UY/SL turrets	DS-2CD2386G2H-IS2U/SL 8MP turrets
Detection	MotionProtect U and DoorProtect Plus U	MotionCam U plus MotionProtect U
Control and sounders	KeyPad Plus and StreetSiren DoubleDeck	KeyPad Plus and StreetSiren DoubleDeck
Range and network	Reyee gateway	ReX 2 plus Reyee gateway and PoE switch

Where a camera has to go somewhere with no data cable, a Wi-Fi model such as the DS-2CD2443G2-IW cube camera can be linked over RTSP in the same way, provided the Wi-Fi signal is solid. For the alarm side of the design, start with our Ajax wireless alarm system guide.

Four-step Ajax Hikvision integration workflow from RTSP link to user access — Static IP, RTSP link, add in Ajax, set access: the four-step integration workflow.

Why will a Hikvision camera not show in the Ajax app?

Most failures come down to a wrong RTSP link, a missing port forward, or the camera limit on the hub. Work through this table before replacing anything.

Symptom	Likely cause	Fix
Works on site Wi-Fi, not on 4G	No port forward or public address	Forward the RTSP port and use the static IP or DDNS name in the link
Never plays anywhere	Typo in the link or wrong channel number	Test the link in a desktop player; check 101, 201 and so on
Stopped after a password change	Credentials in the link are out of date	Use a dedicated view-only NVR user and edit the link in Ajax
Cannot add more cameras	Hub limit reached	Link the NVR (one slot) or move to Hub 2 Plus
Slow to load or buffering	Main stream on a weak mobile signal	Link the sub-stream (102) for phone viewing
EZVIZ login rejected	Hik-Connect credentials used	Create a separate EZVIZ account with a different email

For handing the customer a working Hikvision app setup alongside Ajax, our Hik-Connect installer setup and handover guide covers the Hikvision side.

Frequently asked questions

Can I view Hikvision cameras in the Ajax app?

Yes. Ajax supports any IP camera with RTSP, and has a dedicated integration for EZVIZ, Hikvision and Safire devices through an EZVIZ account. Live view, pause, stills and zoom work in the Ajax app.

Does connecting a Hikvision NVR use up the camera limit?

Ajax says a linked recorder occupies one slot in the hub limit, while each individually linked camera takes its own slot. On anything more than a few cameras, link the NVR.

Can I use my Hik-Connect login in Ajax?

No. Ajax states that Hik-Connect logins do not work for the EZVIZ service, so the cloud route needs a separate EZVIZ account. The RTSP route needs only the camera or NVR username and password.

Does the Ajax app record Hikvision footage?

Keep the Hikvision NVR as the recorder. Ajax recommends the official Hikvision or EZVIZ apps when you need to save video, and its video scenarios documentation covers Ajax NVRs and cameras.

Which Ajax hub should I fit for a Hikvision site?

Hub 2 handles up to 25 cameras or streams and Hub 2 Plus up to 100 on firmware before OS Malevich 2.42.111, according to Ajax. On newer firmware, check with Ajax’s video device calculator.

Will the cameras still work if the Ajax hub goes offline?

Ajax says RTSP cameras operate independently of the hub, so if the hub loses its cloud connection but the cameras or recorder are still running, the streams stay viewable in the app.

Related guides

Order Ajax and Hikvision from Netview

Netview is a Leicester-based authorised Hikvision wholesaler and Ajax stockist with same-day dispatch on stocked lines. Browse the Ajax hubs, detectors and Hikvision recorders and cameras in this guide, check live trade stock and order online at netviewcctv.co.uk.

November 13, 2026 | View: 6 | By: netviewcctv.co.uk