A modern IP camera is a small computer with a network port. It can tell you its name, list its video streams, hand you a live video URL, and accept a command to pan left. All of that is standardised in ONVIF, an open industry specification supported by camera makers across the price range.
The practical consequence is that a standards-based app can control a camera from almost any brand in exactly the same way. Remote97 is built on that idea: it discovers the camera, authenticates with the username and password you already set on the camera, and pulls the video directly from the device on your own network. There is no relay server in between, and no account to create.
Two ways to add a camera
1. Automatic discovery (WS-Discovery)
When you open the device scan, Remote97 sends an ONVIF WS-Discovery Probe as a UDP multicast to 239.255.255.250:3702, announcing it is looking for a NetworkVideoTransmitter. Cameras that speak ONVIF answer with a ProbeMatches message containing an XAddrs field — the URL of their device service, typically something like http://192.168.1.64/onvif/device_service.
The app then verifies each candidate before calling it "supported". This matters more than it sounds: plenty of consumer cameras answer the discovery probe but have no ONVIF service at all. Remote97 classifies by the response body, not just the HTTP status code. A SOAP authentication fault means "real ONVIF camera, you just need credentials"; an HTML login page means "ONVIF probably disabled — check the camera's admin page". A non-ONVIF device is not quietly added as a broken camera.
2. Manual add by IP
If multicast does not cross your network — a VPN, a managed switch, or a router with multicast filtering — add the camera manually. You enter the host/IP, port, username, password, and whether to use TLS. The app probes the usual device-service paths (/onvif/device_service, /onvif/device, /, /onvif/Device) and keeps the one that returns a valid capabilities document.
Enable ONVIF on the camera
Open the camera's web admin page, turn ONVIF on, and create a dedicated ONVIF user. Give it administrator or operator rights if you want PTZ control.
Put the phone on the same network
Same WiFi or Ethernet subnet as the camera. This is a local-control app by design.
Scan, or add by IP
Use auto-discovery, or choose the camera category and enter the address manually.
Enter credentials and test
The app runs a real authenticated request before it will save the device. A wrong password is reported as an authentication error, not silently accepted.
Name it and assign a room
Once saved, the camera appears on the home screen with a live thumbnail and in its room's device list.
Why credentials are checked properly
ONVIF authenticates each SOAP request with a WS-Security UsernameToken: a username, a nonce, a UTC creation timestamp, and a password digest computed as Base64(SHA1(nonce + created + password)). There is no "login" session — every request carries its own proof.
There is a subtlety that trips up a lot of clients. ONVIF defines two commands as pre-authentication — GetCapabilities and GetSystemDateAndTime — which a camera must answer even with bad credentials. A client that only calls those will happily declare "connected" while every later command fails. Remote97 therefore verifies credentials with a command outside that whitelist (GetDeviceInformation) before it considers the camera online.
The two failure modes are kept distinct, because the fix is different:
| Response | Meaning | What to do |
|---|---|---|
401 / NotAuthorized | Wrong username or password | Edit the credentials on the device — there is a button for it on the detail page |
403 / AccessDenied | Account exists but lacks permission | Use an Administrator or Operator account on the camera |
| Timeout / connection refused | Camera offline or unreachable | Check power, IP and subnet |
ONVIF accounts have three levels — Administrator (everything, including user management), Operator (PTZ and control) and User (read-only). Remote97 detects the level after connecting and shows a badge on the detail page. With a read-only or anonymous account, PTZ, imaging and relay controls are disabled rather than failing one by one when you press them. If someone later changes the camera password, the home row shows "re-authentication required" instead of a vague "offline".
Live view: what actually happens
After authenticating, the app asks the camera for its capabilities and then its media profiles. GetProfiles returns the available streams; Remote97 picks the highest-resolution profile as the main stream and the lowest as the sub stream. Both Media and Media2 services are queried, because some cameras only advertise their H.265 profile through Media2.
For each profile, GetStreamUri returns an RTSP URL (commonly on port 554). That URL — not the snapshot URL — is the real video. Remote97 plays it with an embedded player that handles H.264 and H.265, injecting the camera credentials into the stream URL so RTSP's own Basic/Digest challenge is satisfied. The app does not hardcode any manufacturer's URL pattern: whatever standard-compliant address the camera returns is used.
If the stream cannot be opened, or no first frame arrives within about ten seconds, the app falls back to a JPEG snapshot via GetSnapshotUri and labels it clearly as a still image. You never stare at a black rectangle wondering whether it is broken.
| Where | Which stream | Why |
|---|---|---|
| Home screen thumbnail | Sub stream (or snapshot) | Low bandwidth; many cameras allow only a few concurrent RTSP sessions |
| Camera wall / multi-camera view | Sub stream | Keeps a wall of cameras from saturating the network |
| Device detail page | Main stream, switchable | Full quality when you are looking at one camera |
| Fullscreen | Main stream, switchable | Full quality with a main/sub switch and PTZ overlay |
Streams are pre-warmed when the home screen opens so the first frame appears quickly, and live decoding stops when the app goes to the background. The number of simultaneous warmed cameras is capped.
Controlling the camera
Every control below is only shown if the camera actually advertises the corresponding service. A fixed camera will not get a fake PTZ pad.
- Pan / tilt / zoom — press-and-hold on a direction pad sends
PTZ:ContinuousMovewith a normalised velocity, and releasing sendsPTZ:Stop. Short taps from a remote key map to brief timed pulses with an automatic stop. - Presets — save the current position, jump to a saved preset, or delete one (
SetPreset/GotoPreset/RemovePreset). - Imaging — brightness, contrast, saturation and sharpness sliders, where the camera exposes an Imaging service. Values are normalised 0–1 as the spec requires.
- Relay outputs — switch relay outputs on and off where the camera exposes DeviceIO.
- Fullscreen and controls — a fullscreen view with main/sub switching, a PTZ overlay, and the option to show or hide the camera name.
- Control panels — a live camera widget can be placed on a custom control panel, with a chosen camera and stream, resized on the canvas.
The technical summary
| Function | Protocol / call | Typical port |
|---|---|---|
| Discovery | WS-Discovery Probe (UDP multicast 239.255.255.250) | 3702 |
| Device service | SOAP over HTTP(S), GetCapabilities, GetDeviceInformation | 80 / 443 / 8443 |
| Authentication | WS-Security UsernameToken (PasswordDigest, SHA-1 + Base64) | same |
| Profiles & capabilities | GetProfiles, GetServices (Media and Media2) | same |
| Live video | GetStreamUri → RTSP / RTP, H.264 or H.265 | 554 |
| Still fallback | GetSnapshotUri → HTTP JPEG | 80 |
| PTZ | ContinuousMove, Stop, GotoPreset, SetPreset, RemovePreset | same device service |
| Imaging / relays | Get/SetImagingSettings, GetRelayOutputs, SetRelayOutputState | same device service |
| Keep-alive | lightweight GetDeviceInformation polls | same device service |
Ports are manufacturer defaults. ONVIF device-service paths and XML namespace prefixes vary between vendors; the app matches XML by local element name and tolerates both singular and plural collection names.
Troubleshooting
The camera is not found
Check that ONVIF is enabled in the camera's own admin page and that an ONVIF user exists. Confirm the phone and camera are on the same subnet. If a VPN or virtual network adapter is active on the phone, multicast may be routed into the tunnel instead of the LAN — turning it off, or adding the camera by IP, solves it. Remember that some consumer cameras reply to the discovery probe while having no ONVIF service; those show as "suspected" with a hint to enable ONVIF.
Authentication failed
Use the ONVIF username and password created in the camera's admin page — the web-interface admin login is not necessarily the same account. If the camera allows anonymous access, Remote97 tells you so rather than pretending your password was validated. If the password was changed after the camera was added, use "edit credentials" on the detail page; the app reconnects with the new value.
PTZ or imaging controls are disabled
Either the camera does not advertise those services, or the account is read-only (User level) or anonymous. Switch to an Administrator or Operator account on the camera.
No picture, or a black frame
RTSP usually requires the same credentials as SOAP — the app injects them automatically, so an authentication failure there is almost always a credential mismatch. Also check that port 554 is reachable, try the sub stream (some cameras allow only a handful of concurrent RTSP sessions), and note that the app falls back to a labelled snapshot if no frame arrives.
Local first, and what that costs
Video is pulled straight from the camera to your phone. Nothing is uploaded, there is no vendor server and no account. Anonymous, non-personal usage statistics are described in the privacy policy. It keeps working during an internet outage, and latency is LAN latency. It also means remote viewing from outside your home network is not built in — you would need your own VPN into the LAN. That is a deliberate trade-off, not an omission.
Frequently asked
Do I need the camera manufacturer's app or a cloud account?
No. You need ONVIF enabled on the camera and its username and password. Remote97 talks to the camera directly over your local network.
Which cameras work?
Cameras that implement the ONVIF device, media and (optionally) PTZ services. Brand does not matter, because the app uses the standard service addresses the camera reports rather than brand-specific URL patterns. A device that only answers the discovery probe without an ONVIF service will be flagged as suspected, not added as supported.
Why does it ask for a username and password?
ONVIF signs each SOAP request with a WS-Security UsernameToken, and the RTSP stream normally requires the same credentials. Without them the camera will not return a stream URL. The app verifies the credentials with an authenticated command before saving the device, so a typo is reported immediately.
Can I view H.265 cameras?
Yes. The embedded player decodes H.264 and H.265, and the app queries both Media and Media2 services so H.265-only profiles are not missed.
What is the difference between main and sub stream?
Main is the highest-resolution profile, used for fullscreen and single-camera detail view. Sub is the lowest, used for home thumbnails and multi-camera views to save bandwidth and stay within the camera's RTSP session limit. You can switch between them on the detail and fullscreen views.
Can it record video or play back recordings?
No. Remote97 provides live viewing and control, not recording or NVR playback. There is no cloud storage and no local recorder in the app.
Does it work without internet?
Yes, as long as the phone and camera are on the same local network. Internet is only needed to download the app and updates.
Where to go next
- Control RS-232 / RS-485 gear over IP — the other half of "no native driver" setups.
- Home theater & smart home control: the complete guide — how cameras fit into a whole room.
- Why local IP control beats cloud hubs — the architecture argument.
- One-tap movie-night scenes — ordered steps and delays.
