Troubleshooting<\/a><\/li><\/ol><\/nav>\n\n\n\nThe problem: cloud-only by design<\/h2>\n\n\n\n Out of the box, the Imou Cruiser Dual has no local management interface. An nmap scan reveals only a handful of open ports:<\/p>\n\n\n\n
PORT STATE SERVICE\n53\/tcp open domain # NextDNS proxy\n80\/tcp open http # ONVIF (no web UI)\n554\/tcp open rtsp # Video streams\n8086\/tcp open unknown # Dahua proprietary (times out)\n37777\/tcp open unknown # Dahua binary protocol (non-functional)<\/pre>\n\n\n\nPort 80 serves ONVIF SOAP endpoints – not a web interface. Port 8086 is open but times out on all Dahua CGI endpoints. Port 37777 sends an empty challenge and goes silent. No telnet, no SSH, no FTP.<\/p>\n\n\n\n
When you try to connect to the RTSP port with the safety code printed on the camera label, the connection is reset by the camera<\/strong>. Port 554 is open and the RTSP service is listening, but it actively refuses to complete the handshake. This is because the TLS encryption toggle in the Imou Life app is enabled by default – and the camera’s RTSP service won’t talk plain RTSP while TLS mode is on.<\/p>\n\n\n\nInterestingly, ONVIF on port 80 is not affected<\/strong> by the TLS toggle – snapshots and device queries work regardless. Only the RTSP service is gated.<\/p>\n\n\n\nStep 1: Disable the TLS encryption toggle<\/h2>\n\n\n\n In the Imou Life app, go to your camera’s settings and find the Encryption<\/strong> or TLS<\/strong> toggle. Turn it off<\/strong>. This is the single most important step – without it, the RTSP service resets all connections.<\/p>\n\n\n\nI verified this experimentally by toggling TLS via the cloud API and testing RTSP after each change:<\/p>\n\n\n\nTLS setting<\/th> rtsp:\/\/ (plain)<\/th> RTSP over TLS (manual)<\/th> ONVIF :80<\/th><\/tr><\/thead> On<\/strong> (default)<\/td>Fails (port speaks TLS now)<\/td> Works (self-signed cert, TLS 1.2)<\/td> Works (unaffected)<\/td><\/tr> Off<\/strong><\/td>Streams video<\/td> N\/A<\/td> Works<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nThe camera needs about 30 seconds to apply the change – the RTSP service restarts internally. After a factory reset, TLS is re-enabled by default, so you will need to disable it again.<\/p>\n\n\n\n
Important nuance:<\/strong> TLS does not actually kill the RTSP service – it switches port 554 from plain RTSP to RTSP-over-TLS. The camera presents a self-signed TLS 1.2 certificate and responds to standard RTSP commands (OPTIONS, DESCRIBE, SETUP) inside the TLS tunnel. The problem is that ffmpeg\/ffprobe\/VLC cannot complete the TLS handshake with rtsps:\/\/<\/code> URLs on this camera. A custom TLS client connecting to port 554, performing the TLS handshake, and then speaking RTSP with Digest auth works perfectly. So if you are building a custom integration, you can leave TLS on for encrypted local streams.<\/p>\n\n\n\nYou can also toggle this programmatically via the Imou Open Platform API if you have registered a developer app:<\/p>\n\n\n\n
# Via the Open Platform API\nPOST \/openapi\/setDeviceCameraStatus\n{\n \"params\": {\n \"token\": \"YOUR_ACCESS_TOKEN\",\n \"deviceId\": \"YOUR_DEVICE_ID\",\n \"enableType\": \"tlsEnable\",\n \"enable\": false\n }\n}<\/pre>\n\n\n\nStep 2: Find the credentials<\/h2>\n\n\n\n The local password is the app password<\/strong> you set during Imou Life setup (including the AB suffix). The safety code printed on the camera label is just the factory default – once you change the password in the app, the safety code stops working:<\/p>\n\n\n\n\nSafety code<\/strong> (printed on camera) -> used for local ONVIF and RTSP access<\/li>\n\n\n\nApp password<\/strong> (set during setup) -> used only for cloud\/P2P access via the Imou Life app<\/li>\n<\/ul>\n\n\n\nThe username is always admin<\/code>.<\/p>\n\n\n\nStep 3: The RTSP URLs<\/h2>\n\n\n\n The Cruiser Dual has two lenses, each with a main stream (H.265, full resolution) and a sub stream (H.264, 640×480). The URL pattern follows the Dahua convention:<\/p>\n\n\n\n
# Lens 1 (PT \/ Pan-Tilt) - Main stream: H.265 2880x1620 @ 15fps\nrtsp:\/\/admin:SAFETY_CODE@CAMERA_IP:554\/cam\/realmonitor?channel=1&subtype=0\n\n# Lens 1 (PT) - Sub stream: H.264 640x480 @ 15fps\nrtsp:\/\/admin:SAFETY_CODE@CAMERA_IP:554\/cam\/realmonitor?channel=1&subtype=1\n\n# Lens 2 (Fixed wide) - Main stream: H.265 2304x1296 @ 15fps\nrtsp:\/\/admin:SAFETY_CODE@CAMERA_IP:554\/cam\/realmonitor?channel=2&subtype=0\n\n# Lens 2 (Fixed) - Sub stream: H.264 640x480 @ 15fps\nrtsp:\/\/admin:SAFETY_CODE@CAMERA_IP:554\/cam\/realmonitor?channel=2&subtype=1<\/pre>\n\n\n\nVerify with ffprobe:<\/p>\n\n\n\n
ffprobe -rtsp_transport tcp \"rtsp:\/\/admin:SAFETY_CODE@CAMERA_IP:554\/cam\/realmonitor?channel=1&subtype=0\"<\/pre>\n\n\n\nAll four streams include AAC audio at 16 kHz mono, 64 kbps.<\/p>\n\n\n\n
Note:<\/strong> The h264Preview_01_main<\/code> URL style that works on some Dahua cameras does not work on Imou firmware. Stick with cam\/realmonitor<\/code>.<\/p>\n\n\n\nDual lens architecture<\/h2>\n\n\n\n Understanding the channel mapping is important for integration:<\/p>\n\n\n\n<\/th> Channel 1 (PT lens)<\/th> Channel 2 (Fixed lens)<\/th><\/tr><\/thead> Type<\/strong><\/td>Pan-Tilt motorized<\/td> Fixed wide-angle<\/td><\/tr> Max resolution<\/strong><\/td>2880×1620<\/td> 2304×1296<\/td><\/tr> Main codec<\/strong><\/td>H.265\/HEVC<\/td> H.265\/HEVC<\/td><\/tr> Sub codec<\/strong><\/td>H.264 Main<\/td> H.264 Main<\/td><\/tr> PTZ<\/strong><\/td>Yes (8 presets)<\/td> No<\/td><\/tr> ONVIF source<\/strong><\/td>VideoSource000<\/td> VideoSource100<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nBoth lenses share a single audio source (AudioSource000, mono).<\/p>\n\n\n\n
ONVIF: what works locally<\/h2>\n\n\n\n Beyond RTSP, the camera exposes a full ONVIF interface on port 80. You can:<\/p>\n\n\n\n
\nStream video<\/strong> – all 4 profiles (2 lenses x 2 quality levels)<\/li>\n\n\n\nTake snapshots<\/strong> – channel 1 only (channel 2 returns HTTP 400)<\/li>\n\n\n\nControl PTZ<\/strong> – pan, tilt on lens 1 with 8 configurable presets<\/li>\n\n\n\nChange encoder settings<\/strong> – resolution, codec, bitrate, framerate, GOP length<\/li>\n\n\n\nAdjust imaging<\/strong> – brightness, contrast, sharpness, IR cut filter (both lenses)<\/li>\n\n\n\nControl night vision (partial)<\/strong> – IR cut filter via ONVIF Imaging: ON (force color), OFF (IR\/B&W), AUTO (auto-switch). Maps to 3 of the 4 cloud modes. The cloud’s “Intelligent” mode adds white LED coordination that ONVIF alone cannot replicate<\/li>\n\n\n\nConfigure motion detection<\/strong> – CellMotionDetector zones, sensitivity, alarm on\/off delays (read and write via ONVIF analytics rules)<\/li>\n\n\n\nSubscribe to events<\/strong> – PullPoint subscriptions deliver real-time MotionAlarm, TamperDetector, GlobalSceneChange, and CellMotionDetector events locally (requires WS-Addressing headers)<\/li>\n\n\n\nManage users<\/strong> – CreateUsers and DeleteUsers both work via ONVIF. The camera supports up to 31 users<\/li>\n\n\n\nWS-Discovery<\/strong> – camera responds on UDP 3702<\/li>\n<\/ul>\n\n\n\nWhat you cannot<\/strong> do locally: access SD card recordings (Recording\/Search\/Replay services all return “not implemented”), configure WiFi (Dot11 methods not implemented), toggle AI human\/vehicle detection, control the white light or siren (no relay outputs exposed), or manage the 30+ camera switches. Those features require the cloud API.<\/p>\n\n\n\nHome Assistant integration<\/h2>\n\n\n\nOption 1: ONVIF integration (recommended)<\/h3>\n\n\n\n Settings -> Integrations -> Add -> ONVIF:<\/p>\n\n\n\n
\nHost:<\/strong> your camera IP<\/li>\n\n\n\nPort:<\/strong> 80<\/li>\n\n\n\nUsername:<\/strong> admin<\/li>\n\n\n\nPassword:<\/strong> your safety code<\/li>\n<\/ul>\n\n\n\nThis gives you 4 camera entities (2 lenses x 2 streams), PTZ controls, and motion detection events – all local, no cloud dependency.<\/p>\n\n\n\n