ZenWiFi BD4 nodes ignore 5GHz channel setting – always stuck on ch 36

[jksmurf]

Interesting findings indeed.

Just a data point, on both my Wi-Fi 6 AIMesh systems (see sig for nodes backhaul etc), assuming the Network Tools, Site Survey is a reasonable determinant of the channels, the channels (2.4 and 5 GHz) I set on the main Router are the same as what is propagated to the nodes. Channels 1 and 48 on my remote network, 11 and 36 locally, for 2.4 and 5 GHz respectively.

 

[Tech9]

I tried the following procedure for a clean setup:

This is a wrong procedure. Don’t do any configuration on the router you want to add as node. Just reset it, wait for it to boot and add using node discovery on the main router. Follow the sequence in post #15 to prevent BD4 units from pairing with each other.

 

[Cico75]

Interesting findings indeed.

Just a data point, on both my Wi-Fi 6 AIMesh systems (see sig for nodes backhaul etc), assuming the Network Tools, Site Survey is a reasonable determinant of the channels, the channels (2.4 and 5 GHz) I set on the main Router are the same as what is propagated to the nodes. Channels 1 and 48 on my remote network, 11 and 36 locally, for 2.4 and 5 GHz respectively.

Thank you for the data point! That's very helpful and actually confirms my suspicion – if channel sync works correctly on your WiFi 6 AiMesh systems, this is likely a BD4 specific firmware bug rather than a general AiMesh issue.

I am currently pushing ASUS support to escalate this to their firmware development team. Let's hope they take it seriously!

 

[Tech9]

I am currently pushing ASUS support to escalate this

There is no need to call ASUS Support when you haven't read ASUS documents about setting up AiMesh. What are you doing is NOT the correct way to add AiMesh nodes. There is also a difference when adding paired mesh set to existing ASUS router. I tried to explain it to you. Your AiMesh devices have IP addresses. If you can log into one of your BD4 and see the GUI - this device is a master node. I'm trying to help you, I've done it before and I know the extra steps... you are not listening. There is no way AiMesh is using different channels. Your BD4 units form own AiMesh because you are powering up the first one, do settings on it and then power up the second one which attaches automatically to the first one.

 

[Tech9]

[AiMesh] How to setup AiMesh system (Web GUI)?

 

[OzarkEdge]

There is no need to call ASUS Support when you haven't read ASUS documents about setting up AiMesh. What are you doing is NOT the correct way to add AiMesh nodes. There is also a difference when adding paired mesh set to existing ASUS router. I tried to explain it to you. Your AiMesh devices have IP addresses. If you can log into one of your BD4 and see the GUI - this device is a master node. I'm trying to help you, I've done it before and I know the extra steps... you are not listening. There is no way AiMesh is using different channels. Your BD4 units form own AiMesh because you are powering up the first one, do settings on it and then power up the second one which attaches automatically to the first one.

Yep... plus ZEN's plug and play automation is not helping the OP.

OE

 

[Tech9]

I'm pretty sure ASUS Support will be totally puzzled and will ask the OP to reboot and reset countless times. If the OP claims issues with the BD4 set without telling them the intention to add both BD4 units as nodes to another router their best solution is going to be RMA.

 

[Cico75]

There is no need to call ASUS Support when you haven't read ASUS documents about setting up AiMesh. What are you doing is NOT the correct way to add AiMesh nodes. There is also a difference when adding paired mesh set to existing ASUS router. I tried to explain it to you. Your AiMesh devices have IP addresses. If you can log into one of your BD4 and see the GUI - this device is a master node. I'm trying to help you, I've done it before and I know the extra steps... you are not listening. There is no way AiMesh is using different channels. Your BD4 units form own AiMesh because you are powering up the first one, do settings on it and then power up the second one which attaches automatically to the first one.

You were right all along - I apologize for overlooking your advice. I was so caught up in the troubleshooting process that I missed it. Thanks to your patience it is now working perfectly - both BD4 nodes are on the same channel as the main router (Ch 52).

I will post a step-by-step routine shortly on how I got it working, including the pitfalls I encountered along the way.

 

[Cico75]

**How to correctly add ZenWiFi BD4 (2-pack) as AiMesh nodes to an existing ASUS router**

Background: BD4 units ship as a pre-paired mesh set. If you power them up together or add them incorrectly, they form their own internal AiMesh with each other instead of connecting to your main router. This causes both nodes to stay on Ch 36 regardless of what channel your main router is set to. Credit to Tech9 for identifying this.
---
**Preparation**
- Disable Ethernet Backhaul Mode on your main router before starting (AiMesh → System Setting). If this is enabled, nodes can only connect via wire and wireless discovery will fail.
- Make sure both BD4 nodes are completely powered off

**Step 1 - Add Node #1 (Main Unit)**
1. Keep Node #2 powered OFF
2. Factory reset Node #1 with Method 2:
(Power off, Hold WPS button while Power on, keep holding until LED goes off/on/flashing, release WPS button Power off unit, turn on)
3. Wait for Node #1 LED to turn solid blue (ready for setup)
4. Do NOT configure anything on the node itself
5. Do NOT plug in any Ethernet cables yet
6. On your main router WebUI: Network Map → AiMesh → Search
7. When Node #1 appears, click to add it
8. Wait for synchronization to complete (LED turns white)

