i-Pro

i-Pro App Won't Connect: Enterprise Troubleshooting Guide

i-Pro app connection failures? Resolve with enterprise-specific tools and diagnostics. Focus on VLANs, firmware channels, and i-PRO Configuration Tool workflows for swift recovery.

Is this your issue?

Camera shows offline in the VMS dashboard but responds to ping
RTSP stream drops intermittently despite stable network link
PoE negotiation fails — switch port shows Class 0 instead of expected Class 3
Firmware update stuck in pending state in the management platform
i-Pro app fails to discover the camera on the same network
Camera does not appear in the VMS platform after re-registration

Sound familiar? The guide below will help you fix it.

i-Pro App Connectivity Issues: Enterprise-Specific Troubleshooting

Your i-Pro app fails to connect to the camera, but the device itself may appear online. This typically indicates a misconfiguration in network settings, VMS integration, or firmware management. The root cause often lies in VLAN assignments, firmware channel mismatches, or incorrect RTSP/ONVIF profiles. This guide provides brand-specific tools and workflows to resolve these issues efficiently.

Quick Checks for i-Pro App Connection Failures

Before diving into advanced diagnostics, perform these immediate checks:

Verify VMS Dashboard Status: Open your VMS platform (e.g. i-PRO Configuration Tool) and confirm the camera is listed as Online. If it shows Offline, proceed to the next step.
Check PoE Link Light: Ensure the switch port connected to the camera shows a solid green light. A blinking or absent light may indicate PoE negotiation failures.
Ping the Camera IP: From the same network, use ping [camera_ip] to confirm basic connectivity. If the camera responds, the issue is likely application-layer.
Inspect Status LED: Look for a steady or blinking blue light on the camera. A red light may indicate a firmware update failure.
Power Cycle via Switch Port: Disable the switch port for 30 seconds, then re-enable it to restart the camera's network stack.

Verify i-Pro Camera Network Configuration

Check VLAN Assignment

Incorrect VLAN settings can prevent the i-Pro app from discovering the camera. In i-PRO Configuration Tool, navigate to Network Diagnostics → VLAN Check:

Confirm the camera's VLAN matches your VMS platform's expected VLAN (e.g. VLAN 100 for surveillance).
Ensure the VLAN allows UDP traffic on ports 3776 and 3777, which i-Pro uses for device discovery.
If the camera is on a different VLAN, update the switch port configuration to align with the camera's settings.

Validate PoE Budget

Insufficient PoE budget can cause the camera to power off or fail to negotiate a connection. In i-PRO Configuration Tool, use the PoE Budget Checker:

Confirm the switch port's allocated power matches the camera's requirements (e.g. 802.3bt for WV-S8574L Multi-Sensor).
If the PoE budget is exhausted, reassign the camera to a different switch port with sufficient headroom.
For large deployments, use PoE Budget Planner in i-PRO Configuration Tool to simulate power allocation across the network.

Diagnose i-Pro Firmware and VMS Integration

Check Firmware Channel

Firmware channel mismatches can prevent the i-Pro app from communicating with the camera. In i-PRO Configuration Tool, navigate to Firmware Management:

Confirm the camera is pulling updates from the correct channel (e.g. Stable or Beta).
If the camera is on a different channel than your network's firmware repository, update the channel setting to match.
For large deployments, use Staged Rollout in i-PRO Configuration Tool to apply firmware updates in batches, avoiding network congestion.

Validate RTSP/ONVIF Settings

Incorrect RTSP or ONVIF profiles can block the i-Pro app from accessing the camera. In i-PRO Configuration Tool, check the following:

RTSP Stream URL: Ensure the URL uses the correct IP address and port (typically 554).
ONVIF Profile: Confirm the profile matches the camera's capabilities (e.g. Profile S for standard streams).
If the camera is not appearing in the VMS dashboard, initiate a Camera Re-registration via the VMS platform's Device Discovery tool.

Advanced Diagnostics with i-PRO Configuration Tool

Perform Network Packet Capture

Use i-PRO Configuration Tool's Packet Capture feature to diagnose network-level issues:

Navigate to Network Diagnostics → Packet Capture and filter traffic on UDP ports 3776 and 3777.
Look for dropped packets or authentication failures in the capture log.
If the camera is behind a firewall, ensure the following ports are open: TCP 80/443 (HTTPS), UDP 3776/3777 (device discovery), and RTSP port 554.

Check VMS Licensing and Database Consistency

Incompatible licensing or VMS database corruption can prevent the i-Pro app from connecting. In your VMS platform (e.g. i-PRO Configuration Tool → Camera Management):

Confirm the camera has sufficient licensing for its resolution and analytics features (e.g. 33MP for WV-S8574L Multi-Sensor).
Run a Database Consistency Check to identify and repair any corruption in the VMS platform.
If the camera is not appearing in the VMS dashboard, initiate a Camera Re-registration via the VMS platform's Device Discovery tool.

Factory Reset and Escalation for i-Pro App Failures

