Mobotix

Mobotix Missing Features? Enterprise Fix Guide

Mobotix cameras missing features? Resolve enterprise-level issues with targeted diagnostics and brand-specific tools. Expert guidance for IT professionals.

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
Thermal analytics features unavailable despite sensor activation
Edge storage failover not triggering during network outages
Camera does not detect motion in low-light conditions even with IR enabled

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

Verify Your Mobotix Camera's Feature Availability

If your Mobotix camera is missing expected features such as thermal analytics, edge storage, or advanced motion detection, the root cause is likely a combination of firmware limitations, configuration errors, or hardware compatibility. This guide provides targeted diagnostics for IT professionals using Mobotix's enterprise tools. Begin with quick checks before proceeding to advanced troubleshooting.

Quick Fixes for Mobotix Missing Features

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

Check VMS dashboard status: In MxManagementCenter, navigate to Cameras → [device] → Status. Look for Feature Lock or Channel Mismatch indicators.
Verify PoE link light: Ensure the switch port shows Class 3 (802.3at) for cameras requiring advanced features (e.g. MOBOTIX M73 with dual-lens platform).
Ping the camera IP: Use ping [camera_ip] from the management server to confirm basic connectivity. If unreachable, check VLAN assignment in MxManagementCenter → Network Settings.
Check status LED: A blinking red LED on the camera housing may indicate firmware update pending or analytics module disabled.
Power cycle via PoE: Disable the switch port for 30 seconds, then re-enable to force a firmware reinitialisation.

Diagnose Mobotix Feature Availability Issues

Check Firmware Channel Configuration

Mobotix cameras require specific firmware channels (stable/beta) to activate enterprise features. Access MxManagementCenter → Firmware Management and select the affected camera:

Verify channel selection: Ensure the camera is on the stable channel unless testing beta features.
Check for staged rollout: If features are missing, confirm the camera is not in a staged deployment group. Use the Staged Deployment tab to apply updates to all devices.
Review release notes: Access the Release Notes section in Mobotix's support portal to confirm feature availability for the current firmware version.

Validate Analytics Module Activation

For cameras with thermal or optical analytics (e.g. MOBOTIX M73), ensure the analytics module is enabled:

MxManagementCenter → Camera Configuration → Analytics: Confirm Thermal Sensor and Optical Sensor options are activated.
Check thermal analytics status: Use the Thermal Analytics Status tool in MxThinClient to identify errors like sensor not detected or power budget exceeded.
Verify PoE power: Ensure the camera is receiving 802.3at (Class 3) power. Access MxManagementCenter → Power Supply and confirm the Power Budget is sufficient for dual-lens operation.

Confirm VMS Integration Settings

Missing features may stem from incorrect VMS integration. Follow these steps:

Validate stream profile: In MxManagementCenter → RTSP Settings, confirm the Stream Profile matches the VMS platform's requirements (e.g. H.265 for high-resolution thermal feeds).
Check ONVIF profile compliance: Use the ONVIF Profile Check tool in MxThinClient to confirm the camera supports Profile S for advanced motion detection.
Re-register the camera: If features remain missing, delete the camera from the VMS and re-add it via MxManagementCenter → Camera Registration.

Use Network Diagnostics Tools

Leverage Mobotix's proprietary tools to isolate network-related feature issues:

MxThinClient diagnostics: Run a Network Health Check to identify VLAN misconfigurations or IGMP snooping blocking multicast streams.
Packet capture analysis: Use the Network Capture Tool in MxThinClient to inspect traffic for dropped packets or authentication failures.
DHCP lease verification: In MxManagementCenter → Network Settings, confirm the camera has a static IP or a DHCP lease on the correct VLAN.

Evaluate Enterprise Feature Licensing

Some Mobotix features require additional licensing:

Access the licensing dashboard: In MxManagementCenter → Licenses, confirm all required features (e.g. edge storage, thermal analytics) are activated.
Check for expired licenses: If a license is expired, renew it via Mobotix's support portal.
Verify VMS compatibility: Ensure the VMS platform (e.g. Wisenet WAVE VMS) supports the camera's advanced features. Refer to the Compatibility Matrix in Mobotix's documentation.

Advanced Troubleshooting for Mobotix Feature Issues

Perform a Factory Reset

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

MOBOTIX M73: Remove the housing cover, press and hold the reset button on the main board for 10 seconds while powered.
MOBOTIX c71: Use the supplied tool to remove the dome cover, then press and hold the reset button on the main board for 10 seconds.
MOBOTIX MOVE SD-340-IR: Access the maintenance port, press and hold the reset button for 15 seconds until the camera begins its reset sequence. After resetting, reconfigure the camera via MxManagementCenter and reapply firmware updates.

Analyse VMS Database Consistency

Missing features may stem from VMS database corruption:

