Mobotix

Mobotix Person Detection Errors? Enterprise Fix Guide

Mobotix person detection errors? Resolve AI misidentification with enterprise-specific tools and diagnostics. Expert guidance for IT professionals.

Is this your issue?

Camera shows offline in 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
AI detection misidentifies vehicles as people in low-light conditions
Person detection fails in wide-angle zones despite proper zone configuration
Thermal analytics status shows 'module not responding' in MxThinClient

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

Validate Mobotix Person Detection Accuracy

Your Mobotix camera may be misidentifying objects or missing people due to AI model limitations, lighting conditions, or suboptimal camera angles. This guide provides enterprise-specific steps to resolve these issues using MxManagementCenter, MxThinClient, and Mobotix-specific analytics tools. Begin with quick checks before diving into advanced diagnostics.

Quick Fixes for Mobotix Detection Issues

Perform these 30-second checks first:

Check the VMS dashboard status in MxManagementCenter → Cameras → [device] → Status. A red icon may indicate analytics module failure.
Verify the PoE link light on your switch port. A flickering or absent light suggests power negotiation issues affecting camera performance.
Ping the camera's IP address from the VMS server using ping [camera_ip]. A 100% packet loss suggests network connectivity problems.
Power cycle the camera by disabling the PoE port on the switch for 30 seconds, then re-enabling it. This resets the camera's analytics processing.

Deep Troubleshooting for Mobotix Detection Errors

Verify Network Health Using MxThinClient

Open MxThinClient on your management server and navigate to Network → Health Check. Look for:

Bandwidth utilization exceeding 80% on the camera's VLAN — this may degrade AI processing.
Jitter greater than 10ms on the RTSP stream — indicates unstable network conditions.
Multicast traffic blocked by IGMP snooping — analytics streams may be dropped. If issues are found, reconfigure your VLAN with QoS prioritization for RTSP (port 554) and ONVIF (port 80).

Adjust Detection Confidence Thresholds

In MxManagementCenter, go to Cameras → [device] → Analytics Settings. Adjust the detection confidence threshold from the default (75%) to 85% or higher. This reduces false positives but may increase missed detections. Save changes and restart the camera via Camera → Reboot.

Check Firmware Channel and Analytics Module Status

Access MxManagementCenter → Firmware → Channel Management. Ensure the camera is on the stable firmware channel. If on beta, switch to stable and restart. Also, check Thermal analytics status in Camera → Analytics → Thermal Module. A red status indicates a failed update or incompatibility.

Validate ONVIF/RTSP Stream Profiles

In MxManagementCenter, go to Cameras → [device] → Stream Profiles. Ensure the Analytics stream is enabled and set to RTSP (port 554) with H.265 encoding. Test the stream directly using rtsp://[camera_ip]:554/Streaming/Channels/101 in a VMS like Wisenet WAVE or Avigilon Control Center.

Use MxThinClient for Advanced Diagnostics

Open MxThinClient and navigate to Tools → Network → Packet Capture. Filter for RTSP and ONVIF traffic. Look for:

Dropped packets or retransmissions — indicates network congestion.
Authentication failures — suggests incorrect ONVIF credentials in the VMS.
Analytics traffic not being routed — verify VLAN trunking and QoS policies.

Advanced Troubleshooting and Escalation

Factory Reset for Specific Models

For MOBOTIX M73, remove the housing cover and press the reset button for 10 seconds. For MOBOTIX c71, use the supplied tool to access the reset button. For MOVE SD-340-IR, access the maintenance port and press for 15 seconds. After reset, reconfigure the camera in MxManagementCenter.

Packet Capture and Protocol Analysis

Use MxThinClient to capture packets on the camera's interface. Analyze for:

RTSP stream interruptions → Check switch port configuration and QoS.
ONVIF handshake failures → Verify VMS credentials and port 80 access.
Analytics traffic blocking → Ensure VLAN trunking and multicast support.

