Doesn't show up on network after setting wifi up in settings

[coltography]

Installed hyperk on my esp8266 to try out, but when I set the wifi network it is not showing up on my network. It's not falling back to the AP either so it must be connecting(?)

I've tried resetting it, using another esp8266, checking my router, restarting router etc. Not sure what else it could be. Serial logs show nothing either.

[awawa-dev]

Hi
check the manual on the wiki - unfortunately it's rather a common issue with this old board and new modern routers. Turning on some router's option may help.

[Esmail-sarhadi]

Two things worth ruling out before the firmware:

• The ESP8266 only sees 2.4 GHz. A router with band steering, or one running WPA3-only / WPA2-WPA3 mixed with PMF required, is a very common silent failure.
• WiFi.begin() returns immediately. If the sketch does not wait for WL_CONNECTED, it may never reach the AP fallback and may print nothing.

Try: after WiFi.begin(), loop for ~15 s printing WiFi.status(), then look for the device on the router by MAC address rather than by name (mDNS and DHCP hostnames often do not show up). If the status never leaves WL_IDLE_STATUS, the credentials or the security mode are the problem, not the network.

[awawa-dev]

It's irrelevant. In such scenario (wifi credentials are set and no clients connected to its AP) Hyperk 0.0.5 will reboot after 3 minutes and will try to reconnect to the AP.

[Esmail-sarhadi]

You're right, and I checked it before answering this time. src/main.cpp on 0.0.5 (f83984b) does block:

WiFi.begin(ssid, pass);
uint32_t timeout = millis() + 12000;
while (WiFi.status() != WL_CONNECTED && millis() < timeout) delay(400);
// ...
if (WiFi.status() != WL_CONNECTED) startAP(hasWifiConfig);

So the firmware waits 12 s and does fall back on its own, and my "the sketch may never reach the fallback" point does not apply to Hyperk. Withdrawn.

What I would still take from that path, for @coltography: when the connect fails, startAP() brings up "Hyperk-Setup" at 192.168.4.1 immediately and prints "Captive Portal Ready at: ...", then "Scheduling automatic restart in 180 seconds ...". So "no AP and nothing on serial" is not the connecting state - either it did connect (no AP by design) or the board never reaches that code / the serial isn't being read. The first ~15 lines after boot would tell which of the two it is.