Hi @OliverElec,

 

I'm not sure I completely follow your setup.  You're saying that you have 4 EAP225's (all V3?) which are all Ethernet connected to a PoE switch?  You're running the Omada/SDN controller software on your MAC?

 

3 of 4 EAP's are working fine, but the 4th (which is the farthest away) is not?  But when you move that EAP physically closer (or directly connect locally to the Switch) then it works fine?

 

How far away is it?  Do you realize that PoE distances are less than Ethernet distances?  Ethernet spec is up to 100 meters for 1Gbit/sec on Cat-5e or better cabling.  But, PoE is only good up to 40-60 meters depending on which PoE spec (aka which voltage 24 or 48) the devices use.

 

1) If you use the midspan power injector instead, proximal to the farthest EAP, does this fix the issue (aka PoE too far check)? 

 

2) If you connect a PC to the (long EAP) cable instead do you get good/clean speed tests (aka bad cable check)?

 

-Jonathan

thank you very much for getting back to me. I think this is the case but the funny thing is ive had it working. I did find a suggestion online about PoE prioritisation, where the most used devices can almost push the weakest link into not connecting or not sending signal. many thanks

Hi @OliverElec,

 

What is the power budget on your PoE switch?  Each EAP uses ~12.6W I believe -- not sure if this is continuous, or if it fluctuates a bit.  Not sure if you have other PoE devices on the switch.

 

https://www.tp-link.com/us/business-networking/omada-sdn-access-point/eap225/#specifications

 

As the accumulated wattage of connected devices approaches the power budget of the PoE switch, you can get some DC voltage sag, which is exacerbated by wire/connection resistance.  Over time, with a little bit of oxidation, a crack in the wire, etc. things that were just barely in spec can fall out of spec.

 

Just a thought,

Jonathan