hAP AX2 POE issues

You’re right, the passive PoE-in is rarely mentioned for MT devices with 802.3 af/at PoE-in support. But it was explained multiple times (by MT staff) that all MT’s PoE-in capable devices support passive PoE-in. Implicit data affirms this in multiple places:

  • PoE-in voltage range, as you wrote, is wider than 802.3 PoE standards specification, which by itself hints at passive PoE capability
  • text in product description
    e.g. description of cAP ax has this: “you can use cAP ax to power other devices … or even another cAP ax!”. The PoE-out explicitly specifies “Passive PoE up to 57V” … combined with statement from product description it means that PoE-in should be passive-capable as well.
  • officially endorsed related products, such as RB-GPOE power injector (actually included with cAP ax) which is passive PoE injector

And, probably to be added to the list (but it’s not MT specific): only rare PoE-powered 802.3 af/at/… compliant devices refuse to be powered if PSE (power provider) doesn’t perform full power handshake … most of them simply accept power (if voltage is within specified range). And this behaviour is what IMO defines “passive PoE” … powering without handshake.