VMS Database Consistency Check

In Avigilon Control Center, go to Tools → Database → Repair. For Wisenet WAVE, use System → Database → Validate. If corruption is found, back up the database and perform a repair. Re-register the camera in MxManagementCenter after resolution.

Escalate to Mobotix Enterprise Support

If issues persist, escalate via https://www.mobotix.com/en/support. Provide:

MxThinClient diagnostics logs (Tools → Export → Logs)
Firmware channel history from MxManagementCenter
VMS integration details (e.g. Avigilon Control Center version)
Packet capture files from MxThinClient Include a summary of steps already taken to avoid duplication.

Root Causes of Mobotix Detection Errors

Common enterprise causes include:

PoE power budget exhaustion on switches — ensure Class 3 (25.5W) is allocated for analytics-heavy models like the MOBOTIX M73.
VLAN misconfiguration blocking analytics traffic — verify VLAN tagging and QoS policies.
Firmware incompatibility after staged rollouts — ensure stable channel alignment with your VMS.
Lighting conditions affecting AI accuracy — use MxThinClient to review Thermal analytics status and adjust camera angles.
UK-specific humidity — ensure IP66 housings are used and cable glands are sealed against moisture ingress.

Protecting Your Mobotix Investment

Enterprise Maintenance Practices

Schedule firmware updates during off-peak hours using MxManagementCenter's Staged Rollout feature.
Monitor VMS health with MxThinClient's Network health check and Device Health metrics.
Plan PoE budgets with 20% headroom for analytics-heavy models like the MOVE SD-340-IR.
Implement dedicated VLANs for cameras with QoS prioritization for RTSP (port 550-554).
Use SNMP monitoring to track bandwidth utilization and packet loss on camera VLANs.

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.

When to Replace Your Mobotix Person Equipment and Lifespan Planning

When replacing Mobotix cameras, consider:

Wired camera lifespan: 5-8 years, with sensor degradation and firmware EOL as factors.
Battery camera lifespan: 3-5 years, with battery degradation after 300-500 cycles.
Surveillance HDD lifespan: 3-5 years for WD Purple or Seagate SkyHawk drives.
UK warranty rights: Up to 6 years under the Consumer Rights Act 2015 for faulty goods.
Troubleshooting time: If basic fixes take more than 30 minutes, hardware replacement may be necessary.

What if alerts actually meant something?

scOS doesn't use motion detection. It detects suspicious activity and alerts you only when something matters. Like a person would. All features included, no subscriptions.

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

Verify VLAN assignments in MxManagementCenter under Network → Camera Settings. Ensure the camera is on a dedicated VLAN with sufficient bandwidth. Misconfigured VLANs can disrupt AI processing and lead to false detections. Use the Network health check tool to validate VLAN tagging and QoS policies. If VLANs are correct, check for multicast/IGMP snooping blocking analytics traffic.

Access MxThinClient diagnostics via the camera's web interface → Analytics → Detection Settings. Adjust the detection confidence threshold from the default (75%) to 85% or higher for critical zones. Lower thresholds increase false positives, while higher thresholds may miss smaller targets. Save changes and restart the camera via MxManagementCenter → Camera → Reboot.

In MxManagementCenter, navigate to Firmware → Channel Management. Ensure the camera is on the stable firmware channel unless testing new features. Staged rollouts can cause temporary detection instability. If issues persist, perform a firmware rollback using the Rollback Wizard under Firmware → History. Confirm compatibility with your VMS platform before proceeding.

Use MxThinClient to capture packets on the camera's interface. Open Tools → Network → Packet Capture and filter for RTSP and ONVIF traffic. Look for dropped packets or authentication failures. If analytics traffic is blocked, check firewall rules in your VMS (e.g. Wisenet WAVE or Avigilon Control Center) and ensure port 554 (RTSP) is open for analytics streams.

All Troubleshooting Guides