iHost 2.12.0 cannot download firmware 2.13.1 – Range request error

eWeLink CUBE
,
1

iHost 2.12.0 cannot download firmware 2.13.1 – Range request error

My SONOFF iHost is currently running 2.12.0 and is being offered firmware 2.13.1, but the OTA update consistently fails at the very beginning of the firmware download.

The OTA API successfully responds with HTTP 200 and identifies 2.13.1 as available. It provides this firmware URL:

global-otadl3.coolkit.cc/.../IHOST_PROD_1786539125.img

However, the downloader repeatedly fails with:

CreateWriteStreamException: FileDownloader error: origin不能进行范围请求处理, 暂不支持该类型的资源服务器。

This approximately translates as:

“The origin cannot process Range requests; this type of resource server is currently unsupported.”

The failure occurs repeatedly rather than being a transient connection problem. The logs suggest that the iHost downloader expects the firmware server to support HTTP byte-range requests, but the firmware CDN endpoint is not responding as expected.

The OTA metadata requests themselves work normally with HTTP 200 responses, and there are no indications of DNS failure, TLS failure, timeout, connection refusal, disk-full, or checksum problems. The process appears to fail before the firmware image is actually downloaded.

Can anyone please check:

  1. Whether the 2.13.1 firmware image at global-otadl3.coolkit.cc currently supports HTTP Range requests.
  2. Whether there is a CDN/origin configuration problem affecting IHOST_PROD_1786539125.img.
  3. Whether the iHost 2.12.0 downloader is compatible with the way this firmware is currently being served.

This looks potentially like a firmware CDN/hosting issue rather than an iHost hardware or storage problem.

I can provide the full diagnostic archive privately if required, but I have not attached it here because the logs contain account/device and authentication-related information.

Thanks!

2

Hello,
Thank you for your feedback. We apologize for any inconvenience this may have caused. Could you please try again to see if the update can complete successfully?

3

Thank you for the incredibly rapid response.

As luck would have it the release of 2.13.1 on the server side seems to have solved the issue, as the ihost has just now successfully updated!