the spare you grabbed and tested, was it a spare AP, or a space ICX? if you had the problem even on a separate newly booted ICX, that def sounds like the unifi device was having issues. if it was a spare AP, and the same icx with the prob was still having the issue on the different AP, then yeah it sounds like a strange icx bug. what OS and PoE fw version are you on?
Sorry for the confusion. I tried spare ap, cable & port in the same stack member. I have a 2 stack setup using the 40G QSFP connectors on back. I don't have another ICX6610 that has POE, so as a last resort I kicked just the POE stackmember which has my access points (only) in it.
I did everything according to the guide you setup (much thanks btw!).
SSH@BCORE#sh ver | i Version
SW: Version 08.0.30uT7f3
SW: Version 08.0.30uT7f3
Boot-Monitor Image size = 370695, Version:10.1.00T7f5 (grz10100)
Not sure offhand how to get the poe firmware version, but I remember upgrading it as per your guide.
I kinda wish I had waited for a deal, as I found the 48 port POE model with 2 PS for about $150 shipped on eBay which I thought was superb.
For my first one, non-poe, 48 port, It was $90 but only with one power supply.
To be fair I use Cisco all day at my day job and have had, at one time, 3 Cisco TAC Teams working for 24 hours straight on a multicast over GRE over ipsec issue that was not solvable by them. I found a workaround as I was on a tight time schedule & we eventually ended up removing that equipment as it was older (although still supported). I"m kinda famous @ work for finding issues

There is an HP G6 or G7 BIOS out there that has a bios memory setting bug I found. HP Later released an updated bios and the only fix was the bug I found. So maybe it's just me & not the equpment
