mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #707] wm default ap name does not match esp default ap #594
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#594
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 @tablatronix on GitHub (Aug 23, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/707
I was testing the other day and I noticed that the default ap did not match the generated wm one from chip id. It was a bit odd.
try to reproduce , I have a screenshot somewhere
@Kadah commented on GitHub (Aug 24, 2018):
Do you mean this?
https://i.imgur.com/T7yBhBA.png
Testing using OnDemandConfigPortal.ino. Screenshot was of an ESP8266 (ESP-12F) after rebooting, but I got the same but different SSID on an ESP32 Thing.
@tablatronix commented on GitHub (Aug 24, 2018):
Yeah the one the chip generates it different that the one wm generates when no ssid is provided
@tablatronix commented on GitHub (Aug 24, 2018):
ok so its not the same
ESP.getChipId() returns the ESP8266 chip ID as a 32-bit integer.@tablatronix commented on GitHub (Aug 24, 2018):
Will have to test esp32 and see if this fix covers that as well
@tablatronix commented on GitHub (Aug 29, 2018):
esp32
@tablatronix commented on GitHub (May 11, 2020):