**Step 2 - Add Node #2**
1. Power OFF Node #1 after it has been successfully added
2. Factory reset Node #1 with Method 2:
(Power off, Hold WPS button while Power on, keep holding until LED goes off/on/flashing, release WPS button Power off unit, turn on)
3. Wait for Node #2 LED to turn solid blue
4. Do NOT configure anything on the node itself
5. Do NOT plug in any Ethernet cables yet
6. On your main router WebUI: Network Map → AiMesh → Search
7. When Node #2 appears, click to add it
8. Wait for synchronization to complete

**Step 3 - Power up both nodes, without Ethernet cables!**
1. Power on both nodes
2. Wait until both show white LED and appear connected in WebUI
3. Verify both nodes are on the correct 5GHz channel (same as main router)

**Step 4 - Connect Ethernet backhaul (if using wired backhaul)**
Important boot sequence - always follow this order or the node will revert to Ch 36!
1. Boot the node WITHOUT any cables plugged in (or Channel will not be synched)
2. Wait until LED turns white and node appears connected in WebUI
3. Then connect the backhaul cable (Router LAN → Node WAN)
4. Wait until node reconnects
5. Only then connect client LAN cables

**Known pitfalls / bugs**
Boot sequence bug: If a node boots with the backhaul cable already plugged in, it reverts to Ch 36. Always boot without cables, wait for white LED, then plug in Ethernet.
Dual-port boot bug: If both backhaul and client cables are connected during boot, the node may not be recognized by AiMesh at all.
Wireless setup via ASUS Router App (iOS/Android) was unreliable - use the WebUI browser interface instead.
If the node shows "not connected" in WebUI after adding, try rebooting the node without any cables and let it reconnect wirelessly first.
**Setup: RT-AX88U Pro (Merlin 3006.102.7) + 2x ZenWiFi BD4 (3.0.0.6.102_58138), wired Ethernet backhaul**

I hope it helps some Folks.

PS: And ASUS Support will hear my Story...

 

[OzarkEdge]

**How to correctly add ZenWiFi BD4 (2-pack) as AiMesh nodes to an existing ASUS router**

Background: BD4 units ship as a pre-paired mesh set. If you power them up together or add them incorrectly, they form their own internal AiMesh with each other instead of connecting to your main router. This causes both nodes to stay on Ch 36 regardless of what channel your main router is set to. Credit to Tech9 for identifying this.
---
**Preparation**
- Disable Ethernet Backhaul Mode on your main router before starting (AiMesh → System Setting). If this is enabled, nodes can only connect via wire and wireless discovery will fail.
- Make sure both BD4 nodes are completely powered off

**Step 1 - Add Node #1 (Main Unit)**
1. Keep Node #2 powered OFF
2. Factory reset Node #1 with Method 2:
(Power off, Hold WPS button while Power on, keep holding until LED goes off/on/flashing, release WPS button Power off unit, turn on)
3. Wait for Node #1 LED to turn solid blue (ready for setup)
4. Do NOT configure anything on the node itself
5. Do NOT plug in any Ethernet cables yet
6. On your main router WebUI: Network Map → AiMesh → Search
7. When Node #1 appears, click to add it
8. Wait for synchronization to complete (LED turns white)

**Step 2 - Add Node #2**
1. Power OFF Node #1 after it has been successfully added
2. Factory reset Node #1 with Method 2:
(Power off, Hold WPS button while Power on, keep holding until LED goes off/on/flashing, release WPS button Power off unit, turn on)
3. Wait for Node #2 LED to turn solid blue
4. Do NOT configure anything on the node itself
5. Do NOT plug in any Ethernet cables yet
6. On your main router WebUI: Network Map → AiMesh → Search
7. When Node #2 appears, click to add it
8. Wait for synchronization to complete

**Step 3 - Power up both nodes, without Ethernet cables!**
1. Power on both nodes
2. Wait until both show white LED and appear connected in WebUI
3. Verify both nodes are on the correct 5GHz channel (same as main router)

**Step 4 - Connect Ethernet backhaul (if using wired backhaul)**
Important boot sequence - always follow this order or the node will revert to Ch 36!
1. Boot the node WITHOUT any cables plugged in (or Channel will not be synched)
2. Wait until LED turns white and node appears connected in WebUI
3. Then connect the backhaul cable (Router LAN → Node WAN)
4. Wait until node reconnects
5. Only then connect client LAN cables

**Known pitfalls / bugs**
Boot sequence bug: If a node boots with the backhaul cable already plugged in, it reverts to Ch 36. Always boot without cables, wait for white LED, then plug in Ethernet.
Dual-port boot bug: If both backhaul and client cables are connected during boot, the node may not be recognized by AiMesh at all.
Wireless setup via ASUS Router App (iOS/Android) was unreliable - use the WebUI browser interface instead.
If the node shows "not connected" in WebUI after adding, try rebooting the node without any cables and let it reconnect wirelessly first.
**Setup: RT-AX88U Pro (Merlin 3006.102.7) + 2x ZenWiFi BD4 (3.0.0.6.102_58138), wired Ethernet backhaul**

I hope it helps some Folks.

PS: And ASUS Support will hear my Story...

Save your notes. You will need to reconfigure your network from scratch whenever a firmware update leaves you with a new issue... sometimes this will fix it... this is ASUS' Story.

FW Reset FAQ

OE

 

[Tech9]

This situation is going to be potentially worse with Zen sets where the main node is different unit from the rest. XB4 is a such example, the main unit is XB4R and the nodes are XB4N. I never had one in my hands, but associating all the unis as nodes to different ASUS router may turn impossible. The ASUS experience includes discovering of non-documented features and workarounds.

 

[OzarkEdge]

OP might want to stick with all stock ASUSWRT to reduce the number of variables going forward... to save time and trouble.

OE