I have the same issue with two IMOU cameras (IPC-S21FE Cruiser SE+ and Ranger 2C-L) on iHost v2.9.0. Both are detected automatically during ONVIF discovery, but adding them always fails with “No response, please try again” after ~30 seconds. I also tried adding them via RTSP — same result.
After digging into the iHost logs, I found the root cause. In aibridge-api.log, every attempt shows this pattern:
POST /api/v1/rest/devices/camera
mqtt publish → camera/system/create
200:500 "30039ms" ← TIMEOUT after exactly 30s
...
Received MQTT on 'camera/system/created' ← arrives ~105s later!
The streamapp service does eventually connect to the camera, but the response arrives 45–105 seconds after the request — well past iHost’s 30-second timeout. So iHost returns a 500 error and discards the result.
For reference, ONVIF Device Manager (ODM) connects to the same cameras perfectly fine using admin + the SC-Code printed on the camera. The RTSP stream also works in VLC. The problem is purely the 30s timeout in iHost being too short for IMOU/Dahua cameras.
Is anyone else experiencing this? I think increasing the timeout to 60–90s would fix it. I will report this as a bug to the eWeLink team with the full logs.
Hello, we sincerely apologize for the inconvenience caused. To help our technical team pinpoint the issue more accurately, could you please provide the device IDs of the two IMOU cameras? Additionally, please submit feedback through the iHost local web page and be sure to upload the relevant logs – this will provide key information for our in-depth analysis. Thank you for your cooperation!
ONVIF version: 20.06
(Device ID to be confirmed — I will check in ONVIF Device Manager)
iHost
Firmware version: 2.9.0
I have already submitted feedback through the iHost local web page with the relevant logs attached.
For reference, here is what I found in the logs that may help your team:
In aibridge-api.log, every camera add attempt (both ONVIF and RTSP) times out after exactly 30 seconds with a HTTP 500 error. However, the streamapp service does eventually connect to the camera and sends back a camera/system/created response — but it arrives 45 to 105 seconds after the initial request, which is too late.
This suggests the 30-second timeout in iHost is too short for IMOU/Dahua cameras, which require more time to complete the ONVIF handshake.
Please let me know if you need any additional information.
Hello, thank you for providing such detailed information and logs! We have received them and will arrange for our technical team to analyze and address the issue as soon as possible. Please bear with us – we will keep you updated as soon as there is any progress. Thank you again for your patience and support!
Hello, we sincerely apologize for the inconvenience caused.
We have analyzed the logs you submitted and confirmed that this is a known issue. It will be fixed in version eWeLink Cube v2.10.0, which is expected to be released around mid-April.
Thank you again for your support and understanding.