Perform Model-Specific Factory Reset

If basic fixes fail, perform a factory reset using model-specific instructions:

WV-S2536L Dome: Press and hold the INITIAL SET button on the camera body for 15 seconds until the status indicator flashes.
WV-X2571LN PTZ: Press and hold the INITIAL SET button (accessible through a maintenance panel) for 15 seconds.
WV-S8574L Multi-Sensor: Press and hold the INITIAL SET button on the rear of the camera body for 15 seconds until the status LED changes.

After resetting, reconfigure the camera via i-PRO Configuration Tool and re-add it to the VMS platform.

Escalate to Enterprise Support

If issues persist, use the Enterprise Support Escalation process:

Submit a Support Ticket via i-Pro's official support website, including packet capture logs, VMS dashboard screenshots, and firmware channel settings.
For large deployments, request a RMA (Return Merchandise Authorization) if hardware failure is suspected.
Ensure your support ticket includes SNMP monitoring logs and QoS policy configurations to expedite resolution.

Root Causes of i-Pro App Connectivity Failures

Enterprise-Specific Network and Configuration Issues

PoE Budget Exhaustion: Insufficient power allocation across switches can cause cameras to power off or fail to negotiate a connection.
DHCP Scope Exhaustion: A depleted DHCP pool in the camera VLAN may prevent the camera from obtaining an IP address.
VMS Licensing Conflicts: Incompatible licensing can block the camera from registering in the VMS platform.
Firmware Channel Mismatches: Cameras pulling updates from incorrect channels may fail to communicate with the i-Pro app.
UK-Specific: Double NAT from Virgin Media Hub 5x or CGNAT from mobile broadband can prevent remote access via the i-Pro app.

Prevention and Long-Term Management

Maintain Network Health with i-PRO Configuration Tool

Schedule Firmware Updates using Staged Rollout to avoid network congestion.
Use VLAN Health Checks in i-PRO Configuration Tool to ensure consistent network segmentation.
Monitor PoE Budget Utilization with the PoE Budget Planner tool to avoid power exhaustion.

Full disclosure: we built scOS to address exactly this—the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.

Deciding on a I Pro App Replacement for i-Pro Cameras

When considering camera replacements, factor in:

Wired Camera Lifespan: 5-8 years typical, with sensor degradation and firmware EOL as factors.
NVR HDD Lifespan: 3-5 years for surveillance-rated HDDs (e.g. WD Purple/Seagate SkyHawk).
UK Consumer Rights Act 2015: Up to 6 years (5 years Scotland) to claim faulty goods under the CRA.
Troubleshooting Time: If basic fixes take more than 30 minutes, hardware failure is likely.

What if it couldn't go offline?

scOS uses wired cameras that can't be jammed or go offline. It detects suspicious activity and only alerts you when it matters — like a person would. Designed to be left alone.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No subscriptions. No tiers. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

VLAN misconfigurations often block i-Pro app discovery. Verify the camera is assigned to the correct VLAN in your switch configuration. In i-PRO Configuration Tool, navigate to Network Diagnostics → VLAN Check to confirm the camera's VLAN matches your VMS platform's expected VLAN. If mismatched, update switch port settings to align with the camera's configuration. Ensure the VLAN allows traffic on UDP ports 3776 and 3777, which i-Pro uses for device discovery. For multi-VLAN environments, confirm the camera's IP is within the correct subnet range.

Firmware channel conflicts can prevent i-Pro app communication. Access the Firmware Management section in i-PRO Configuration Tool and confirm the camera is pulling updates from the correct channel (e.g. Stable or Beta). If the camera is on a different channel than your network's firmware repository, update the camera's channel setting to match. For large deployments, use Staged Rollout in the i-PRO Configuration Tool to apply firmware updates in batches, avoiding network congestion. Always verify the camera's firmware version matches the VMS platform's compatibility requirements.

i-Pro app failures often stem from VMS integration errors. In your VMS platform (e.g. i-PRO Configuration Tool → Camera Management), verify the camera's RTSP stream URL and ONVIF profile settings. Ensure the RTSP URL uses the correct IP address and port (typically 554) and that the ONVIF profile matches the camera's capabilities (Profile S for standard streams). If the camera is not appearing in the VMS dashboard, initiate a Camera Re-registration via the VMS platform's Device Discovery tool. Confirm the VMS has sufficient licensing to support the camera's resolution and analytics features.

For enterprise environments, use Packet Capture in i-PRO Configuration Tool to diagnose network-level issues. Navigate to Network Diagnostics → Packet Capture and filter traffic on UDP ports 3776 and 3777. Look for dropped packets or authentication failures. If the camera is behind a firewall, ensure the following ports are open: TCP 80/443 (HTTPS), UDP 3776/3777 (device discovery), and RTSP port 554. For cloud-managed deployments, confirm the camera's Cloud Connectivity status in i-PRO Configuration Tool. If the camera is not connected to the cloud, check the Cloud Credentials section for expired certificates or incorrect region settings.

All Troubleshooting Guides