Uggh. Then you'd have to reverse engineer the website's calls to try that method.   ...Or prepaid cards 😉 ... View more

+1 for "prepaid billing" mode. Despite the name, there is no need for actually implementing billing. Basically you pre-generate "prepaid" card PINs and configure the network to honor them for X hours/days of access. Very similar to how most hotels issue you a unique code that is only good for the duration of your stay.   Alternatively, check out the Dashboard API - you should be able to script a bunch of cURL (or Postman, etc) calls to create all those users. I haven't done Meraki-auth before, but I believe they need to be org/network admins with access level set to None. ... View more

My biggest warning on mesh: All mesh nodes will use the same channel as the gateway they're connected to. That means that worst-case your entire network will run on 2 channels... or you might get lucky and be able to mix some on 2.4 and some on 5Ghz... Neither is going to be a great experience unless you have very few devices and/or vary low bandwidth demands. This is going to create a massive "hidden transmitter" problem domain.   I second the push for as many cabled nodes as you can manage. 2 is better than 1, but 4 or so is probably a bare minimum for the 12 APs you want to deploy. You really want to make sure that each repeater can talk directly to a gateway. ... View more

I haven't looked into those particular features, but I have found that most (all?) of the Dashboard is REST/JSON based, so you can probably hack something up with a bit of reverse engineering. ... View more

 This is not restricted to MX either, I've seen this behavior across all Meraki products. ... View more