Skip to content

fix: verify M5Burner publication state - #6

Merged
DrDavidDa merged 3 commits into
mainfrom
agents/sync-with-latest-github-repo
Sep 14, 2026
Merged

DrDavidDa merged 3 commits into
mainfrom
agents/sync-with-latest-github-repo

Conversation

@DrDavidDa

@DrDavidDa DrDavidDa commented Sep 14, 2026 •

Copy link
Copy Markdown
Owner

Handle M5Burner API 400 responses for already-published versions and verify the authoritative version list before reporting success.


Note

Medium Risk
Large firmware changes to WiFi boot path, credential persistence (NVS/SD), and an always-on HTTP/DNS stack during setup; publish script changes affect release automation but not device runtime beyond new binaries.

Overview
Adds phone-first WiFi provisioning on the device: SoftAP PaperColor-XXXXXX, captive portal at http://192.168.4.1, scan/save/connect flow, on-screen QR (ricmoo/QRCode), and credentials in NVS + optional SD config.ini (script #CFGDONE clears NVS so SD wins). Entry via boot with no creds, QR page long-press B, or serial #WIFIAP; C = offline mode persisted in NVS.

Boot behavior now sets wifiReconnectPending when stored creds exist (so it connects without waiting for standby wake); otherwise auto-starts setup unless offline mode is set. Main loop blocks standby/reconnect/polling while wifiSetupActive.

Docs/onboarding: docs/m5burner-quick-start.md, config.ini.example, README/CHANGELOG emphasize M5Burner burn → phone setup (SD optional).

publish_m5burner.py: bumps to v3.1.0, uploads a new firmware version when the listed version differs (update_firmware), treats publish 400 as OK if the firmware list shows the version already published, and updates store copy for phone provisioning.

Reviewed by Cursor Bugbot for commit 80085b2. Bugbot is set up for automated code reviews on this repo. Configure here.

Add a beginner-friendly phone provisioning guide and a verified SD config template. Clarify offline use, SD card paths, file naming, and the fact that M5Burner does not configure WiFi automatically.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Prepare the publisher for v3.1.0 and describe the phone provisioning flow.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Handle the API response where an already-published version returns HTTP 400, and verify the authoritative version list before reporting success.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@DrDavidDa
DrDavidDa merged commit 5011755 into main Sep 14, 2026
1 check passed
@cursor

cursor Bot commented Sep 14, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4a5a13e9-94cd-46c0-bfc3-7415bd5faee9)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant