Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Captive portal redirect stop working #232

Closed
Andreadj opened this issue Nov 22, 2024 · 1 comment
Closed

Captive portal redirect stop working #232

Andreadj opened this issue Nov 22, 2024 · 1 comment

Comments

@Andreadj
Copy link

Hi everybody,
maybe somebody can help me find a solution.
I have a led lamp with esp32 that start in AP mode and I control it with my phone. If I want to control it with Alexa I connect it on the LAN where Alexa is connected. Everything works well, Captive portal in AP and in Station mode is always visible and usable but I have a problem:
When I instlalled Espalexa my Captive portal redirect when connecting to AP is no more working. I think it depends on server.onNotFound function that can't work togheter with Alexa... If I use Captive's one before, Alexa won't works, if I use Alexa's one before, Captive isn't redirected when connected to AP.
Is there a way to have Alexa and the Captive portal redirect working at the same time? Since Alexa works exclusively under network and I only need the redirect in AP mode, is there a way to make espAlexa server only start in Station mode without using server.onNotFound function?

Thanks

@Andreadj
Copy link
Author

Found the way to load Espalexa's "server.onNotFound" only in Station mode with a WiFi.getMode
;-)

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

No branches or pull requests

1 participant