@aubey 

Seems to be a handshaking issue between the switch and the EAP225-Outdoor.  The EAP225 is a low voltage (24VDC) poe compared to the EAP245's 48 VDC.   The switch manual does indicate: "If necessary, the output voltage can be switched manually."  The EAP225's do work if you set the switch output voltage manually?

Do you get any of these warning lights on the switch?  

• Triangle LEDs (top row) indicate PoE out status. Green LED indicates that the respective port uses low voltage, a red LED indicates high voltage. Flashing single green LED: problem to start a low voltage device. Flashing single red LED: problem with high voltage device.
• PoE FAULT LED indicates an exceeded overall max PoE output limit. Port PoE-out priorities will work in 3 independent sections (8 ports each) and overload will happen in any section that breach 150W consumption

@1207 Yep, the EAP225s do work if I set the port to "forced on", but I have confirmed with others who own the switch that low voltage POE devices handshake perfectly fine. This is an extremely popular switch, it has no (known) issues with POE. I don't have any low voltage POE devices myself (apart from the 225s), so cannot check myself.

I am really, really trying to avoid setting up any ports as passive POE due to the risks of accidentally blowing things up that don't support POE if down the line I reorganize. I am desperately hoping that there is a solution here that does not involve passive poe.

@1207 RE: Edits

1) I get no indicator at all for the port that the 225 is connected to. This seems to indicate that the eap225 does not have the correct resistance to start the POE handshake, as I do not get the flashing "problem in handshaking" indicator (handshaking is never even attempted).

2) Nope, no issues there.

@Virgo 

Passive POE is the only way to make the AP turn on, as the AP does not properly conform to active (at/af) POE signaling from what I can tell as per my previous messages.

Additionally, 802.3AF (which the 225 supports) is usually a minimum of about 44 volts, so I think I should be fine using 26v passive for testing purposes at least.

@aubey 

Might want to take a look at this link.  It is for an EAP225 ceiling, but the poe specs are the same for the EAP225-Outdoor. They appear to be saying the switch needs to be able to handshake with a device that can accept both passive and 802.3AF and this type of handshake is not defined in 802.3. 

@1207 

I have no idea what that thread is saying... If the AP claims to support 802.3af, it should work when plugged in to a switch which supports 802.3af.

On an unrelated note:



This is what my 225-outdoor shows up as when connected to the SDN controller. Why do they say [Custom]? Perhaps I got something from a weird batch?

@aubey 

I totally agree with you. If it is 802.3AF compliant, as it claims, it should work on a 802.3AF compliant switch. 

Not sure on the custom label.  I've heard they had to change something on the EAP firmware to be compliant with recent spectrum rule changes in Canada. I believe the new Canada firmware also prevents you from loading earlier versions, and firmware from other countries.

Maybe someone from TP Link will respond to this link. 

@aubey 

I also have the CRS328, with some EAP245's and an EAP225 Outdoor. 

Funny thing is the EAP225 used to work for a few weeks with the port PoE on 'Auto'. And after reboot, after moving equipment around, the EAP225 wouldn't power up. 

Thought the EAP was faulty until I forced the PoE Power On. 

I figure that's just the way it is with some devices.