-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Enabled setting "Force 802.11g mode (ESP8266 only)" lost after reboot #3665
Comments
You may want to disable fast roaming and BSS transition in UniFi. |
And please post your configuration (cfg.json) |
I was able to reproduce the problem, with MS EDGE on windows, and using an 8266 freshly installed with wLED.
@blazoncek very mysterious behaviour - "disable sleep" is still there after reboot, but "force g mode" is lost. The only suspicious part is that "sleep" is stored with true/false value, while "phy" is stored as 0/1. Any idea? |
On first look everything seems in order. force802_3g = doc[F("wifi")][F("phy")] | force802_3g; //force phy mode g? and wifi[F("phy")] = (int)force802_3g; But now I wonder if Try changing the line 698 to read: wifi[F("phy")] = (bool)force802_3g; and re-save configurations. |
Confirmed - works for my case, too 👍 cfg.json now has |
What happened?
I have several D1 mini 8266 devices, which had connection problems (using an UniFi access point). The newly introduced setting "Force 802.11g mode (ESP8266 only)" does seem to solve the issue, thank you! Unfortunately, the setting is not saved during reboot. After a soft or hard reboot, the devices connect using the WiFi 4 standard (and not the WiFi 3 when activating the option).
To Reproduce Bug
Activate the setting "Force 802.11g mode (ESP8266 only)"
Reboot
Setting "Force 802.11g mode (ESP8266 only)" not activated any more
Expected Behavior
Settings "Force 802.11g mode (ESP8266 only)" keeps activated.
Install Method
Binary from WLED.me
What version of WLED?
0.14.1-b3 build 2401060
Which microcontroller/board are you seeing the problem on?
ESP8266
Relevant log/trace output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: