Bitaxe – WiFi Won’t Connect (5GHz Network / ESP32 2.4GHz Only)

Log into your router's admin interface. Most ISP routers live at `192.168.1.1`, `192.168.0.1`, or `10.0.0.1` in a browser. 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. If you've never logged in, find that sticker first — you'll need admin access for every remaining step.

Find the Wi-Fi / Wireless / Network / Radio settings page. You're looking for two specific things: the 2.4 GHz radio's current state (enabled or disabled) and whether 2.4 GHz and 5 GHz share a single SSID or have separate names. Record both answers — they determine which fix you need.

If the 2.4 GHz radio is disabled, enable it. Set the SSID to something distinct like `HomeNet-24` or `HomeNet-IoT`. Use the same password as your main network for simplicity. Security: WPA2-Personal (AES only). Channel: Auto, or manually 1, 6, or 11. Avoid WPA3 and Mixed-Mode — older ESP-Miner builds have rough WPA3 support.

Save router settings and wait 60 seconds for the router to re-broadcast. On the Bitaxe config page (connect to `Bitaxe_XXXX` AP, browse to `http://192.168.4.1/`), tap the SSID scan refresh button. Your new 2.4 GHz SSID should now appear in the list. If it doesn't, refresh once more after another 30 seconds.

Enter the 2.4 GHz SSID and password on the Bitaxe config page, save, and let the device reboot. Watch the OLED — it should transition from `WIFI: CONNECTING…` to `IP: 192.168.x.x` within 30 seconds. From your laptop on the same LAN, browse to that IP to confirm the AxeOS dashboard loads.

If you run a mesh system, disable band steering. On Eero: Eero app → Settings → Advanced → Wi-Fi → toggle `Steering` off, OR add a separate IoT Network with 2.4 GHz only (Eero specifically added this feature because of devices like the Bitaxe). On Nest Wi-Fi: Home app → Wi-Fi → Settings → Advanced → toggle band steering off. On Orbi: Admin → Wireless → uncheck `Enable Smart Connect` to get separate SSIDs. On Deco: Deco app → Advanced → IoT Network (supported models).

On ASUS AiMesh / standalone ASUS routers: Admin → Wireless → Smart Connect → Off → configure a separate 2.4 GHz SSID. On ISP gateways without SSID-split in the web UI, call ISP support and request `dual-SSID mode` or `legacy 2.4 GHz guest network` — this usually requires an escalation but the feature exists on every major Canadian and US ISP gateway.

Verify the full security stack on the 2.4 GHz SSID: WPA2-Personal (AES only, not TKIP), fixed channel 1/6/11 (not Auto in congested apartments), channel width 20 MHz, AP Isolation / Client Isolation DISABLED. AP Isolation blocks the Bitaxe from talking to anything else on the LAN and breaks the AxeOS dashboard even when Wi-Fi works.

Temporarily disable MAC filtering to test. If your router has a MAC whitelist enabled, the Bitaxe is blocked until its MAC is added. Find the Bitaxe MAC address on the Bitaxe AP config page (before connection) or on the AxeOS dashboard (after connection); format is `XX:XX:XX:XX:XX:XX`. Add to the router's allow list.

Reboot the router first, wait 2 minutes for it to fully rebroadcast, then power-cycle the Bitaxe. Watch the OLED transition through `WIFI: CONNECTING…` to the assigned IP. From any LAN device, browse to that IP and confirm the AxeOS dashboard renders. This is the moment most users' problems end.

If your main router genuinely cannot be split-SSIDed (carrier-locked gateway, landlord controls it, roommate situation), drop a dedicated 2.4 GHz travel router inline. The GL.iNet Mango GL-MT300N-V2 costs ~$30 CAD, plugs WAN into your existing network, and broadcasts a clean 2.4 GHz WPA2-PSK SSID of your choosing. Configure in 10 minutes, connect the Bitaxe to it instead of the main network.

Alternative: dedicate an old Android phone as a 2.4 GHz hotspot. Plug it into a wall charger, disable cellular data, let it tether via Wi-Fi client mode to your main network using a share-Wi-Fi app (NetShare, PdaNet+, or the OEM feature on newer Samsung / Xiaomi). Functionally identical to a travel router; costs nothing if you have an old phone in a drawer.

If you're on an old `ESP-Miner` firmware build, flash the current release via USB-C. Use a USB-C data cable (not charge-only — charge-only cables silently break diagnostics), hold the boot button while connecting, and use the Bitaxe Web Flasher at `bitaxeorg.github.io/bitaxe-web-flasher/`. A factory image wipes saved SSID and pool config, so re-enter credentials on first boot after flash.

Test the Bitaxe on a known-clean external network. Bring it to a friend's house, plug it in, see if it joins their 2.4 GHz SSID. If it joins immediately, your hardware is fine and your home network is the problem (good data for your next ISP call). If it fails on a friend's network too, move to Tier 4 — antenna or ESP32-S3 module is suspect.

If the Bitaxe won't even serve its own `Bitaxe_XXXX` AP reliably, you have a crash-loop problem, not a band problem. Cross-reference `bitaxe-esp32-crash-loop` and `bitaxe-axeos-connection-issues` for different troubleshooting paths. Serial console via USB-C (`esptool.py --port /dev/ttyUSB0 monitor` at 115200 baud) will show you boot-time errors that the OLED can't display.

Stop DIY when you've confirmed: band-split SSID configured, band steering disabled, WPA2-Personal only, phone-hotspot test failed, Tier 3 travel router failed, friend's network test failed, firmware reflashed. At this point the ESP32-S3 module, antenna, or antenna-feed trace is suspect. Ship the Bitaxe to D-Central for bench diagnosis. We built the original Bitaxe Mesh Stand — we know these boards.

D-Central bench process: cold-boot inspection under USB-C serial monitor with a known-good 2.4 GHz test AP at 1 m range. If the ESP32-S3 radio doesn't associate with the bench router, we measure antenna-feed resistance (characteristic 50 Ω, antenna path resistance < 1 Ω) and visually inspect the antenna and feed trace for solder defects, impact damage, or contamination.

If antenna and feed are healthy but the radio still fails to associate, the ESP32-S3 module itself is replaced with hot-air rework (top-side 280–310 °C, preheated board). Module cost is minor; bench labour is the real line item. Expected turnaround 3–7 business days. Ship via any trackable carrier — anti-static bag, bubble wrap, include a note with your symptoms and firmware version to save diagnostic time.