Skip to content
This repository has been archived by the owner on Feb 4, 2023. It is now read-only.

Accessing manager after connection #15

Closed
dbhaig opened this issue Apr 12, 2020 · 1 comment
Closed

Accessing manager after connection #15

dbhaig opened this issue Apr 12, 2020 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@dbhaig
Copy link

dbhaig commented Apr 12, 2020

Hi Khoi
I am experimenting with your WiFi Manager library on an ESP8266 and have been able to get it to successfully connect to my WiFi router.

According to the README.md file:

"The configuration portal will now be visible on two networks, these being it's own network and the network to which it has connected. On it's own network it will have two IP addresses, the original 192.168.4.1 and the same IP address it has on the network to which it connected."

Once connected to the router, I am not seeing the configuration port at either the 192.168.4.1 or the DHCP assigned IP address.
(I can successfully ping the DHCP assigned IP address but not the 192.198.4.1 address once the ESP8266 is connected.)

What am I missing?

Thanks, in advance.

@khoih-prog
Copy link
Owner

Hi Don,

Thanks for using the library. I'm sorry for the not-updated and misleading README

I dropped the persistent Config Portal quite a while and use dynamic Config Portal with these features:

  1. open only when necessary to enter Credentials
  2. closed whenever Credentials are valid and Config Portal not needed
  3. More efficient as Config Portal WebServer is not running in normal operation.

because of these following concerns and potential issues

Imagine you have 20 different devices, each running its own AP. There will be a lot of issues such as :

  • channel conflict => big issue for every board, even for your router if channel is duplicated.
  • unintended (re-)connection from other devices
  • the STA+AP mode is not as very reliable as STA only.
  • the Portal Webserver must be still running and not efficient to do so.

Will fix the README soon.

Regards,

khoih-prog added a commit that referenced this issue Apr 13, 2020
### Releases 1.0.7

1. Use `just-in-time` scanWiFiNetworks() to reduce connection time necessary for battery-operated DeepSleep application. Thanks to [CrispinP](https://github.com/CrispinP) for identifying, requesting and testing. See [Starting WiFIManger is very slow (2000ms)](#6)
2. Fix bug relating SPIFFS in examples :
 - [ConfigOnSwitchFS](examples/ConfigOnSwitchFS)
 - [ConfigPortalParamsOnSwitch](examples/ConfigPortalParamsOnSwitch)  (now support ArduinoJson 6.0.0+ as well as 5.13.5-)
 - [AutoConnectWithFSParameters](examples/AutoConnectWithFSParameters)
 See [Having issue to read the SPIFF file](#14), Thanks to [OttoKlaasen](https://github.com/OttoKlaasen) to report.
3. Fix [README](README.md). See [Accessing manager after connection](#15)
@khoih-prog khoih-prog added the documentation Improvements or additions to documentation label Apr 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants