Mobotix

Mobotix Camera Not Recording? Enterprise Fix Guide

Mobotix cameras not recording? Follow this enterprise-focused guide to resolve storage, firmware, and VMS integration issues using MxManagementCenter and brand-specific diagnostics.

Is this your issue?

Camera shows 'Recording Disabled' in MxManagementCenter 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
Thermal analytics not triggering events despite motion in the field of view

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

Validate Mobotix Camera Recording Configuration

If your Mobotix camera is failing to record footage despite appearing online, the issue likely stems from storage configuration, motion detection settings, or VMS integration. This guide focuses on advanced diagnostics using MxManagementCenter, firmware-specific tools, and enterprise features unique to Mobotix. Confirm the camera is enrolled in the correct firmware channel and that storage media (microSD card or cloud subscription) is properly configured before proceeding.

Quick Checks for Mobotix Recording Failures

Before diving into advanced diagnostics, perform these 30-second checks:

Verify VMS Dashboard Status: In MxManagementCenter, check if the camera shows 'Recording Disabled' under Camera Status. A red icon may indicate failed storage verification.
Confirm PoE Link Light: On switches supporting 802.3at, ensure the port shows Class 3 power allocation. A Class 0 status suggests power budget exhaustion or incompatible switch firmware.
Ping the Camera IP: Use ping -c 4 [camera_ip]`` to confirm network connectivity. A 100% packet loss may indicate VLAN misconfiguration or firewall blocking.
Check Status LED: A solid green LED on the camera housing indicates normal operation. A flashing red light suggests storage failure or motion detection misconfiguration.
Power Cycle via Switch: Disable and re-enable the switch port for 30 seconds to reset the camera's network stack.

Deep Troubleshooting for Mobotix Recording Issues

Verify Storage Configuration and MicroSD Health

Mobotix cameras rely on internal microSD cards for local recording. For models like the M73, ensure the card is rated for continuous recording (e.g. Samsung PRO Endurance or SanDisk High Endurance). In MxManagementCenter, navigate to Camera Settings > Storage Configuration and verify:

Recording Mode: Set to 'Continuous' or 'Scheduled' based on your needs
Storage Destination: Confirm 'Internal Storage' is selected
Card Health: Use the SD Card Diagnostic Tool in MxManagementCenter to check for errors. A failing card will show 'Read Error' in the event log

Configure MxActivitySensor for Motion Detection

For cameras with on-device analytics (e.g. M73 or MOVE SD-340-IR), ensure MxActivitySensor is properly configured:

Access the camera's web interface at http://[camera_ip]
Navigate to Setup > Event Control > Motion Detection
Define Analytics Zones using the drag-and-drop tool
Set Sensitivity to 'High' for critical areas
Enable Directional Movement detection if required

Diagnose VMS Integration and License Issues

If using a VMS platform, confirm integration settings:

In MxManagementCenter, go to Camera Settings > VMS Integration
Verify ONVIF Profile is set to 'Profile S' for compatibility
Check RTSP Stream URL: rtsp://[username]:[password]@[camera_ip]/stream1
Ensure VMS License is active for the camera model. A deactivated license will show 'VMS Connection Failed' in the dashboard

Analyze Network Health with MxThinClient

Use the MxThinClient Diagnostic Tool to identify network issues:

Connect the tool to the same VLAN as the camera
Run a Full Network Health Check
Review Multicast/IGMP Snooping settings. If enabled, ensure the camera is in a Multicast-Allowed Zone
Check QoS Prioritization: Ensure the camera's VLAN has Priority 5 for video streams
Verify DHCP Lease Time: Set to 8 hours for enterprise environments

Confirm Firmware Channel and Update Status

Mobotix firmware updates are managed via Stable or Beta channels:

In MxManagementCenter, go to Firmware Management
Ensure the camera is enrolled in the Stable Channel for enterprise deployments
If an update is pending, check Download Status. A failed download may require a Staged Rollback to a previous version
For models like the c71, ensure Firmware Version matches the VMS Platform Compatibility List

Advanced Diagnostics and Recovery Steps

Perform a Model-Specific Factory Reset

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

MOBOTIX M73: Remove the housing cover and press the reset button on the main board for 10 seconds
MOBOTIX c71: Use the supplied tool to remove the dome cover and press the reset button on the main board
MOBOTIX MOVE SD-340-IR: Access the maintenance port and press the reset button for 15 seconds

