-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/api/device/otaFlash not found #102
Comments
Tried different web server(docker image, apache,nginx) but result Is the same. I'm using the hotspot smartphone network. |
I am experiencing the same issue... Sonoff Mini2, 3.6 firmware.. nginx in docker... |
I had exactly the same issue. Like me you must have been trying to flash tasmota.bin. The solution is to flash tasmota-lite.bin instead. I think that there is a check in firmware 3.6.0 that file size of firmware is < 500kb. |
I get same with lite file. Using nginx to host. |
I was having the same problem, turned out that in the HTTP post I was using a SHA256 with uppercase letters. Once I used the same hash with lowercase letters it flashed correctly. Sonoff Mini R2 with FW 3.6.0. |
Got it working by using a different Tasmota version. Everything same as before, but it seems that Tasmota 8.4.0 (Lite) flashed without any issues (I was using 9.2.0 before). The "/api/device/otaFlash not found" error is meaningless though. Flashed it successfully even with that error. I tried to create a new NGIX server with "api/device/otaFlash" POST endpoint, and no error occurring while flasiht, it still failed to flash with Tasmota 9.2.0. |
Same thing here, @jf2020 had the right solution - use tasmota-lite.bin. When it works, the sonoff will do tons of request like |
I have a sonoff mini (bought in 2019) in DIY mode running 3.6 firmware. I put successful in DIY mode with post request, when i try to reflash firmware i get this error "POST /api/device/otaFlash HTTP/1.1" 404 301 "-" "-"
Also this tool cannot see the sonoff mini.
Anyone able to reflash without soldering?
The text was updated successfully, but these errors were encountered: