ACCESSLocksmiths

Video intercoms · Dahua 2-wire field guide

The Dahua intercom app (DMSS): the easy resident setup

For the person who lives there, the whole system comes down to three taps: ring, answer, unlock. This is how to get them there.

Part 6 of 7 · By Gareth Barber, Owner & Head Locksmith, Access Locksmiths · Published 2026-10-05

The right app

For a Dahua villa intercom on iPhone or Android, the app is DMSS (Dahua Mobile Security Surveillance). The older iDMSS and gDMSS apps are retired.

There is a second app called DMSS VDP, meant for apartment building managers — not a single villa. Install DMSS. On the App Store the developer field may show an individual account name; judge by the app name and description, not the developer string.

Before you start (installer)

The door station must be Online in its cloud status, which means a working gateway and DNS (Part 1, step 5.4). No cloud path, no app.

Setup on the resident's phone

  1. Install DMSS.
  2. Me → Sign up with the resident's email, confirm, and log in. This account owns the door — keep the email and password safe.
  3. Home → + → SN/Scan and scan the door station's QR code, or tap Manually Enter SN and type the door station serial.
  4. Next → device type VTO → Next.
  5. Name it Gate, username admin, password = the door station password, then Save.
  6. Device Details → enable Alarm Subscription / Notifications.
  7. In the phone's own settings, allow DMSS notifications and Background App Refresh.

Adding by IP/Domain instead only works while the phone is on the same network. Use the serial number for access from anywhere.

The daily experience

The gate button rings the phone like a call. Tap Answer. Tap Unlock. That's it. Live View shows the gate on demand.

The door code is a separate job, set on the door station — see Part 3.

In Brisbane and would rather it was just done? Access Locksmiths installs, repairs and commissions video intercoms and access control of all makes, with a written handover. Call 0404 159 369 or get a quote by text.

Written from one real deployment. Client-identifying details have been removed; technical values are generic examples. Firmware and hardware generations differ — verify each step against your own models. Corrections are welcome and will be published with attribution.

← Part 5: RPC2 API — configuring a VTH with no web UI Part 7: Commissioning checklist & handover pack →
📞 Call nowBook online