For me at least, the hardware version is shown on the status page within the admin panel. Glad to report that things here are still fine, both APs have been rock solid thus far. If you're really at your wits end then it seems your options are limited if you want a reasonably priced 11n AP with POE built in - it's got to be between the D-Link DAP2553, or the Netgear WNAP210, the latter which I wouldn't trust as far as I could throw it based on my experiences with Netgear WG102 APs.
To be fair, I think the support we're seeing here on Cisco Community is probably better than you're likely to find anywhere else for a product at this price point - at least there's a Cisco employee here keeping an eye on proceedings, even if there are some issues that still haven't been resolved.
Shepner, when the AP hangs, what exactly do you have access to? You can ping the AP, but can you access the admin pages on the APs webserver? I'm just a little curious because I had a problem that might be similar, which was the major influence in purchasing my WAP4410s. I had a pair of Ericsson APs, and besides the inherent instability and console only administration (no web admin!), I could never get roaming working properly with them. If I roamed from one AP to the other, the network would not realise that I had moved, and it would either take 15 minutes or a power cycle to be able to get back on the network. I could still ping the AP itself the whole time. I think this may well have been something to do with the address tables on the switch not updating, but I never managed to sort it, as I gave up on those APs in frustration due to the other aforementioned problems before I ever really got to resolving the roaming. With exactly the same switch (and same config on the switch), roaming worked straight out of the box with the WAP4410, so I can only assume that every time a client associates, the access point is sending out a graceful ARP request to the switch.
