NerdQAxe – WiFi 5GHz Network Not Visible

Log into your router admin. Browser to `192.168.1.1`, `192.168.0.1`, or `10.0.0.1` for most home routers; mesh systems use the vendor mobile app (Eero, Google Home, Orbi app, Deco app). Default credentials are usually printed on a sticker on the router. ISP gateways often have a separate admin password on the same sticker — try both. Without admin access, every step below is impossible.

Navigate to the Wi-Fi / Wireless / Network / Radio settings page. Identify two specific facts and write them down: the 2.4 GHz radio's enable/disable state, and whether 2.4 GHz and 5 GHz share a single SSID name or have separate names. The combination determines which fix you need next.

If the 2.4 GHz radio is disabled, enable it. Set its SSID to something distinct: `HomeNet-IoT`, `HomeNet-24`, or `MinerNet`. Use the same password as your main network. Security: WPA2-Personal (AES only, not TKIP, not Mixed Mode). Avoid WPA3-only — older ESP-Miner-NerdQAxePlus builds are unreliable on WPA3-SAE. Channel: Auto, or pin to 1, 6, or 11. Width: 20 MHz.

Save router settings and wait 60 seconds for the router to actually re-broadcast. On the NerdQAxe AP config page (connect to `NerdQAxe-XXXX`, browse to `http://192.168.4.1/`), tap the SSID scan refresh. Your new 2.4 GHz SSID should now appear. If it doesn't, refresh once more after another 30 seconds — some routers take longer than they admit.

Enter the new 2.4 GHz SSID and password on the NerdQAxe config page, save, reboot. Watch the TFT — it should transition `WIFI: CONNECTING…` to `IP: 192.168.x.x` within 30 seconds. Browse to that IP from any LAN device; the NerdQAxe dashboard should render. Mining will start once your pool is configured.

Disable band steering on mesh systems. Eero: Eero app → Settings → Advanced → Wi-Fi → toggle `Steering` off, OR add a separate IoT Network with 2.4 GHz only. Google Nest Wi-Fi: Home app → Wi-Fi → Settings → Advanced networking → band steering off. Netgear Orbi: Admin → Wireless → uncheck `Enable Smart Connect`. TP-Link Deco: Deco app → Advanced → IoT Network on supported models (X20, X60, X90, X95). ASUS AiMesh: Admin → Wireless → Smart Connect → Off → configure separate 2.4 GHz SSID.

Tackle ISP gateways. If the consumer UI doesn't expose SSID-split: (1) call ISP support, ask for `dual-SSID mode` or `legacy 2.4 GHz guest network` from their side — exists on every major Canadian and US carrier (Bell, Rogers, Telus, Videotron, Xfinity, Comcast, Spectrum) but consumer UIs hide it; usually requires escalation. (2) Log in as the admin user, not the default user. (3) Put the gateway in bridge mode and run your own router behind it — the long-term gold standard for any home miner.

Verify the security stack on the 2.4 GHz SSID: WPA2-Personal (AES only), fixed channel 1/6/11 (not Auto in dense apartments), channel width 20 MHz, AP / Client Isolation DISABLED. AP Isolation breaks NerdQAxe dashboard access even when the radio link works — the link succeeds but LAN traffic is blocked.

If your router has MAC filtering / whitelisting, temporarily disable it to test. If the NerdQAxe joins, add the device's MAC (visible on the AP config page before connection or on the dashboard after) to the allow list permanently. Format `XX:XX:XX:XX:XX:XX`. Re-enable the whitelist with the new entry in place.

Reboot in the right order. Power-cycle the router first (full power off for 30 seconds, then back on), wait 2 minutes for it to fully rebroadcast, then power-cycle the NerdQAxe by disconnecting the 12 V input. Watch the TFT transition through `WIFI: CONNECTING…` to the assigned IP. From any LAN device, browse to that IP and confirm the dashboard renders.

Drop a dedicated 2.4 GHz travel router inline. If your main router cannot be reconfigured (landlord, roommate, fully carrier-locked gateway), buy a GL.iNet Mango (`GL-MT300N-V2`, ~$30 CAD). Plug its WAN port into your existing network, configure its Wi-Fi as 2.4 GHz WPA2-PSK with a chosen SSID like `MinerNet`, and connect the NerdQAxe to that. 10-minute setup.

BSSID lock on advanced routers. UniFi / OpenWrt / pfSense / OPNsense: pin the 2.4 GHz BSSID for your IoT SSID to a single radio on a single AP. UniFi: Settings → Wi-Fi → Advanced → Band Steering off, Minimum RSSI tuned per AP. OpenWrt: edit `/etc/config/wireless`, set `option bssid` explicitly per interface. Forces the NerdQAxe to associate with one specific AP rather than getting steered between mesh nodes.

Repurpose an extender or second router as a 2.4 GHz-only AP. Set it to AP mode (not router mode), disable its 5 GHz radio entirely, ethernet-uplink to your main network. Place within 5–10 m of the NerdQAxe. Gives the miner a dedicated, uncongested 2.4 GHz path without touching the main router.

Flash the latest `ESP-Miner-NerdQAxePlus` firmware via USB-C. Use a USB-C DATA cable (not charge-only — charge-only silently bricks diagnostics, the #1 first-time-builder mistake). Hold boot button if needed during connect. Use the Web Flasher or the NerdQAxePlus releases on `https://github.com/bitmaker-mining/NerdQAxePlus`. A factory image wipes saved SSID; re-enter credentials after first boot.

Test on a known-clean external network. Bring the NerdQAxe to a friend's house, plug it in, watch onboarding. Joins their 2.4 GHz in 30 seconds = your hardware is fine, your home network is the problem. Fails on theirs too = antenna or ESP32-S3 module suspect, advance to Tier 4.

Stop DIY when: band-split SSID configured, band steering disabled, WPA2-Personal verified, phone hotspot test failed, Tier 3 travel router failed, friend's-network test failed, firmware reflashed clean. At this point the ESP32-S3 module, antenna feed trace, or antenna itself is suspect. Ship the NerdQAxe to D-Central rather than continuing to flash firmware that won't help.

D-Central bench process. Cold-boot inspection under USB-C serial monitor at 115200 8N1 against a known-good bench 2.4 GHz AP at 1 m. If the ESP32-S3 doesn't associate, we measure antenna-feed continuity (50 Ω characteristic, antenna path resistance < 1 Ω end-to-end), inspect the antenna under microscope for impact / solder / contamination defects, and check the ESP32-S3 module 3.3 V supply rail under load. If antenna and feed are healthy but radio fails, the ESP32-S3 module is replaced via hot-air rework (top-side 280–310 °C, board pre-heated).

Ship safely. Anti-static bag, double-box, ≥5 cm foam on every side. Include a printed note with: observed symptoms, firmware version (visible on dashboard or in serial boot log), connectivity test results from Tiers 1–3, contact info. Notes save 30 minutes of bench-rate diagnostic re-walking. Expected turnaround 3–7 business days for NerdQAxe-class hardware.