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

MDNS doesn't work when AP is set to always on #2496

Closed
1 task done
Ethan-C-Honzik opened this issue Jan 19, 2022 · 7 comments
Closed
1 task done

MDNS doesn't work when AP is set to always on #2496

Ethan-C-Honzik opened this issue Jan 19, 2022 · 7 comments
Labels

Comments

@Ethan-C-Honzik
Copy link

What happened?

If you set the AP opens behavior to Always MDNS doesn't work meaning the device can't be discovered by the wled app.

To Reproduce Bug

Connect esp to WiFi, turn AP opens to always, observe that MDNS stops working.

Expected Behavior

MDNS should work on the connected wifi network when the AP opens setting is set to always on.

Install Method

Binary from WLED.me

What version of WLED?

0.12.0

Which microcontroller/board are you seeing the problem on?

ESP8266

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@blazoncek
Copy link
Collaborator

This has been discussed elsewhere (can't recall issue # or location) but has been decided it is unresolvable with the TCP stack on ESP.
If you want to have mDNS then do not enable persistent AP mode.

@Ethan-C-Honzik
Copy link
Author

good to know. It's probably worth noting this in the UI if it can't be fixed.

@blazoncek
Copy link
Collaborator

you may want to try 0.13-b6 which has newer ESP core if there are any changes.

@stale
Copy link

stale bot commented Jul 10, 2022

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs.
Thank you for using WLED!

@stale stale bot added the stale This issue will be closed soon because of prolonged inactivity label Jul 10, 2022
@jmerc77
Copy link

jmerc77 commented Jul 21, 2023

noticing a similar issue with 0.14.0-b1 hoshi. running a custom compiled version on the esp32-s3 (no code changes, just compiler configs). i say "similar" as it works fine on a desktop pc running a chromium based browser (brave in my case) or stock chrome. but never on my phone. on the phone it doesn't work in the app or any of the browsers (not even chrome/chromium based). in all cases, the dhcp assigned ip works fine as long as you know the ip. though, have not verified if changing away from always open fixes it or not because i dont know which one to pick that will still allow an ap connection regardless of weather the router is still connected or not.

@stale stale bot removed the stale This issue will be closed soon because of prolonged inactivity label Jul 21, 2023
@jmerc77
Copy link

jmerc77 commented Jul 21, 2023

well, well, well. seems to not have been a WLED problem. apparently, it works now for me after noticing my phone all of the sudden refused to connect to the router. which then i reset the router, before the reset fully took place it started working! i then had to wait for the router to reset afterwards but still worked once everything was back online. the version i was using is 2 betas old but they somehow fixed this issue on or before the version i'm using (0.14.0-b1 hoshi, latest at this time is 0.14.0-b3).

btw, as long as you upgrade to latest, it seems it is now fixed and this issue can now be closed. i am not authorized to do so. all i can do is make the suggestion and hope someone listens.

@softhack007
Copy link
Collaborator

Seems like the issue can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants