yes. It needs to opened on the console or any settings you change will not be registered for the menu to use them.I just flashing my esp32s2 with v3 bin file , can't open config page with PC chrome browser like usual
So , config page only can be open from console now ?
No it's just for esp32-s2 if you see for esp8266 auto send me the linkCheck first post already does this.
I don't see for esp8266 i just see esp32-s2 if you can send me the link for thank youCheck first post already does this.
Only for esp32s2 psphiveNo it's just for esp32-s2 if you see for esp8266 auto send me the link
Post automatically merged:
I don't see for esp8266 i just see esp32-s2 if you can send me the link for thank you
I think that this might be the problem you are having. I dont think they connect to 5ghz connections.....
And the last, is possible that the s2 board is not able to connect with a 5ghznetwork and only works with 2.4ghz networks (I think that it can be the root of all my issues)?
I think there might be a bug in the esp script.....
What can be happen? and why I cannot connect again to the PS-Phive! Wifi after the reboot? (maybe it can be a bug in the script that change the password of both Wifi connections when you set-up the password of your home wifi?
thanks for your clear answer.I think there might be a bug in the esp script.
As a test I tried using "wrongSSID" as my Home Wifi SSID to simulate no being able to connect to the home wifi and my esp started acting strangely and I cant connect to the access point anymore.
Re flashed the bin, entered my correct home wifi details and all is good again.
I'm looking into it.So you confirm that it is a bug on esp script... can it be fixed for your side or isn't possible?
if (connectWifi && WIFI_SSID.length() > 0 && WIFI_PASS.length() > 0) {
WiFi.setAutoConnect(true);
WiFi.setAutoReconnect(true);
WiFi.hostname(WIFI_HOSTNAME);
WiFi.begin(WIFI_SSID.c_str(), WIFI_PASS.c_str());
if (WiFi.waitForConnectResult() != WL_CONNECTED) {
} else {
IPAddress LAN_IP = WiFi.localIP();
if (LAN_IP) {
String mdnsHost = WIFI_HOSTNAME;
mdnsHost.replace(".local", "");
MDNS.begin(mdnsHost.c_str());
if (!startAP) {
dnsServer.setTTL(30);
dnsServer.setErrorReplyCode(DNSReplyCode::ServerFailure);
dnsServer.start(53, "*", LAN_IP);
}
}
}
}
Tested and works as you said... so great work again...I'm looking into it.
As it is in the original stooged code it looks like it should work but obviosly not:
if WiFi.waitForConnectResult() is not WL_CONNECTED, do nothing else do the wifi thing.JavaScript:if (connectWifi && WIFI_SSID.length() > 0 && WIFI_PASS.length() > 0) { WiFi.setAutoConnect(true); WiFi.setAutoReconnect(true); WiFi.hostname(WIFI_HOSTNAME); WiFi.begin(WIFI_SSID.c_str(), WIFI_PASS.c_str()); if (WiFi.waitForConnectResult() != WL_CONNECTED) { } else { IPAddress LAN_IP = WiFi.localIP(); if (LAN_IP) { String mdnsHost = WIFI_HOSTNAME; mdnsHost.replace(".local", ""); MDNS.begin(mdnsHost.c_str()); if (!startAP) { dnsServer.setTTL(30); dnsServer.setErrorReplyCode(DNSReplyCode::ServerFailure); dnsServer.start(53, "*", LAN_IP); } } } }
Maybe instead of receiving the "WL_CONNECTED" status it is receiving the "WL_IDLE_STATUS" which is trigering it to continue when it shouldnt.
I'll do some rewrite tests and see if I can fix it.
Obviosly it wont fix your problem of not being able to connect but at least it might fix the issue of it messing up the original access point if it cannot connect to whatever wifi settings it is given.
Post automatically merged:
@xZenithy right, I've done some tests and it appears that the issue is that if the ESP cannot connect to the home wifi SSID that you enter it messes up the ESP and the regular access point no longer works.
Its ok if the password is wrong, that doesnt mess anything up but if the SSID is wrong or it cannot connect to the entered SSID (like in your case), things get messed up.
I've modified the wifi side of stooged's original script and now it doesnt mess up the ESP if it cannot to the home wifi SSID that is entered in the settings.
Below is a bin for you to test. Obviosly you still can't connect to your 5ghz network but it shouldn't mess up the ESP anymore if it cannot connect.
I'm not sure, I just had a quick look but I could not find any.Tested and works as you said... so great work again...
However it no resolve my issue because the hardware limitation of the board and 2.4ghz Wifi band only.
I guess there isn't a S2 model that support 5Ghz band, right?
Yes, it can do it, but I have 2 rooters, one only 5ghz and it has main internet connection where is connected the ps4 and one second rooter connect by cable to the main rooter and this has 2.4ghz band...I'm not sure, I just had a quick look but I could not find any.
Thanks for testing and for finding the issue in the first place.
Does your router not support broadcasting 2.4ghz and 5ghz at the same time?
I've tested this new esp32s2 bin, this one flawlessly work on home wifi network. Previous one also work but home wifi dns not shown... Brave @Leeful..I'm looking into it.
As it is in the original stooged code it looks like it should work but obviosly not:
if WiFi.waitForConnectResult() is not WL_CONNECTED, do nothing else do the wifi thing.JavaScript:if (connectWifi && WIFI_SSID.length() > 0 && WIFI_PASS.length() > 0) { WiFi.setAutoConnect(true); WiFi.setAutoReconnect(true); WiFi.hostname(WIFI_HOSTNAME); WiFi.begin(WIFI_SSID.c_str(), WIFI_PASS.c_str()); if (WiFi.waitForConnectResult() != WL_CONNECTED) { } else { IPAddress LAN_IP = WiFi.localIP(); if (LAN_IP) { String mdnsHost = WIFI_HOSTNAME; mdnsHost.replace(".local", ""); MDNS.begin(mdnsHost.c_str()); if (!startAP) { dnsServer.setTTL(30); dnsServer.setErrorReplyCode(DNSReplyCode::ServerFailure); dnsServer.start(53, "*", LAN_IP); } } } }
Maybe instead of receiving the "WL_CONNECTED" status it is receiving the "WL_IDLE_STATUS" which is trigering it to continue when it shouldnt.
I'll do some rewrite tests and see if I can fix it.
Obviosly it wont fix your problem of not being able to connect but at least it might fix the issue of it messing up the original access point if it cannot connect to whatever wifi settings it is given.
Post automatically merged:
@xZenithy right, I've done some tests and it appears that the issue is that if the ESP cannot connect to the home wifi SSID that you enter it messes up the ESP and the regular access point no longer works.
Its ok if the password is wrong, that doesnt mess anything up but if the SSID is wrong or it cannot connect to the entered SSID (like in your case), things get messed up.
I've modified the wifi side of stooged's original script and now it doesnt mess up the ESP if it cannot to the home wifi SSID that is entered in the settings.
Below is a bin for you to test. Obviosly you still can't connect to your 5ghz network but it shouldn't mess up the ESP anymore if it cannot connect.