Capture Network Traffic for Analysis

Use Wireshark to capture packets on the camera's VLAN:

Filter for rtsp and onvif traffic
Look for RTSP 503 errors indicating stream failure
Check for DHCP Offer packets to confirm the camera is receiving an IP address
If using HTTPS for camera management, ensure Port 443 is open on the firewall

Repair VMS Database Corruption

For VMS platforms like MxManagementCenter, run a database consistency check:

Navigate to System > Database Tools
Initiate a Database Repair scan
If corruption is detected, export the camera configuration and re-register the device
Re-import the configuration after repair completes

Root Causes of Mobotix Recording Failures

Common enterprise-level causes include:

PoE Budget Exhaustion: Multiple cameras on the same switch may exceed power limits, causing the camera to enter Power Saving Mode
VLAN Misconfiguration: Cameras on a VLAN without IGMP Snooping enabled may fail to receive multicast streams
VMS Licensing Issues: A deactivated license may prevent recording despite stable network and storage
Firmware Incompatibility: A staged firmware update may fail if the camera's ONVIF Profile doesn't match the VMS platform
UK-Specific: Building Regulations Part Q requirements may require thermal cameras to use 4K resolution for compliance, which may not be supported by all microSD cards

Keeping Your Mobotix System Healthy

Schedule Regular Firmware and Storage Checks

Use MxManagementCenter to schedule Monthly Firmware Health Checks
Set SD Card Diagnostic alerts for less than 10% remaining life
Implement QoS Policies for the camera VLAN with Priority 5 for video streams
Enable SNMP Monitoring on switches to track PoE usage in real time

Plan for Enterprise-Scale Deployments

Allocate 20% headroom in PoE budget for future expansions
Use Dedicated Camera VLANs to isolate video traffic from other services
For UK installations, ensure thermal cameras meet Part Q compliance with 4K resolution and motion detection enabled

Contextual Disclosure

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 System

Assess Camera Lifespan and Replacement Needs

Wired Cameras: Replace after 5-8 years due to sensor degradation
Battery Cameras: Replace after 3-5 years (battery life degrades after 300-500 cycles)
NVR HDDs: Replace after 3-5 years with surveillance-rated drives (WD Purple/Seagate SkyHawk)
MicroSD Cards: Replace after 1-2 years with high-endurance models
Warranty Rights: Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods (5 years in Scotland)

What if nothing was ever missed?

scOS records 24/7 and analyses every frame. It detects suspicious activity — not motion — and only alerts you when something matters. All features included.

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 feature tiers. Hub included, from £10/month. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

Verify PoE budget exhaustion by checking switch port power allocation in your network management system. For Mobotix cameras like the M73, ensure the switch supports 802.3at (PoE+) and that no other devices on the same VLAN are draining power. Use the MxManagementCenter's Network Health Check tool to identify underpowered ports. If the issue persists, temporarily disable non-critical devices on the same VLAN to free up power headroom.

In MxManagementCenter, navigate to Camera Settings > Storage Configuration and confirm the recording mode is set to 'Continuous' or 'Scheduled'. For hemispheric models like the c71, ensure Dewarping is enabled in the VMS. If using cloud storage, verify Subscription Status in the Account Management section. A failed subscription may prevent recordings from being saved to the cloud.

Use the MxThinClient Diagnostic Tool to run a full network health check. This tool identifies VLAN misconfigurations, multicast/IGMP snooping issues, and ONVIF profile compatibility. For PTZ models like the MOVE SD-340-IR, ensure RTSP Stream Profile is set to 'Main Profile' in the camera's web interface under Setup > Network > Streaming. A mismatch here can cause stream drops.

Access the Firmware Management section in MxManagementCenter and ensure the camera is enrolled in the Stable Channel. For models like the M73, a firmware update stuck in 'Pending' may indicate a failed download. Perform a Staged Rollback to a previous version, then retry the update. If the issue persists, contact Mobotix support with the Event Log from the camera's web interface.

For UK installations, check if Building Regulations Part Q requirements are affecting thermal cameras. Ensure thermal sensors are correctly configured in Setup > Thermal Analytics. If using a c71 in a stone or cavity wall environment, verify that WiFi Band settings are adjusted to 2.4GHz (if wireless) to avoid signal degradation. This is critical for outdoor models relying on wireless connectivity.

All Troubleshooting Guides