I would like to propose an optional enhancement to the WiFi provisioning flow.
At the moment, after the user enters the WiFi password and the device successfully joins the target network, the transition is very brief and does not provide enough usable information for non-technical users. In practice, many users still need to identify the device in their DHCP server or router in order to assign a fixed IP address.
A helpful improvement would be an optional post-provisioning step that presents network identification details in a user-friendly way.
Requested behavior
After successful WiFi provisioning, the library could optionally:
- connect to the target WiFi network as usual,
- wait until a DHCP lease has been obtained,
- capture the assigned IP address,
- temporarily present a confirmation page that shows:
- the MAC address of the device,
- the DHCP-assigned IP address,
- keep that information visible until the user confirms,
- then continue into normal operation.
Why this would help
This would make first-time setup much easier for normal users, especially in installations where a fixed DHCP lease is recommended.
The MAC address is useful for creating a reservation in the router, and the DHCP IP is useful for directly opening the device after setup.
Right now, this step is difficult for users who do not know how to inspect DHCP leases or match the correct device manually.
Important note
This should ideally be implemented as an optional feature, so that existing users who prefer the current fast provisioning flow are not affected.
Possible API idea
This could be exposed as an optional configuration flag or callback-based post-provisioning page, for example:
- enable post-provisioning info page
- provide custom renderer or custom message block
- allow showing MAC address and local IP
Use case
This is especially useful for embedded devices that expose a local web UI after provisioning and are intended to be reachable under a stable local IP address.
I would like to propose an optional enhancement to the WiFi provisioning flow.
At the moment, after the user enters the WiFi password and the device successfully joins the target network, the transition is very brief and does not provide enough usable information for non-technical users. In practice, many users still need to identify the device in their DHCP server or router in order to assign a fixed IP address.
A helpful improvement would be an optional post-provisioning step that presents network identification details in a user-friendly way.
Requested behavior
After successful WiFi provisioning, the library could optionally:
Why this would help
This would make first-time setup much easier for normal users, especially in installations where a fixed DHCP lease is recommended.
The MAC address is useful for creating a reservation in the router, and the DHCP IP is useful for directly opening the device after setup.
Right now, this step is difficult for users who do not know how to inspect DHCP leases or match the correct device manually.
Important note
This should ideally be implemented as an optional feature, so that existing users who prefer the current fast provisioning flow are not affected.
Possible API idea
This could be exposed as an optional configuration flag or callback-based post-provisioning page, for example:
Use case
This is especially useful for embedded devices that expose a local web UI after provisioning and are intended to be reachable under a stable local IP address.