Resolution

4 MP (2688 x 1520)

Lens

2.7-13.5 mm motorized vari-focal

IR Distance

up to 60 m

Min. Illumination

0.003 lux @ F1.5

Video Compression

H.265 / H.264 / MJPEG

Power

PoE (802.3af) / 12 VDC

Interface

RJ45 10/100M

Quick Start — Dahua IPC-HFW4433R-ZS

Get the bullet camera online and streaming. These are reference patterns; confirm against the official Dahua IPC HTTP API / NetSDK documentation for your firmware.

1. Find the device

Use Dahua ConfigTool (Windows) or scan the subnet:

# example: discover Dahua devices
nmap -p 37777,80,554 192.168.1.0/24

Default IP is usually DHCP; factory web UI is at http://<ip>.

2. Activate & set password

Log in to the web UI with the default admin / admin (or blank), then set a strong password. Devices ship inactive and must be activated.

3. Live stream (RTSP)

ffplay "rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0"
# subtype=0 main stream, subtype=1 sub stream

4. Verify the HTTP API

curl --digest -u admin:PASSWORD \
  "http://192.168.1.65/cgi-bin/magicBox.cgi?action=getSystemInfo"

A successful response returns version= and serialNumber= lines.

Next steps

• API reference → API tab (CGI examples).
• Application integration → SDK tab (NetSDK).

API Reference — Dahua HTTP API (IPC-HFW4433R-ZS)

Dahua cameras expose a CGI-based HTTP API under /cgi-bin/..., authenticated with HTTP Digest (some endpoints require a session token obtained via global.login).

Reference patterns only. Parameter names and availability vary by firmware — verify against the Dahua IPC HTTP API document.

Authentication

curl --digest -u admin:PASSWORD "http://192.168.1.65/cgi-bin/magicBox.cgi?action=getSystemInfo"

For programmatic sessions, call global.login to obtain a session token, then append session=TOKEN to subsequent CGI calls.

Common endpoints

Example: get config

curl --digest -u admin:PASSWORD \
  "http://192.168.1.65/cgi-bin/configManager.cgi?action=getConfig&name=VideoInOptions"

Example: snapshot

curl --digest -u admin:PASSWORD \
  "http://192.168.1.65/cgi-bin/snapshot.cgi?channel=1" -o snap.jpg

Notes

• Media port 554 (RTSP), TCP 37777 is the private transport used by the SDK/DMSS.
• ONVIF is also supported for cross-vendor clients.

SDK — Dahua NetSDK (IPC-HFW4433R-ZS)

For recording, real-time playback, PTZ, and alarm handling, use Dahua NetSDK (binary 37777 protocol). It is more capable than CGI for media and events.

Reference overview. Obtain NetSDK (headers + libs) and samples from the official Dahua developer portal.

Languages & platforms

• C / C++ — native NetSDK, Windows & Linux (incl. arm).
• C# — via the provided NetSDKCS wrapper.

Typical flow (C# reference)

// Pseudocode — adapt to NetSDK's wrapped declarations
NETSDK.Init();
int lLoginID = NETSDK.Login(ip, port37777, "admin", password, out deviceInfo);
if (lLoginID <= 0) throw new Exception("Login failed");
// StartRealPlay(lLoginID, channel, windowHandle) ...
NETSDK.Logout(lLoginID);
NETSDK.Cleanup();

Best practices

• Call Init() once per process; Cleanup() at exit.
• Register the alarm callback if you need motion/IO events.
• Match 32/64-bit SDK binaries to your application's bitness.

FAQ — Dahua IPC-HFW4433R-ZS

Q: The camera won't stream / RTSP times out. A: Confirm activation and the admin password. Verify the device IP and that port 554 is reachable.

Q: CGI returns 401. A: Use Digest auth (curl --digest). For stateful calls, obtain a session via global.login and pass session=.

Q: Forgot the admin password. A: Use ConfigTool "Password Reset" with the device's reset file/security code, or contact the vendor channel.

Q: Which port for the SDK? A: TCP 37777 is the NetSDK/DMSS transport. RTSP is 554; HTTP 80.

Q: ONVIF vs HTTP API? A: ONVIF works for cross-vendor clients; the Dahua HTTP API and NetSDK give full vendor features (IVS events, motorized lens control).