Support
How to Add a Dahua NVR to DMSS
App and Remote Viewing Support
Summary
Use this page when a Dahua recorder or NVR needs to be added into DMSS properly, including owner account setup, cloud binding, playback testing and shared-user handover.
Applies to
- Dahua NVRs
- Dahua recorders with app or cloud support
- Dahua sites using DMSS
Difficulty and time
Difficulty: Moderate
Estimated time: 15 to 30 minutes when the recorder is already online locally
What you will need
- Recorder local admin password
- Phone with the correct mobile app
- Access to a monitor and mouse on the recorder
- Working internet connection on site
- Verification code or device password where required
What this guide covers
- What to check before you start
- The clean setup order
- Common mistakes that break remote viewing
- Troubleshooting offline or binding issues
- When support should step in
Dahua app setup usually goes wrong when the phone app is treated as the first step. In practice, the recorder, the router path, the device status and the account ownership all matter before the QR code is scanned.
This page is written for owners, installers and handover staff who want a cleaner outcome. It focuses on the order that tends to save time: local recorder first, network path second, account ownership third, app binding fourth, and notifications last.
If the site has already changed routers, internet providers, device passwords or owner accounts, slow down and confirm those basics before you try to add the device again.
Before you start
Gather the basics before you open the app. It is much easier to solve binding issues when the local recorder path has already been checked.
- Confirm you are dealing with the correct owner account, not a temporary installer login.
- Make sure the recorder date, time and timezone are correct.
- Have the router connection working before you touch cloud setup.
- Keep the recorder model and serial number handy in case support is needed.
Do not keep rebinding the device between random accounts
If the recorder is already bound to a different user account, repeated attempts from other phones usually create more confusion, not less.
Confirm who owns the device in the cloud path before you remove, re-add or reset anything.
What usually causes this
- The recorder was never properly online before the app setup started.
- The wrong owner account was used and no one recorded who actually owns the device.
- The verification code, device password or binding path was entered incorrectly.
- Notifications were tested before live view, playback and event logic were proven locally.
Step 1: Confirm the recorder is working on site
Before you open DMSS, make sure the Dahua NVR is already recording locally on a monitor and mouse. If the recorder is not stable on site, the app setup usually becomes confusing very quickly.
- Check that cameras are visible on the local screen.
- Confirm the recorder time and date are correct.
- Make sure the recorder has a working connection to the router.
- Record the device model, serial number and current admin password.
Step 2: Create or confirm the correct DMSS owner account
The first account should usually belong to the real site owner or the person who will manage the system long term. Avoid setting the whole site up under a temporary installer phone unless there is a clear handover plan.
- Install DMSS on the owner's phone.
- Confirm the region and mobile number or email path are correct.
- Complete any verification email or SMS steps before you add the device.
- Write down which account is the owner account so later sharing is clean.
Step 3: Enable the cloud or P2P path on the recorder
At the recorder, go to Network > P2P and enable the cloud service. Do not rush past this screen. The device needs the right gateway, DNS and internet path before the app can bind it reliably.
- Check the gateway matches the router address on site.
- Check DNS is populated. Public DNS such as 8.8.8.8 and 8.8.4.4 can be a useful test where appropriate.
- Wait for the platform or P2P status to show online before continuing.
- Record any verification code or binding code shown on screen.
Step 4: Add the Dahua device into DMSS
Once the recorder is online, bind it through the app using the QR code, serial number, or the correct owner-account flow for that brand. Most support issues happen when people try to scan first and troubleshoot the network later.
- Use the app scan function with the recorder QR code where available.
- Enter the device verification code or device password carefully.
- Give the device a clear site name so it can be recognised later.
- If the device says already bound, stop and confirm which account owns it.
Step 5: Confirm live view and playback before alerts
The first success point is not the push notification. It is stable live view and usable playback in DMSS. If that part is unreliable, notification setup usually wastes time.
- Open live view and confirm all required channels load.
- Test playback from the app for a recent time range.
- Turn Wi-Fi off and test again on mobile data.
- Only after that should you move to event or push-notification testing.
Step 6: Share access and finish the handover
The owner account should normally keep control of the device and then share access to family members, staff or managers as required. That is cleaner than putting everyone on one login.
- Share only the access each user actually needs.
- Confirm whether the shared user needs live view only or playback as well.
- Test at least one real event if alerts are part of the handover.
- Note the owner account, device password and verification code in the site records.
Small office handover after install
Situation: A new office fit-out has a single NVR and the owner wants remote access for herself and one manager.
Solution used: The installer added the recorder to the owner account first, tested live view on mobile data, then shared access to the manager account rather than giving out the owner login.
Why this was chosen: That kept the ownership path clean and made later password recovery easier.
Installation notes: Notifications were tested only after the recording and event schedules were confirmed locally.
Common mistakes
- Trying to scan the QR code before platform access or P2P shows online.
- Using the wrong owner account and then forgetting who actually owns the device.
- Turning on notifications before live view and playback have been proven.
- Entering the verification code, serial number or device password from memory instead of reading it directly from the recorder.
- Assuming Wi-Fi testing is enough and skipping a mobile-data test.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| Device will not add to the app | Cloud or P2P status, verification code, device password, existing account binding | Confirm the recorder is online locally first, then recheck the code and whether the device is already owned by another account. |
| Device shows offline | Gateway, DNS, router path, platform access or P2P status | Fix the local internet path on the recorder before retrying the app. |
| Live view works on site Wi-Fi only | Mobile-data test, router path, app permissions | Test away from the site Wi-Fi and confirm the device really is bound through the cloud path, not just visible on the LAN. |
| Shared user cannot see cameras | Sharing permissions, wrong user account, owner account confusion | Check what permissions were granted and whether the user logged into the correct app account. |
| Notifications do not arrive | Event setup, push permissions, phone settings, cloud status | Test the event at recorder level first, then confirm app push permissions and phone notification settings. |
When to contact support
Contact SecurityWholesalers support when the recorder is online locally but still refuses to bind, or when the device appears to be owned by an unknown account after a legitimate ownership change.
Include the order number, product model, serial number, screenshots of the cloud or platform status page, and a short note explaining what you already tested.
Related support guides
- Dahua Support Guides - Go back to the brand support hub.
- Tech Support Guides - Browse the full support section.
Related buying guides
- Dahua Buying Guide - Broader buying and system-planning advice for this brand.
- CCTV Buying Guide - General camera, recorder and storage planning help.
- NVR Buying Guide - Useful if the app problem is really a recorder-selection or system-design issue.
Relevant product categories
- Dahua CCTV Products - Relevant products and replacement hardware.
- CCTV Products - General CCTV category if the site is mixed-brand.
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
-
How do I add a Dahua NVR to DMSS?
The normal order is to confirm the recorder works locally, create the correct owner account, enable the cloud or P2P service, wait for online status, then add the device by QR code or serial and test live view before notifications.
-
Why will the Dahua recorder not add to DMSS?
Usually because the recorder is not truly online, the verification code or device password was entered incorrectly, the wrong account is being used, or the device is already bound to another user.
-
Should I add the recorder or each camera?
On most NVR-based sites the recorder is the cleaner device to add because it keeps all cameras, playback and user sharing in one place.
-
Why should the owner account be set up first?
Because the owner account usually controls future sharing, account recovery and long-term handover. Fixing a bad ownership path later can take more time than doing it properly at the start.
-
Should notifications be turned on straight away?
Not until live view, playback and the event logic have already been tested. Otherwise customers often chase app alerts when the real issue is the event setup on the recorder or camera.