Remote viewing is the feature that sells systems and the one handed over with the least care. In most installations we inspect, the app works, and every default that should have been changed is still set to whatever it shipped with.
The convenience is real. So is the exposure, because a camera reachable from your phone is by definition reachable from outside your house.
How remote viewing actually works
Almost all modern recorders use a manufacturer cloud relay: the recorder makes an outbound connection to the vendor’s service, your app connects to the same service, and the two are introduced. You scan a QR code and it works. Nothing needs to be opened on your router.
The older method — port forwarding — exposes the recorder directly to the internet on a chosen port. It is faster and it is far riskier, because your recorder is then discoverable by anyone scanning that range, and recorder firmware is not built to be a front-line internet service.
If your installer set up port forwarding, ask why. There are legitimate reasons on a commercial site with a static address and a firewall in front. On a house, the cloud relay is almost always the right answer.
The five things to change on day one
- The admin password. Not the app password — the recorder’s own admin login, which is frequently left as the factory default or as something the installer uses across every site. Change it and write it down somewhere you will still have in three years.
- Your own user account. Do not use admin for daily viewing. Create a separate user with view-only rights, so a compromised phone cannot reconfigure or wipe the system.
- Remove the installer’s access, or agree explicitly that it stays for support. Either is fine; not knowing which is not.
- Turn off UPnP on the recorder unless you know you need it. It can open router ports automatically, which quietly undoes the safety of using the cloud relay.
- Update the firmware once, at handover. Recorders often ship with firmware a year or more old, and the gap usually includes security fixes.
None of this takes more than twenty minutes and it should be part of handover rather than something you discover later.
Why your app is slow, and what fixes it
Two different bottlenecks get blamed on the app.
Your upload speed. Video leaving your house travels on your connection’s upload, which on most Indian home broadband is a fraction of the download figure that gets advertised. Four cameras at full resolution can exceed it comfortably. The fix is not a better app: it is viewing the sub-stream.
Sub-stream versus main stream. Recorders keep two versions of each feed — a high-resolution main stream for recording and a low-resolution sub-stream for remote viewing. If your app is set to main stream, every camera you open fights your upload. Set the app to sub-stream for live grids and switch to main stream only when you need detail on one camera. This one setting resolves most complaints about lag.
What remote access does not give you
- It is not a backup. Footage lives on the recorder. If the recorder is stolen or its disk fails, the app shows you nothing, however faithfully it worked yesterday.
- It is not monitoring. Nobody, including you, watches a live grid. Notifications help, but they are triggers to look, not surveillance.
- It does not survive a power cut unless the recorder, cameras, switch and router are all on backup. Local recording is the part worth protecting first.
- Cloud relay is not cloud storage. The vendor service introduces your phone to your recorder; in the standard configuration it does not keep a copy of anything.
Who should have access, and how to remove it
Decide the list deliberately, and keep it short. For a household, that is usually two adults with view-only accounts and one admin credential stored securely rather than on a phone.
The part people skip is removal. Access granted to a domestic helper, a tenant, a contractor or a family member who has since moved out tends to persist for years because nobody wrote down that it existed. Keep a note of every account created and review it annually — the same discipline that makes access control work on a building applies to your camera app.
If you inherit a system from a previous owner or a previous installer, assume unknown accounts exist and audit the user list before you rely on it.
Common questions
Can my installer see my cameras after handover?
If their account still exists, yes. That is not necessarily wrong - it is how remote support works - but it should be a decision you made rather than something you discover. Ask for the user list at handover and confirm which accounts are yours, which belong to the installer, and how to remove the latter.
Is port forwarding dangerous?
It is materially riskier than the cloud relay on a home connection, because it exposes the recorder directly to internet scanning. If your setup uses it, ask whether the cloud option would work instead. Where port forwarding is genuinely required, it belongs behind a firewall with restricted source addresses, not open to everyone.
Why can I view at home but not on mobile data?
Usually the app is connecting on the local network only, and the cloud registration was never completed. Check that the recorder shows its cloud status as online and that the QR pairing was done. It is a configuration step, not a fault, and it is commonly missed when an installer tests only on site.