@ElektrodaBot From which version is ota_http available?
Initial assessment The string “ota_http” is not a generic API name; in practice it refers to: - an OpenBeken console/MQTT command that triggers an OTA update from a given HTTP URL, and - unrelated SDKs also talk about “OTA over HTTP,” but they don’t expose a command literally called ota_http.
Given the Tasmota-like command style and the common usage on Elektroda, your question is almost certainly about OpenBeken.
Direct answer - OpenBeken: the ota_http command has been present in public builds since at least the 1.15–1.16 series and is documented and in active use in current 1.17/1.18 releases. A widely used example of its syntax appears in the OpenBeken provisioning tutorial (cmnd/<topic>/ota_http <URL>), and the command is listed in the project’s Commands docs. (elektroda.com)
If you meant another platform, please say which one (ESP-IDF, AWS FreeRTOS, etc.), because the answer differs and the identifier “ota_http” is not used there as a function name.
Detailed analysis - Evidence of availability and usage - The OpenBeken provisioning guide shows the exact command form: topic: cmnd/BK7321N/ota_http payload: http://server/fw.rbl This article (published well before the 1.18 line) demonstrates that ota_http existed and was intended for bulk updates via MQTT, implying availability at least in the 1.15–1.16 timeframe. (elektroda.com) - The command is part of the “Commands” documentation in the OpenBeken repository (commands/commands-extended), which is kept alongside current releases. While release notes do not always call out individual console commands, the docs confirm the command’s presence in supported builds. (github.com)
- Why you may see conflicting answers about the “first” version - OpenBeken publishes very frequent tags; some additions land between tags and get pulled into the next roll-up release. Minor console commands often don’t get explicit “Added in vX.Y.Z” notes, so the cleanest way to confirm on a device is to run help in the console or try the command: - Web UI → Console: type ota_http ? (or consult the Commands page linked from the firmware’s About page). - Or send a dry run via MQTT to a test device and read the log.
Current information and trends - As of mid-November 2025, ota_http is still the recommended headless/bulk method for updating OpenBeken nodes via MQTT (group topics), and it coexists with the Web UI OTA panel (drag-and-drop .rbl). The tutorial shows the intended bulk-update pattern for Home Assistant users. (elektroda.com)
Supporting explanations and details - What ota_http does - It instructs the device to fetch a .rbl image from an HTTP server and flash it to the inactive OTA slot. When used over MQTT with a group topic, it enables fleet updates in one go. (elektroda.com) - Where to find it in docs - OpenBeken repo docs: commands / commands-extended contain the console/MQTT command set, including ota_http. (github.com)
Practical guidelines - Verifying on your device - From the device Web UI → Console: run help and scan for ota_http (or try ota_http ?). - From MQTT, publish a test to a single device rather than a group to confirm behavior before bulk updates (e.g., cmnd/<DeviceName>/ota_http http://host/fw.rbl). (elektroda.com) - Safety - Ensure the .rbl matches the chip family (T vs N) and that the device has sufficient free space; mismatched or oversized images will be rejected by the OTA logic. The project docs emphasize using the correct .rbl artifact. (elektroda.com)
Brief summary - In OpenBeken, ota_http has been available since at least the 1.15–1.16 series and remains supported in current releases; it’s documented in the Commands pages and demonstrated in the official provisioning tutorial. (elektroda.com)
Questions for you - Can you confirm you mean OpenBeken (not ESP-IDF or AWS FreeRTOS)? If yes, which exact firmware version is on your device now (from the About page), and on which chip (BK7231T/N)? With that, I can tell you definitively whether ota_http is present in your build and provide an example tailored to your setup.
You can call me in any topic by writing @ElektrodaBot. Disclaimer: Some answers provided by the ElektrodaBot may be inaccurate. Elektroda not responsible for accuracy, reliability or completeness of the information presented. All ElektrodaBot responses should be verified by the user. OpenAI can monitor and save information entered after calling ElektrodaBot.
Initial assessment of available information - Your device reports OpenBeken build OpenBK7231N_1.18.125. In this branch the OTA-over-HTTP command ota_http is present and supported. It has been publicly documented and demonstrated since at least the 1.15.576 builds. (elektroda.com) - The most recent tagged release today (November 15, 2025) is 1.18.211; a BK7231N .rbl image is provided in that release. (github.com)
Direct answer to your original question - ota_http availability: Confirmed in OpenBeken since at least 1.15.576 and therefore included in your 1.18.125 build. (elektroda.com)
Detailed problem analysis Why an OTA attempt from 1.18.125 might “not update to most recent”:
1) Image/URL mismatch - Wrong platform file (e.g., OpenBK7231T_…rbl on a BK7231N device) is rejected by the updater. Always use the N image for BK7231N. (elektroda.com) - Indirect or webpage URLs won’t work. Use a direct asset link to the .rbl file or serve the .rbl from a simple HTTP server on your LAN. The project’s own examples use plain HTTP to a local server. (elektroda.com)
2) MQTT topic or GroupTopic issues - If you trigger via MQTT, confirm you are publishing to the device’s actual cmnd/<DeviceName>/… or to the defined GroupTopic. A wrong topic silently does nothing; after setting GroupTopic a reboot is required before group commands are accepted. (elektroda.com)
3) Configuration side effects - Rarely, specific flag sets or autoexec.bat contents can interfere with the OTA flow. If you suspect this, temporarily comment out nonessential startup commands and retry. A prior case involved OTA failing until configuration was adjusted. (elektroda.com)
4) Network/transport details - If the device cannot reach the server or the download is interrupted, the firmware stays unchanged. Use the device Web UI “Log” view while triggering OTA; you should see sequential OTA:… progress entries followed by a reboot. If you do not see these, the URL or connectivity is the root cause. (elektroda.com)
5) Attempting a “no-change” update - If you OTA the same version you already run, you will still reboot back into the same reported version. Verify the target version string in the asset name before you start.
Current information and trends - Latest release: 1.18.211 published on November 14, 2025; assets include OpenBK7231N_1.18.211.rbl. As usual, do not mass-flash alpha builds; test on one device first. (github.com)
Supporting explanations and details - What ota_http does: it fetches an .rbl image over HTTP and writes it to the OTA slot; after download/verification the device reboots into the new image. A working example and console transcript exist in the provisioning tutorial using an HTTP URL and a 1.15.x image; the same mechanism applies to newer versions. (elektroda.com) - Expected log: During a successful update, the log shows monotonically increasing OTA address offsets, then “close OTA” and a countdown to reboot. If you do not see this pattern, the fetch did not start or was aborted. (elektroda.com)
Practical guidelines Try the fastest, verifiable path below.
C) If you prefer the Web UI instead of a URL - Open device Web UI → OTA/Upgrade → upload the .rbl you downloaded for BK7231N. This path removes any dependency on external HTTP access and has been steadily improved over recent releases. (elektroda.com)
D) If you trigger via MQTT for fleet updates - Topic: cmnd/<DeviceName>/ota_http or cmnd/<GroupTopic>/ota_http - Payload: the full HTTP URL to the .rbl - Reboot devices after setting a new GroupTopic before sending a broadcast. (elektroda.com)
Checklist before retrying: - Confirm the file name exactly starts with OpenBK7231N_… and the version you intend (e.g., 1.18.211). (github.com) - If using MQTT, verify the topic with a known-good command first (e.g., Power Toggle) to prove delivery, then run ota_http. (elektroda.com) - Watch the Log for OTA:… progress. If it doesn’t start, paste the exact URL into a browser on the same Wi‑Fi to verify the file is accessible. (elektroda.com)
Ethical and legal aspects - As always, use only the correct image for your chip and update devices you own or administer; mismatched images can brick hardware and void regulatory approvals.
Possible disclaimers or additional notes - Alpha tags in releases indicate development builds—avoid pushing those to many devices at once. Test on a single node first. (github.com)
Suggestions for further research - If you continue to see failures, share the Console or MQTT log around the OTA attempt and the exact URL you used. We can correlate the error with known cases where flags/autoexec influenced OTA behavior. (elektroda.com)
Brief summary - ota_http is present in your 1.18.125 build and has been available since at least 1.15.576. The latest release as of November 14–15, 2025 is 1.18.211; use the BK7231N .rbl and a direct URL or a local HTTP server, verify the MQTT topic if used, and monitor the Log for OTA progress/reboot. (elektroda.com)
Questions for you - How exactly did you trigger the update (console vs MQTT vs UI)? - What URL did you pass to ota_http? - Can you paste the Console/Log lines from the moment you start OTA until it returns to idle? - Do you have a GroupTopic configured, and did you reboot after setting it? (elektroda.com)
With those details I can pinpoint why your 1.18.125 unit didn’t advance to 1.18.211 and give a step-by-step fix.
You can call me in any topic by writing @ElektrodaBot. Disclaimer: Some answers provided by the ElektrodaBot may be inaccurate. Elektroda not responsible for accuracy, reliability or completeness of the information presented. All ElektrodaBot responses should be verified by the user. OpenAI can monitor and save information entered after calling ElektrodaBot.
