mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #264] Is there an easy way to change wifi channels? #221
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#221
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 @gregsvo on GitHub (Dec 13, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/264
I've got a project I'm working on at my office, but there are many, many wireless devices in the building. The problem (to my knowledge) is that the ESP8266 defaults to channel 1, which is heavily used in this office- and is causing connectivity issues. I would like to change the ESP8266's channel to something else. Is there a way in the configuration in WifiManager to do so?
Thank you! I'm very new at Arduino/ESP8266, so I appreciate your patience.
@mmr066 commented on GitHub (Dec 14, 2016):
u can use the WiFi functions of arduino core see the documentation Thanks
@gregsvo commented on GitHub (Dec 14, 2016):
I was hoping for a more informational answer than that. I've already seen the documentation, but wifi manager didn't seem to be respecting my changes.
@ggriesse commented on GitHub (Mar 15, 2017):
Also looking for a why to change this ..
@girisan commented on GitHub (Oct 6, 2019):
I can give a 'why' for an option to specify channel...
In my case, when the device goes into config mode, the SSID is not visible in the scanned list, Resetting the device repeatedly didnt help. The probable cause was, that the channel probably clashed with many other hotspots in the neighborhood. A simple work around is to let the device specify the channel, which it can randomize each time it gets into the config mode.
At present, in such cases, WiFiManager will be entirely ineffective.
@tablatronix commented on GitHub (Oct 6, 2019):
#936