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

Enabled setting "Force 802.11g mode (ESP8266 only)" lost after reboot #3665

Closed
1 task done
trfrde opened this issue Jan 9, 2024 · 5 comments
Closed
1 task done
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@trfrde
Copy link

trfrde commented Jan 9, 2024

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

  • I agree to follow this project's Code of Conduct
@trfrde trfrde added the bug label Jan 9, 2024
@blazoncek
Copy link
Collaborator

You may want to disable fast roaming and BSS transition in UniFi.

@blazoncek
Copy link
Collaborator

And please post your configuration (cfg.json)

@softhack007 softhack007 added the confirmed The bug is reproducable and confirmed label Jan 10, 2024
@softhack007
Copy link
Collaborator

softhack007 commented Jan 10, 2024

I was able to reproduce the problem, with MS EDGE on windows, and using an 8266 freshly installed with wLED.

  • go into Wifi settings, check "Force 802.11g mode". Just for comparison, i've also checked "disable wifi sleep".
  • save & connect
  • go back into Wifi settings -> Ok -> checkmarks are there
  • look at cfg.json -> ok -> contains "wifi":{"sleep":false,"phy":1}
  • open info panel, press "reboot"
  • after reboot, look into wifi settings --> NOK -> checkmark missing for "Force 802.11g mode" (checkmark "disable sleep" is still there)
  • cfg.json still correct: "wifi":{"sleep":false,"phy":1}

@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?

@softhack007 softhack007 changed the title Enabled setting "Force 802.11g mode (ESP8266 only)" not saved during reboot Enabled setting "Force 802.11g mode (ESP8266 only)" lost after reboot Jan 10, 2024
@blazoncek
Copy link
Collaborator

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 | operator handles it properly.

Try changing the line 698 to read:

  wifi[F("phy")] = (bool)force802_3g;

and re-save configurations.

blazoncek added a commit that referenced this issue Jan 10, 2024
blazoncek added a commit that referenced this issue Jan 10, 2024
@blazoncek blazoncek added the fixed in source This issue is unsolved in the latest release but fixed in master label Jan 10, 2024
@softhack007
Copy link
Collaborator

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 "wifi":{"sleep":false,"phy":true} as it should be.

softhack007 pushed a commit to MoonModules/WLED that referenced this issue Jan 10, 2024
@blazoncek blazoncek added this to the 0.14.1 candidate milestone Jan 15, 2024
Djelibeybi pushed a commit to Djelibeybi/WLED-MM that referenced this issue Jan 15, 2024
DedeHai pushed a commit to DedeHai/WLED that referenced this issue Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master
Projects
None yet
Development

No branches or pull requests

3 participants