Failed to connect when we have multiple access point with same name

[jkandasa]

I tried this WiFiManager it is working awesome. When I have more than one ap with same name(I'm using repeater, to extend WiFi Range) it is not connecting. It looks like we are not using bssid to connect a specific access point.

I believe when we connect with bssid, this problem will be resolved.

Thank you!

[kentaylor]

@lakidd, is the effort you've made of implementing extra interface functionality an indication you didn't get the results reported from this sketch?

[lakidd]

I haven't tried that sketch. My tests have been on my own code (which I've only published snippets of here). I'm on the road for a few days so will test w/ that sketch when i get home. With my modified version of WiFi manger I'm seeing a total connect time of 508ms (or 508-274=234ms from when the code starts to execute). FWIW I'm using a hidden SSID. As an aside, using an ATTINY85 to power up the ESP8266 and a reed switch connected to the ATTINY. When the reed switch changes state, the ESP wakes up, connects to the network and to an MQTT server and sends the state of the reed switch. It then powers down. I've got my power consumption down to 8uA when closed and 1uA when open which I'm pretty happy with.

Below is my output using my code and specifying the BSSID.

Start millis:274

millis:274

MAC Address
5c:cf:7f:1a:92:69:
mounting FS...
mounted file system
reading config file
opened config file
{"mqtt_server":"192.168.1.233","mqtt_port":"8080","mqtt_location":"geek"}
parsed json
*WM: Adding parameter
*WM: server
*WM: Adding parameter
*WM: port
*WM: Adding parameter
*WM: location
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Custom STA IP/GW/Subnet
*WM: 192.168.1.222
*WM: Using last saved values, should be faster
*WM: Connection result:
*WM: 3
*WM: IP Address:
*WM: 192.168.1.222
connected to Wireless

millis:508

[kentaylor]

Thanks @lakidd for providing input on the rain gauge switch design. I've incorporated some of the feedback into an updated discussion and revised design.

I'm also still curious on whether you got the same results.

[lakidd]

yeah i'm getting there @kentaylor got a bit going on before xmas but will do soon

[lakidd]

OK, I give up :-) Running the code from here

I get these results which don't change with or without BSSID specified. http://pastebin.com/RUQaqzvY

One thing I did figure out was that i was using v2.1 of the esp8266 arduino cores on the code that was connecting quicker with BSSID. Interestingly @kentaylor sample code above crashes on that version. The test I've run above was w/ version 2.3. I'll have to try my larger project w v2.3 and see if the difference goes away.

[tablatronix]

can we throw some gists together for testing this ? Or do you have a fork or branch with an example

[lakidd]

@tablatronix So I forked WiFiManager here and added an optional BSSID parameter to the captive portal. Seems to work for me. I haven't tested with the v2.3 ESP8266 arduino cores tho. Is that what you were after ?

[tablatronix]

Yeah whatever you seem to be having issue with or gave up on. Ill try to reproduce here.

[suculent]

I'll try to revive this issue in order to test and merge. I'd love to have this feature available for anyone.