OTA through the relay stops after 64 KB
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, python
- Domain
- embedded-iot
Research direction
Connect the panel over USB and run tools/mon.py --seconds 120 --no-reset during an OTA attempt. Read the [ota] lines printed by otaFrom, especially http, size, begin failed, and reject total=... match=...; use those readings to narrow down why the download stops. Done means the panel completes the OTA and installs the firmware.
Written by the indexing model from the issue text.
Description
publish_fw.sh can't ship firmware right now: the panel takes the ota op, starts the download, and hangs up after 65,536 of 1,153,312 bytes. It goes back to streaming on the old build, so nothing breaks, but nothing installs either.
From nginx on the relay host, second attempt (2026-10-22, times EDT):
03:26:59 GET /pxt/stream 200 stream closes, op received
03:27:01 GET /pxt/fw 200 65536 B "ESP32HTTPClient"
03:27:03 stream reconnects on the same build, uptime still counting (no reboot)
The first attempt never reached nginx at all. The stream closed and reconnected two seconds later with no /pxt/fw request logged, which points at the TLS connect in otaFrom.
Ruled out:
- A short read timeout.
HTTPClient::setTimeoutpasses milliseconds through (HTTPClient.cpp:479in the pinned core), sohttp.setTimeout(20000)is 20 s, and the hang-up came within about a second. - The relay. A
curlof/pxt/fwthrough the same nginx got all 1,153,312 bytes.
The next step needs the panel on USB: run tools/mon.py --seconds 120 --no-reset during an attempt and read the [ota] lines otaFrom prints (http, size, begin failed, reject total=... match=...). Until then, flash over USB with tools/flash_serial.py, or from the panel's access point with tools/onboard.sh.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 40m
- Merged PRs (30d)
- 14
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from STRML/pixoticker
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
STRML/pixoticker#16 ·
Maintainers usually reply within 1 day
All issues in STRML/pixoticker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
alltheplaces/alltheplaces#20570 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
area:ci bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
catincloud-labs/dagster-dex#206 · 1 comment ·
Maintainers usually reply within 1 day
-
number_to_words raises ValueError with threshold= for ordinals ("12th") and comma-grouped strings ("1,000")Possibly taken @hemtilva claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
providers security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agentbreeder/agentbreeder#1031 ·
Maintainers usually reply within 1 day