Initial noise about nodemcu-firmware HOT 3 CLOSED

The characters maybe from bootloader(in baud 74880). can't be switched off.
There are another 2 pins in chip can be used as uart, if we swap to these pins. no more garbage.
but since ESP-01 or some other modules didn't have them out. so can't turn it off in these modules.

wifi.sta.getip() always return a string now.
which is better?
maybe return two results?

ip, got = wifi.sta.getip()  
if got==true then..

or,

ip = wifi.sta.getip()
if ip~=nil then...

from nodemcu-firmware.

Hi

Thanks for the explanation- as you say we are stuck with the pins we have available... Oh well it was worth trying :-)

I'm still getting to grips with Lua's ability to return more than one argument - I think it's wonderful.

But I would say that perhaps your second option is the best? Right now mine returns "0.0.0.0" if there is no initial connection - I would be happier if NIL was returned.. but that also begs the question - do you CHECK... for example let's say we already have a connection and the home router gets turned off - would you still return the IP?

What I'm trying to achieve is to be able to tell if we currently have a connection - so that, for example in a small unit controlling a light removely by a phone, if the router failed - we could detect lack of Internet - and reboot the board after a short delay.

I'm assuming that right now if connectivity is lost momentarily, we are in trouble?

from nodemcu-firmware.

No check for the connection to router, in nodemcu.
but the low level sdk will check and return a 0.0.0.0 if the current ap/router failed.
there is still a bug in it. sometimes router failed like 1s, we can get a valid ip, but can't connect to network anymore.
it's hard to detect. but a wifi.sta.disconnect() and wifi.sta.connect() will solve this.

from nodemcu-firmware.