Enable hidden SSID when connecting #1337
Comments
|
Please try mega-20180430 and report back.. |
|
The flag to list hidden SSID in a scan is not set,. So it will not connect to hidden SSID, also not in build 0430. |
|
On my side, hidden SSID is working, absolutely no problem. |
|
Hidden SSID is a flag for scanning, I am not sure it is also a flag for the WiFi.begin(). |
|
Hi, thanks for the fast reaction. I tried mega-20180430. Unfortunately the problem isn't solved, I changed back to mega-20180426 and it works again flawlessly. Protocol of mega-20180430 (SSID stared out by me): INIT : Booting version: mega-20180430 (ESP82xx Core 2_4_1) [edit] |
|
Strange, now i have done a test with DHCP. My SSID is hidden in the AP. Connect no problem, see here |
|
Hi, The normal bin 0426 is working pretty stable with hidden SSID as well as all other previous versions I have tried. |
|
I have tested with this version: Edit: AP is OPENWRT router |
|
Flashed with mega-20180430, and performed a factory reset. 2nd try: manually configured the ESP. Also without success: When going back to a previous version (dev-13) it is working again. So perhaps now only connecting to a hidden AP is possible? |
|
Have you tried a clean install ? |
|
If you are connected to the ESPeasy node via serial, you can simply reset to factory default. And no, it is not limited to hiddenAP, because my own AP's are not hidden and they work just fine. |
|
I did perform a 'reset' on my NodeMCU device in the console. Brainwave: I flashed a new Wemos D1 mini with this binary file. So my problem seems to be hardware-related. The hardware however does function properly, when I go back to dev-13. It was the cheapest nodeMCU that I ever bought, and does not have the metal shield over the WiFi compartment. My guess is that this particular device does not have the proper hardware for the current Wifi code. |
|
It can be that some part of the flash is not configured properly. Lines 97 to 101 in 45afaf8 This persistent line, disables writing to that part of the flash. |
|
(took some time to create a fresh build environment) I commented line 99 (the WiFi.persistent line). Same problem. |
Grovkillen
added
Status: Needs Info
|
@DittelHome
I then give myself the option to erase the whole Node before flash..
|
|
Flashing todays version (mega-20180502) solves the problem. Now I can configure the nodeMCU by connecting to the Wifi (192.168.4.1), and after that it will properly connect to my accesspoint. As I don't have a hidden AP available, I do not know if the original problem is solved too. |
|
Hi, |
|
New devices arrived, flashed 0503, still no connection to hidden SSID. Perhaps needed: my AP is an AVM Fritzbox 7272 Protocol: |
|
@Wiki591 you say "toasted my last free Wemos Device" |
|
And @Wiki591 - If you make the AP visible do they then connect fine ? |
|
@Oxyandy Some of us let the magic smoke escape from the electronics and as we all know, electronics main component is this magic smoke. If you let it out, electronics do not work anymore. |
Oh, this kind of toasted.. Which you rather, jam or honey ?!Of course, never happened with me either.. |
|
Hi, @Oxyandy: as TD-er already stated: producing some tiny little blue clouds exhaled by the electronics is not the best way to keep these things running. They end up in the all-embracive Data Nirvana. Back to problem: I have no problems to connect to my AP (AVM Fritzbox 7272) if it is visible. As well as with the same config.dat, just flashed mega 0421 - 0426 the devices connect to the AP with hidden SSID instantaneously. Flashing the same device with the same config with 0428 and higher trying to connect to the same WLAN produces the protocol posted before - no connection. |
|
Ok, you have inspired me, I will make my SSID hidden & play. |
|
I was thinking about changing this by adding the parameter to the wifi setup function, but I don't want to change too much at the same time anymore, or else you don't know what's causing what anymore. |
|
meh, my node does not seem to care if set hidden, connects anyway.. |
|
@Oxyandy Do you have this Beacon timeout with 0504 on any node, or just a few? |
|
ESP_Easy_mega-20180506_normal_ESP8266_4096_Self_Compiled.zip Try this please, there have been some quirks, maybe this resolves it for you. |
|
Flashed over the top, no settings changed. INIT : Booting version: (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3) Connecting same AP, SSID visible: INIT : Booting version: (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3) at least, during this established connection made the AP hidden, follow-up in protocol: 30286 : WD : Uptime 1 ConnectFailures 0 FreeMem 18528 |
|
Apparently it may be related to the first connect attempt when in AP mode: esp8266/Arduino#4519 |
|
Hi, |
|
OK, here we go. What I have done first:
Then I have hidden the SSID of the AP again - no reboot of the Wemos
The I rebooted the Wemos
Protocol 1: _60286 : WD : Uptime 1 ConnectFailures 0 FreeMem 18528 ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 1384, room 16 INIT : Booting version: (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3) Protocol 2: 177436 : WIFI : Set WiFi to STA Protocol 3: _>reboot load 0x4010f000, len 1384, room 16 INIT : Booting version: (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3) |
|
I read last week you have to set the flag to use a BSSID to connect and also make sure to include that BSSID. |
|
öhm, does anyone still take care of this issue (of mine)? |
|
It is still on my to-do list. |
|
Thank you, so I'll be patient. |
|
That's about when we changed to 2.4.1 I guess |
|
Yes, correct, so tells the documentation - and some changes in the [wifi] section |
|
Reading the docs concerning changes in 20180426 -> 20180428, its says "Just disconnect when DNS lookup is not possible" |
|
@Wiki591 |
|
When using a static IP config, you now have to use all fields. |
|
@Oxyandy Yesterday I have configured my AP standard-like, ie DHCP by himself. No success. I just tried static IP, no success either. Protocol: INIT : Booting version: mega-20180513 (ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3) |
|
Hi, Due to an overload of APs in my neighbourhood on channels 1-11, I switched in the past my AP to Channel 12. Result was a seriously better performance and stability. I don'nt know why, but in my neighbourhood several APs n the last 2-3 months where switched to channel 12, too. Today I switched to channel 9. Result: better performance and - i can't believe it - ESPEasy is able to connect to my hidden network. I have tried with 2018-05-22-notrmal GOTCHA! For me the issue is solved and there is a workaround for other users in the furture. I am very grateful for your thoughts and your work/efforts in the past two months about this issue. Hopefully with this message you will be freed a little bit concerning the lack of time in this stage of the project. THANK YOU!. |
|
Hi, |
|
OK, that's strange to say the least. Glad to see this to work. @Grovkillen Can you make some note about this on the Wiki? |
|
@TD-er I will |
|
Hi, After updating my productive devices to ESP_Easy_mega-20180522_normal_ESP8266_4096 I can report, all are doing their job stable and are performing good during the past 20 hours or so. |
|
Good to hear it is working fine now. |
|
fyi: |
|
my configuration with hidden ssid:
|
Not sure what you intend to tell us with this reply. |
Up to version mega-20180426 connecting to a network with hidden SSID was no problem.
Using version mega-20180428 the attempt to connect to a network with hidden SSID ends up with error "No AP found"
Pls reenable this feature, its a question of avoiding unwanted and annoying automated connection tries in our recent environment of everything-is-online.
The text was updated successfully, but these errors were encountered: