Welcome @joe-wifi,

Unfortunately, I don't think this is possible the "ssh capability" doesn't give you admin/CLI access like you would think (and I thought) it would.

A better solution might be to have an SSID password rotation feature in Omada / OC200 to schedule the password to change based on a list, etc.  Though I think you can currently schedule SSID's to turn on and off on a schedule.  I wondering if you could configure it to turn on and off multiple copies of the same WLAN config (aka set(s) of SSID) that are all essentially the same, save for their passwords.

Is this for some sort of voucher application where you don't want repeat customers (or squatters) to remember the password from before?

-Jonathan

Hello and thanks.

In few words I just don't like captive portals and I prefer to have different wifi password every day. Imagine everyday clerk/operators get an email with the new password and they know to hand out that one if guests arrive.

I implemented this system this morning. Works perfectly with a simple script sending http requests to the eap unit (given the ssh is rather limited with its default users/permissions and it would take me longer to reverse engineer that). If anyone is interested I'll share it on github.

Obviously if tp-link is reading this, please consider adding this as a feature! Daily email rotation with email sent with new password! Until then I'll just have a docker running with a cron at midnight with the above script.

Cheers