Verify the full model and regional specification
The cited Ranger 2 5MP and Bullet 2E 3MP specification pages list ONVIF and H.264/H.265 video. Those statements apply to the products and regional pages named. They should not be expanded into a promise for every resolution, battery model, hardware revision or regional firmware sold under the Imou brand.
Compare the physical model label with the manufacturer page rather than relying only on the marketing family name. If the local interface is absent from the matching specification, ask Imou for confirmation before assuming that a firmware change or another model URL will make it available.
Use a discovered URI instead of an assumed OEM path
For a supported and correctly configured ONVIF camera, use the video profile and stream URI returned by the camera. This avoids treating a familiar-looking third-party URL template as an official Imou standard. The sources used here do not establish one universal RTSP path or port for every Imou product.
An Imou Life cloud account and a local device account serve different purposes. Follow the exact model instructions for obtaining or configuring local integration credentials. Do not assume that a factory password, a cloud password or a label code is valid for every model.
Prepare a local connection step by step
- Record the model number, hardware revision if provided, region and installed firmware.
- Check the matching Imou specification or manual for ONVIF or another documented local stream interface.
- Complete the manufacturer setup and confirm that the camera and viewing device can reach each other on a trusted local network.
- Configure the local integration account and any required service switch according to that model instructions.
- Try supported ONVIF discovery in SmartRTSP and select an advertised video profile, or enter a URI explicitly provided by the model documentation.
- Verify the correct lens, first-frame video and stable playback. Save the working settings without publishing device credentials.
Keep movement and cloud features outside the video claim
A Ranger camera with mechanical movement may pan in the manufacturer app, while a Bullet camera has a different physical design. An ONVIF specification or RTSP picture alone does not establish PTZ, auto-tracking, notifications or two-way-audio compatibility in another app.
If discovery fails, first check local reachability, the integration account and any model-specific enablement requirements. If a profile is discovered but video fails, inspect the returned URI and selected encoding. Do not solve an initial local test by exposing camera ports to the public Internet. Model confirmation is more useful than repeatedly trying unrelated brand templates.
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
Do all Imou cameras support ONVIF?
No universal claim is made here. The cited regional specifications explicitly list it for the named Ranger 2 5MP and Bullet 2E 3MP examples. Check your exact model and firmware.
Can I copy a Dahua-style URL for every Imou camera?
No official brand-wide path is established by these sources. Prefer the URI returned by the supported camera or documented for the exact model.
Will a working video feed include tracking and two-way audio?
Not necessarily. Video, motor control, tracking and talkback are separate capabilities that must be checked independently.
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.