EAP650 using mesh when not supposed to

EAP650 using mesh when not supposed to

EAP650 using mesh when not supposed to
EAP650 using mesh when not supposed to
Yesterday - last edited 11 hours ago
Tags: #Mesh #POE
Model: EAP650  
Hardware Version:
Firmware Version: 1.1.3 Build 20250326 Rel. 54048

Hi everyone,

I’m running into an issue with my EAP650 access points where one AP consistently connects via wireless mesh, even though both APs are hardwired and mesh is disabled at the site level.
 

Network Setup:

  • Router: ER605 v2.20

  • Switch: Off-brand unmanaged PoE switch

  • APs: 2× EAP650

  • Controller: Omada Controller (software)

  • Both EAP650s are powered and connected via PoE

  • Mesh: Disabled (Site Settings)

  • EAP LLDP: Enabled

  • Fast Roaming: Enabled
     

Behavior:

  • Whichever EAP650 connects first behaves correctly and uplinks directly to the router.

  • The second EAP650 always shows as routing through the first AP (mesh uplink), even though it is physically connected via Ethernet.

  • This happens consistently and is visible in the Omada topology.
     

Important troubleshooting detail:

  • If I power one EAP650 with the wall adapter and bypass the PoE switch (Ethernet only), both APs immediately work correctly and uplink directly to the router as expected.

  • This confirms:

    • The Ethernet runs are good

    • The APs are capable of proper wired uplink

    • The issue appears to be related to PoE + switch behavior, not cabling
       

Why this is confusing:

  • Mesh is explicitly disabled

  • LLDP is enabled

  • The APs are physically wired

  • Yet Omada still forces the second AP to use a wireless uplink unless PoE is removed from one device
     

Questions:

  1. Is there a known issue where certain unmanaged PoE switches cause Omada to mis-detect wired uplinks?

  2. Does the EAP650 require a specific LLDP or PoE handshake that some off-brand switches don’t fully support?

  3. Is there a way to force Ethernet uplink per AP in Omada?

  4. Are there controller logs I should check to confirm why Omada believes the Ethernet uplink is unavailable?
     

I can make this work by using a wall adapter, but that’s not ideal for ceiling mounting, and I’d prefer to keep everything PoE as designed.

Hopefully I'm just overlooking something simple, but any insight from TP-Link staff or others who’ve seen this would be appreciated. Thanks!

f2c2576ca8a54e0ab825f56993774d40df1c5f38fb29401e810b00db10c610e0cfffc5d13b42442b810adf4e8a51ff61dd60c84773e842b59419d5260325b2ef

  0      
  0      
#1
Options
1 Accepted Solution
Re:EAP650 using mesh when not supposed to-Solution
11 hours ago - last edited 11 hours ago

Hi  @BigDaddyHead 

 

Thanks for posting here.

You have a slight misunderstanding about this issue. These two EAPs are not connected via mesh bridging. If they were mesh-bridged, the line between the two EAPs would be dashed. In the screenshot you provided, the line is solid, indicating that the two EAPs are connected via a wired connection. Additionally, if it were mesh bridging, there would be a WiFi icon next to the second EAP. The following two screenshots show how mesh bridging is displayed for your reference.

 

 

 

 

Therefore, in your case, the topology display is inaccurate. For more information on this situation, please refer to the following post:

Troubleshooting Topology in Controller Is Not Recognized Properly

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:EAP650 using mesh when not supposed to-Solution
11 hours ago - last edited 11 hours ago

Hi  @BigDaddyHead 

 

Thanks for posting here.

You have a slight misunderstanding about this issue. These two EAPs are not connected via mesh bridging. If they were mesh-bridged, the line between the two EAPs would be dashed. In the screenshot you provided, the line is solid, indicating that the two EAPs are connected via a wired connection. Additionally, if it were mesh bridging, there would be a WiFi icon next to the second EAP. The following two screenshots show how mesh bridging is displayed for your reference.

 

 

 

 

Therefore, in your case, the topology display is inaccurate. For more information on this situation, please refer to the following post:

Troubleshooting Topology in Controller Is Not Recognized Properly

Recommended Solution
  0  
  0  
#2
Options