Run a database check: In the VMS platform (e.g. Avigilon Control Center), navigate to Database Tools → Repair and initiate a consistency check.
Re-import camera settings: If the VMS database is corrupted, delete the camera from the VMS and re-import settings via MxManagementCenter.
Verify feature activation: After re-import, check MxManagementCenter → Feature Activation to confirm all features are enabled.

Root Causes of Mobotix Feature Discrepancies

Enterprise-Level Network Configuration

Missing features often trace to network misconfigurations:

VLAN tagging errors: Ensure the camera is assigned to the correct VLAN in MxManagementCenter → Network Settings. VLAN misconfigurations can block analytics traffic or firmware update channels.
PoE power budget exhaustion: For switches managing multiple Mobotix cameras, verify the PoE budget in MxManagementCenter → Power Supply. Insufficient power may disable advanced features like thermal analytics.
DHCP scope exhaustion: If the camera is on a DHCP-assigned IP, confirm the scope includes enough addresses for all devices on the VLAN.

Firmware and Feature Roadmap

Some features are only available on specific models or firmware channels:

Model-specific features: Check the Feature Matrix in Mobotix's documentation to confirm your model supports advanced analytics or edge storage.
Firmware roadmap: Access the Mobotix Firmware Roadmap on their support portal to see if requested features are planned for future updates.
Channel restrictions: Features on the stable firmware channel may be delayed compared to beta versions. Use the Firmware Management tool in MxManagementCenter to switch channels if required.

Protecting Your Mobotix Investment for Mobotix Cameras

Enterprise Maintenance Best Practices

To prevent feature discrepancies, implement these strategies:

Schedule firmware updates: Use MxManagementCenter → Firmware Management to apply updates during off-peak hours. Enable staged deployment for large deployments.
Monitor PoE budget: Regularly check MxManagementCenter → Power Supply to ensure switches have sufficient headroom for all connected devices.
Dedicated VLANs: Assign Mobotix cameras to a dedicated VLAN to isolate analytics traffic from other network segments.
Enable SNMP monitoring: Use SNMP traps in MxManagementCenter to alert on PoE budget exhaustion or firmware update failures. 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 Mobotix Replacement for Mobotix Cameras

When troubleshooting exceeds 30 minutes without success, consider hardware replacement:

Battery camera lifespan: 3-5 years typical. Battery degradation may prevent advanced features like thermal analytics from functioning.
Wired camera lifespan: 5-8 years typical. Sensor degradation or firmware EOL may limit feature availability.
UK procurement: Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods. For enterprise deployments, contact Mobotix support via their official portal for RMA processes.
Warranty considerations: Ensure your deployment includes active support contracts for firmware updates and feature activation assistance.

What if this wasn't your problem to solve?

scOS detects suspicious activity — not motion. It only alerts you when something matters, like a person would. Designed to be left alone. 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 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 are a common root cause for missing features in Mobotix cameras. Navigate to MxManagementCenter, select the affected camera, and verify the Network Settings tab. Ensure the VLAN ID matches the switch port configuration. If the camera is assigned to a different VLAN than the management platform, communication will fail. Use the Network health check tool within MxThinClient to confirm VLAN tagging is enabled. For switches supporting 802.1Q, ensure QoS policies are not blocking management traffic on the designated VLAN. If VLAN assignment is correct but features remain missing, check for firmware channel mismatches in the Firmware Management section of MxManagementCenter.

Firmware management in Mobotix systems relies on firmware channels (stable/beta) defined in MxManagementCenter. Access the Firmware Management tab, select the camera, and confirm the channel matches the intended deployment. If a feature is missing, it may be due to a staged rollout where only a subset of cameras has updated firmware. Use the Staged Deployment option to apply updates incrementally. If the camera is on the stable channel but newer features are required, switch to the beta channel and monitor for compatibility issues. Always verify feature availability in the Release Notes section of Mobotix's official support portal before channel changes.

Thermal analytics features on Mobotix cameras (e.g. MOBOTIX M73) require analytics module activation in MxManagementCenter. Navigate to Camera Configuration → Analytics and confirm the Thermal Sensor option is enabled. If the feature is disabled, re-enable it and restart the camera. Check the Thermal Analytics Status tool within MxThinClient for error codes. If the sensor is not detected, verify the Power Supply tab in MxManagementCenter to ensure the camera is receiving sufficient PoE (802.3at) power. For models with dual-lens platforms, ensure the Optical Sensor is not conflicting with the Thermal Sensor in the Lens Configuration settings.

Enterprise support for Mobotix cameras requires accessing the MxManagementCenter Event Log and Network Diagnostics tools. If features remain missing after basic troubleshooting, initiate a packet capture via the Network Health Check tool in MxThinClient. Export the capture file and submit it to Mobotix support via their official portal. For hardware-related issues, use the RMA Process in MxManagementCenter → Support Tools. Select the affected camera, generate a diagnostic report, and follow the instructions to return the device for evaluation. Enterprise customers with active support contracts should escalate via the Priority Support channel in the Support Portal.

All Troubleshooting Guides