Verify Your Mobotix Camera's Feature Availability
If your Mobotix camera is missing advertised features such as thermal analytics, cloud connectivity, or 4K resolution, the issue likely stems from incorrect configuration, firmware incompatibility, or licensing constraints. Confirm that the camera is registered to the correct firmware channel and that all required modules are activated. Use MxManagementCenter to verify subscription tiers and ensure the camera's capabilities align with your purchased features. If no resolution is found, proceed to the quick checks below.
Quick Fixes for Mobotix Missing Features
Before diving into advanced diagnostics, perform these initial checks:
- Check VMS dashboard status: In your VMS platform, confirm the camera is online and that all advertised features are listed as 'enabled'.
- Verify PoE link light: On the switch port, ensure the camera is receiving power (Class 3 or 4). If the link light is off, check the switch's power budget.
- Ping the camera IP: Use the command line to ping the camera's IP address and confirm network connectivity.
- Check status LED: On the camera housing, ensure the LED indicates a stable connection (green light for active features, amber for limited functionality).
- Power cycle via PoE switch: Disable and re-enable the switch port to restart the camera's network stack.
Diagnose Missing Features via MxManagementCenter
Check Firmware Channel Configuration
Access MxManagementCenter and navigate to Camera Settings → Firmware Management. Ensure the firmware channel is set to 'stable' unless testing beta features. If the camera is stuck in a pending state, check the event log for errors related to the firmware update. For advanced users, use the MxThinClient diagnostics tool to capture network traffic and identify blocking factors such as firewall rules or incorrect RTSP stream URLs.
Validate Analytics Module Activation
For models like the MOBOTIX M73 or S ONE Dual, ensure the 'Thermal analytics module' is activated in MxManagementCenter. If the module is disabled, re-enable it and confirm the camera's firmware is up to date. Use the Network health check feature in MxManagementCenter to identify misconfigurations or licensing issues.
Confirm VMS Integration Settings
If the camera is not displaying expected features in your VMS, verify the connection settings in MxManagementCenter. Ensure the VMS is using the correct stream profile (e.g. 4K for the c71 model) and that the ONVIF profile is compatible with your VMS platform. For cloud-managed cameras, confirm that the 'Cloud connectivity' feature is enabled and that the necessary ports (e.g. 443, 80) are open in your firewall.
Advanced Diagnostics for Missing Features
Use MxThinClient for Protocol Analysis
Launch the MxThinClient diagnostics tool and connect to the camera via its IP address. Use the 'Network health check' feature to identify issues such as multicast/IGMP snooping blocking RTSP streams or incorrect VLAN assignments. For cameras using the MOVE SD-340-IR PTZ model, verify that the 'Cloud connectivity' module is activated and that the camera is receiving sufficient power via PoE++ (802.3bt).
Review VMS Database Consistency
If the camera is registered but missing features in the VMS, perform a VMS database consistency check. Navigate to the VMS platform's configuration settings and verify that the camera's license is active and that the feature set matches your subscription tier. For advanced users, use the MxThinClient tool to export the camera's event log and identify errors related to missing features.
Escalate to Enterprise Support
If the issue persists, contact Mobotix support via https://www.mobotix.com/en/support. Provide the camera model, firmware version, and any error codes from the MxThinClient diagnostics tool. For UK-based users, mention any CGNAT-related issues and confirm that the camera is configured for private IP address routing.
Root Causes of Missing Features
Missing features on Mobotix cameras are often due to firmware incompatibility, licensing constraints, or incorrect configuration settings. Common causes include:
- PoE budget exhaustion: A switch port may not be allocating sufficient power (Class 3 or 4) for the camera's features.
- VLAN misconfiguration: The camera may be assigned to a VLAN without sufficient IP addresses or incorrect stream profiles.
- VMS licensing: The VMS platform may not have the required license to activate advanced features like thermal analytics or 4K resolution.
- Firmware channel mismatch: The camera may be using a 'stable' firmware channel that does not support the requested feature.
- UK-specific CGNAT issues: Mobile broadband providers like EE or Vodafone may block cloud connectivity unless the camera is configured for private IP routing.
Prevention and Long-Term Care
To avoid missing features on Mobotix cameras, schedule regular firmware updates via the MxManagementCenter and ensure all licenses are active. Use a dedicated VLAN for cameras and configure QoS policies to prioritize RTSP streams. For advanced users, enable the MxThinClient diagnostics tool to monitor network health and firmware compatibility. 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.
Replacement Decisions for Mobotix Cameras
If troubleshooting exceeds 30 minutes and basic fixes fail, consider replacing the camera. Wired Mobotix cameras typically last 5–8 years, while battery-powered models degrade after 3–5 years. For UK users, the Consumer Rights Act 2015 provides a 6-year right to claim faulty goods. If the camera is beyond its lifecycle, consult Mobotix support to confirm compatibility with your current VMS platform and subscription tier.