mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 00:55:52 +03:00
[GH-ISSUE #1846] PoC "Wizard" portal flow #1549
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#1549
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eimermusic on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1846
I have a fork where I added a "Wizard-like" (step-by-step or linear) flow for the WiFiManager portal.
I wanted to post here to gauge if there is any broader interest.
I have implemented it to be compatible alongside existing functionality but nothing has been tesed for regressions yet.
This simple implementation works like this:
If Wifi is connected, it jumps straight to custom parameter setup.
There is a simple "progress" dialog while verifications are happening.
This functionality works well for me and is great for setting up wifi + API credentials and having all of it verified before closing the config portal.
No support for any of the other features (erase, info...) simply because I have no need for them myself.
https://github.com/eimermusic/WiFiManager
@tablatronix commented on GitHub (Jan 26, 2026):
nice I always thought it would be nice like that, but wound up just maintaining the project instead of making UI changes.
Got any screenshots
@eimermusic commented on GitHub (Feb 2, 2026):
Sorry for the delay. Here are some screenshots from my phone connecting to the portal. The custom parameter verification has a similar spinner and success / fail screen as the wifi step.
And after filling in those parameters there is spinner and success screen.
The parameter verification has active wifi available to verify the API credentials for real.
Skip and Back are the questionably named buttons to go back and forth in the "wizard".