Has FSBrowserNG been tested with the new ver 2.4.1 board manager?

[bill-orange]

I just recompiled working code under the new board manager. It compiles fine but I can not bring up the web config web page to get started. I am using a WEMOS D1 Mini Pro

[species5618]

Do you get anything out of the serial port

No promises. I may get chance to looks in the next 24 hrs

[bill-orange]

Nothing I would judge as helpful. With pin 4 to 3.3v I can see a row of connect dots.
I can not joun its network. With pin 4 to ground I get two blinks but can not connect.

[species5618]

testing on a wemos D1, and the use config exmaple

2.4.0 and 2.4.1 appear to behave the same if config.json exists and is correct
or config.json is missing, and it goes into access point mode

oddly the connect event report ip address 0.0.0.0 but i can ping if by looking up the IP in my DHCP logs and access the web server , i need to look at this

i have not been able to test , forced acces point mode this evening, left my jumper wire things at a friends house

2.4.1 does include a few connect reconnected changes, looks like i have some reading to do

[bill-orange]

Yes, I noticed the ip address 0.0.0.0 also. Thanks

[bill-orange]

Looks line ver 2.4 board manager broke WiFiManager

[species5618]

Have you got a url for reference
Or any other info

[bill-orange]

https://github.com/tzapu/WiFiManager

From a very brief look, the same symptoms as you report on FSBrowserNG.

[species5618]

i have an idea, which explains the 0.0.0.0

due to it not always working the while and it causing a blocking delay the ( WiFi.status() != WL_CONNECTED ) bit was removed, which wait for an ip address

WiFi.onStationModeConnected event seem to trigger when wifi mode is established but before DHCP take places, so at the point, the event goes off the IP address is 0.0.0.0

so i need to find time to work though all the example and tune the connection handler to

not block, display IP address correctly, and reconnect properly

[species5618]

weirder and weirder ...
looking at my DHCP logs !
I have just discovered the devices was requesting a IP from DHCP every 5 seconds for ages, !!!

[species5618]

there is a separate event for GotIP

WiFi.onStationModeGotIP

i will look into adding a handler ,