esphome / esphome/feature-requests

Captive Portal and/Or Access Point on demand

Open
#2,676 9 comments 9 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**
Add the possibility to start the `captive_portal` on demand from the `web_server` or even a GPIO pin.
Add the possibility do deactivate the `captive_portal` and start the `web_server` form the `captive_portal`
Make it possible to disconnect from a wifi network an start the ap with eighter the `web_server` or the `captive_portal`

**Please describe your use case for this integration and alternatives you've tried:**
Once you connected the device to a wifi network using the camptive portal there is no way to change to a different wifi network without shutting down the wifi the ESP is curently connected to, to force a start ot the ap and the captive portal.
Once connected to a wifi there is alo on way to make the device standalone anymore with using the ap insetead of connected to the wifi

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified in the request. Clarify the supported device behavior and the entry points for switching between the Wi-Fi connection, access point, web server, and captive portal before implementation; done should cover the requested transitions and their GPIO or web-server triggers.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.