Why is Dahua DMSS not connecting to my recorder?

Usually because the recorder is offline, the P2P status is not healthy, the wrong device has been added, or the account binding history is confused.

Why did DMSS stop working after an internet change?

Often because the recorder network settings, DNS, or P2P state changed when the modem or router changed.

Why am I not receiving notifications in DMSS?

Often because push permissions, event linkage, or phone-level notification permissions are not configured properly.

Should I remove and re-add the device in DMSS?

Sometimes yes, but only after checking that the recorder or camera is healthy locally. Re-adding the device will not fix a recorder that is already offline.

Can DMSS problems be caused by the phone rather than the NVR?

Yes. Battery optimisation, background restrictions, and notification permissions on the phone can all affect DMSS behaviour.

Which related page helps after this one?

Usually the camera-not-showing page or the notifications-not-working page, depending on whether the problem is device visibility or push alerts.

What should I record before changing any settings?

For Dahua CCTV Buying Guide, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.

Should I factory-reset the equipment while troubleshooting?

Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.

Support

Dahua DMSS Setup and Troubleshooting

Most DMSS problems are not really app problems in isolation. They are usually a mix of device binding, P2P status, recorder settings, phone permissions, and network conditions. That is why replacing the app rarely fixes the real issue.

App Support

Dahua DMSS troubleshooting concept showing cameras, NVR, router and phone access — When DMSS misbehaves, check the path in order: camera or NVR health, recorder network status, router or internet changes, account binding, then phone permissions.

What DMSS should do on a normal site

Show live view from the recorder or camera.
Allow playback of recorded footage where the device supports it.
Deliver alarm or event notifications when the device and phone are configured correctly.
Give the owner a simple way to review the system without logging into the NVR every time.

The first checks when DMSS will not behave

Confirm the camera or NVR is actually online locally before testing the app.
Confirm the device P2P or cloud status is online in the recorder or camera settings.
Confirm the correct device has been added to DMSS and is not bound to a different user account.
Confirm the phone still has notification permission, background activity permission, and network access allowed for DMSS.

Sample scenarios

Example: a butcher shop changes internet provider and suddenly DMSS live view fails. The cameras are still recording locally. In that case the issue is often recorder network settings, P2P status, or DNS rather than the cameras themselves.

Example: a warehouse manager receives no push alerts after replacing their phone. The NVR is online and the camera analytics are working. The fault is often DMSS notification permissions or the device not being re-added or rebound properly to the new phone session.

What usually fixes DMSS problems

Checking whether the recorder is online before touching the app.
Refreshing the device addition in DMSS if the account or binding history is unclear.
Checking push configuration and event linkage at the recorder or camera.
Checking phone-level permissions and battery optimisation settings.

Relevant SecurityWholesalers Categories and Products

These Dahua categories are relevant because DMSS is most often being used with Dahua cameras, NVRs, and small-business systems.

Dahua NVRs - DMSS most often fronts a Dahua recorder on small-business and commercial sites.
Dahua CCTV cameras and kits - The main Dahua camera and kit category for users who are setting up a new DMSS site.

Sources and Further Reading

Step 1: Record the exact starting condition

Before changing Dahua CCTV Buying Guide, reproduce one clear test and write down the affected device, channel or user, the exact error wording, and the last time it worked.

Photograph the current status or error.
Record the exact model and firmware or app version.
Note what changed immediately before the fault.
Protect recordings, account ownership and the current configuration.

Step 2: Follow the local path described above

Use the recorder, controller or device screen named in this guide before treating the phone app as the cause. Record the status you find before editing it.

Start at the local device where possible.
Use the exact channel, door, zone or user involved.
Compare it with one working equivalent.
Change one setting at a time.

Step 3: Correct the proven layer only

Keep power, cabling, storage, network, account and app checks separate. Correct only the layer that failed the controlled comparison.

Resolve physical power or cabling before software.
Prove local operation before remote access.
Keep owner and shared-user permissions separate.
Avoid reset, format or unbind options unless a backup and recovery plan exist.

Step 4: Repeat the original test and document it

Repeat the same test, then verify any local and remote outcomes separately. A saved setting or online icon is not enough on its own.

Record the successful test time.
Check the expected log, playback or hardware response.
Restart only when it is a safe and relevant proof.
Save the final screenshot with the site handover record.

Troubleshooting table

Symptom	What to check	What to do next
The local device also fails	Power, cable, storage or local configuration	Keep the test local and resolve the first failed layer before changing app or cloud settings.
Local operation works but the app fails	Ownership, sharing permission, cloud status or remote network	Keep the proven local setup and compare owner versus shared-user access on mobile data.
Only one channel, zone, door or user fails	Item-specific schedule, permission, wiring or assignment	Compare it side by side with one working item and change only the meaningful difference.
The fault started after another change	Router, password, firmware, account, power or configuration change	Document the last known working state and reverse only the relevant change where safe.
The fault is intermittent	Exact time, logs, signal, load, power and environmental pattern	Capture failure times and screenshots so support can correlate the event instead of guessing.

When to contact support

Contact SecurityWholesalers support when the local result, exact model, firmware or app version and one controlled test are documented but the fault remains. Send the order number if available, screenshots, exact failure time and the checks already completed.

Before you start

Record the exact model, version, error wording, affected item and last known working time. Photograph the current state and protect recordings, configuration and account ownership before making changes.

Common mistakes

Changing several unrelated settings before repeating the original test.
Skipping the local device check and relying only on an app symptom.
Resetting, formatting or unbinding equipment without a backup and ownership record.
Escalating without the exact model, version, error text and test time.

Worked example

Compare one failing path with one working path

Situation: One device, channel or user failed while another comparable item still worked.

Solution used: The two paths were compared at the local device first, one meaningful difference was corrected, and the original test was repeated.

Why this was chosen: The comparison isolated the affected layer without disturbing the rest of the system.

Installation notes: The final status, screenshot and test time were added to the handover record.

Important

Protect the working system before continuing

Do not reset, disconnect, format or overwrite a working path until its current settings, ownership and required evidence have been recorded.

Related support guides

All Technical Support Guides - Find the matching brand, app, recording, network, alarm, intercom or access-control guide.

Related buying guides

SecurityWholesalers Buying Guides - Check compatibility and system-design guidance.
Full Store Directory - Find the relevant product family.

Frequently asked questions

Why is Dahua DMSS not connecting to my recorder?
Usually because the recorder is offline, the P2P status is not healthy, the wrong device has been added, or the account binding history is confused.
Why did DMSS stop working after an internet change?
Often because the recorder network settings, DNS, or P2P state changed when the modem or router changed.
Why am I not receiving notifications in DMSS?
Often because push permissions, event linkage, or phone-level notification permissions are not configured properly.
Should I remove and re-add the device in DMSS?
Sometimes yes, but only after checking that the recorder or camera is healthy locally. Re-adding the device will not fix a recorder that is already offline.
Can DMSS problems be caused by the phone rather than the NVR?
Yes. Battery optimisation, background restrictions, and notification permissions on the phone can all affect DMSS behaviour.
Which related page helps after this one?
Usually the camera-not-showing page or the notifications-not-working page, depending on whether the problem is device visibility or push alerts.
What should I record before changing any settings?
For Dahua CCTV Buying Guide, record the exact model, firmware if known, current status, precise error wording, screenshots and the last known working condition. Change one item at a time.
Should I factory-reset the equipment while troubleshooting?
Not as an early step. A reset can erase network, recording, user, account or integration settings. Use it only with a configuration backup, known credentials and a model-specific recovery plan.