Distinguish camera generation from stream format
The official technical article separates newer Mx cameras from Mx6 devices running firmware before version 5.4.0.44. Stream layouts and paths changed between firmware generations. A URL that worked before an update may therefore need to be obtained again from the current interface.
MOBOTIX MOVE is a separate range of centrally managed cameras. Its ONVIF capabilities depend on the individual model. Do not apply an Mx7 profile path to a MOVE camera merely because the manufacturer name is the same. Likewise, MxPEG is not a synonym for a standard H.264 video stream.
Check the integration mode and connect locally
- Read the model label and installed camera software version. Identify whether the device belongs to Mx6, Mx7 or MOVE.
- Sign in to the authorized local configuration and find the integration-protocol settings for that camera generation.
- Check which mode is enabled: RTP, ONVIF or another documented integration. Record the configured RTSP port and available video profiles.
- For a standard RTP-mode URI use the corresponding standard camera account. For an ONVIF-specific URI, check whether the camera requires an ONVIF account instead.
- Copy the appropriate current URI into SmartRTSP on a reachable local network. Confirm the selected video codec and test the stream before adding further functions.
rtsp://<camera-ip>:<configured-rtsp-port>/stream/profile0Treat profile0 as a mode-specific example
The example above corresponds to a documented RTP-integration stream layout; it is not a universal MOBOTIX address. ONVIF mode can use a profile-token-based URI, and older firmware can expose different resources. Use the camera’s current documentation or the URI returned for the selected ONVIF profile.
A request that reaches the camera but returns unauthorized may be using the wrong account category. A request that authenticates but has no usable video may instead be selecting a different encoder or codec. Keep those two checks separate so that a profile change does not conceal a credential problem.
Keep playback and camera capabilities separate
First verify one ordinary live stream. Then check audio, pan/tilt control, dewarping and any model-specific recording behavior separately. A camera being listed as ONVIF capable does not prove that every optional function is exposed to every viewer.
When adjusting stream dimensions or integration mode, consider the recorder or management system already using the device. Save the previous configuration and avoid changing a production integration simply to try a guessed URL.
Check each feature independently
Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.
Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.
Frequently Asked Questions
Can I use one URI for every Mx and MOVE camera?
No. Camera family, firmware and integration mode determine the address and available encoders.
Why does my normal camera password fail on an ONVIF URL?
The documented integration modes can use different account categories. Confirm the ONVIF user and permissions required by that URI.
Is this a physical MOBOTIX compatibility certification?
No. Official documentation was checked on 2026-10-18. Validate the exact camera, format and functions on the local installation.
Official sources and scope
Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.