Thin client AP's not showing up in the Nodes with problems displays

I believe the root cause of the issue is that thin APs are not managed nodes in Orion NPM. You may want to configure an advanced alert for your APs a leverage the All Triggered Alerts resource instead of the Nodes with Problems resource. 

I've pretty much known that was the answer all the time.  I'm trying to play devils advocate here because Solarwinds support won't come out and say that.  While I appreciate you responding, I actually want some one from Solarwinds to admit that is the case.  In addition if they can trigger an alert for a down thin AP by detecting it off the associated wireless controller why can't that same information be pushed to the table support Nodes with problems?  I've go over 1000 AP's in my network with 80% as thin client and the other 20% will be converted this year.  As it stands right now the wireless module basically functions as a stand alone module with the exception of alerting.  

Just a question, if I could.. The canned AP Alerts doesnt seem to allow a trigger based on the associated Controller name! Do you know how I could do this?

How can I write an alert to sent to a specific group based on the asscoiated controller name, when an AP goes down.

I see the macro "${Controller}", but when constructing the alert there are only stats available when you choose a trigger type of wireless controller.

Just a question, if I could.. The canned AP Alerts doesnt seem to allow a trigger based on the associated Controller name! Do you know how I could do this?

How can I write an alert to sent to a specific group based on the asscoiated controller name, when an AP goes down.

I see the macro "${Controller}", but when constructing the alert there are only stats available when you choose a trigger type of wireless controller.