Wow. You're straining my memory.
Let's see...
I wrote a script called "ruckusconf" that I used to automate ruckus commandline stuff.
That can be found here:
https://github.com/bot779/ruckusconfThe command I used to download the "get detected" output was:
./ruckusconf --debug --outfile getdetected --timeout 300 --command 'rksap_cli -A "get detected"' $CONTROLLER
(Where $CONTROLLER is the IP of your active ZD controller)
In order to get things going quickly (in case you have trouble getting the ruckusconf script working) I'd suggest invoking the linux "script" command, ssh-ing into your ZD, getting into debug mode and then typing:
rksap_cli -A "get detected"
I don't know if the output of "get detected" has changed since the last few firmware updates...
The apnames.sed command was autogenerated by another set of scripts called makeapnames.sed and getruckusapnames.
That can be found here:
https://github.com/bot779/getruckusAgain, this depends on certain behavior of the ZD which may have changed.
(in this case, responses to SNMP queries)
The "showdetected" script cleans-up the "get detected" output a bit and puts it in the file called "getdetected".
I guess I didn't consider that script to be "clean" enough 'cause I didn't post it online anywhere.
See if you can download the output of "get detected" to a file.
If you can, you should be able to get some level of function just by grepping for the mac address of a client.
Let me know if that worked for you (or how far you got) and I'll see if I can clean-up the rest of the scripts.