Skip to content

chore: align M5Burner release metadata - #5

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

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

Conversation

@DrDavidDa

@DrDavidDa DrDavidDa commented Sep 14, 2026 •

Copy link
Copy Markdown
Owner

Align publish_m5burner.py with v3.1.0 and document phone provisioning in M5Burner metadata.


Note

Medium Risk
Large firmware change to WiFi boot path, credential storage (NVS/SD), and always-on HTTP/DNS during setup; misconfiguration or portal bugs could block connectivity until user re-enters setup.

Overview
Adds on-device WiFi provisioning so users can configure network from a phone without a PC: SoftAP hotspot PaperColor-XXXXXX, captive portal at http://192.168.4.1, scan/select SSID, status polling, on-screen QR (new ricmoo/QRCode dep). Entry via first boot with no creds, QR page long-press B, or serial #WIFIAP; optional offline mode (C key) persisted in NVS.

Credentials are stored in NVS and synced to SD config.ini; #CFGDONE / script full writes clear NVS so SD stays authoritative. Boot behavior now sets wifiReconnectPending when creds exist (fixes “won’t connect until wake”) and auto-starts setup when none exist.

Docs/release: docs/m5burner-quick-start.md, config.ini.example, README/CHANGELOG updates; publish_m5burner.py bumped to v3.1.0 with M5Burner copy describing phone provisioning.

Reviewed by Cursor Bugbot for commit fa0c990. 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>
@DrDavidDa
DrDavidDa merged commit e1a40d8 into main Sep 14, 2026
@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_95cfc313-a7f8-42fa-81d0-4a64a7509ec0)

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