mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #1209] AP Does Not Respect Bandwidth Directive #1031
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#1031
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lbussy on GitHub (Feb 10, 2021).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1209
Basic Infos
Hardware
WiFimanager Branch/Release: Master (I don't see a "development" branch in the list)
Esp32:
Hardware: ESP32-WROOM-32
Core Version: v3.2.3-14-gd3e562907
Description
When AP mode starts, it starts with 40MHz bandwidth and multiple channels. When I set the bandwidth and channel the code does not seem to respect the setting as determined by a spectrum analyzer:
Settings in IDE
Module: Lolin D32
Additional libraries: N/A
Sketch
Debug Messages
@tablatronix commented on GitHub (Feb 10, 2021):
Same, I looked into this before not sure if it was an esp bug or hardware bug.
@tablatronix commented on GitHub (Feb 10, 2021):
ok figured it out, let me see if i can work something ( i thought setcountry was able to set this )
@tablatronix commented on GitHub (Feb 10, 2021):
You have to use apcallback, needs to be set after starting ap
@lbussy commented on GitHub (Feb 10, 2021):
Hah! You had a fix for it all along. :)
Thank you, sir.
@tablatronix commented on GitHub (Feb 10, 2021):
I was playing with this a few weeks ago, and forgot all about it, I had to test again to see if it needed to be before or after, if you set it before, it doesn't work, unlike channels. Shrug
So it has to be set after you start ap, or something in our startap resets it
@lbussy commented on GitHub (Feb 12, 2021):
You know this - but that ended up working. Thank you for your help.