[nemik]

The CC3XXX "SmartConfig" was complete garbage the last time I was evaluating it on a CC3200. It didn't work on 802.11n networks, only b/g. And that was when it worked. I got it only once trying on both an iPhone and Nexus 5, I would hate to have to answer any customers' support questions about using something so flaky.

The audio thing does require an app though to do provisioning, which I suppose isn't a problem for the kinds of people ordering this thing.

My preferred provisioning method is to let the little Dash-like device broadcast some setup or config access point. You connect to it, get an HTML UI to input target AP credentials into, and submit the form. It works from just about any device.

[joezydeco]

Totally agree about the SmartConfig. Interesting idea, very convoluted method.

Thankfully most devices I've been working on have a touchscreen to provision the SSID/PW, or we just ask the user to put it in a text file and inject it via a thumb drive. It really doesn't have to be this hard.

[nemik]

Agreed, but touchscreens and SD or USB means connectors, which are often a significant part of BOM cost and take up space. If you can do it all from the one-chip/module you have in there it's a big benefit when it comes to making something small and cheap.

[joezydeco]

Like I said, I've been fortunate to have alternate provisioning means.

I think the audio trick is a pretty elegant hack. Device agnostic and doesn't need a lot of handholding. But it also has an impact on the BOM. You need to add that Cortex M3 + microphone to sniff it out. Otherwise the whole thing could have been run off one chip like the ESP or GainSpan GS2100.

Doing the access point-to-client switcharoo is a good one too but needs a bit more instruction on the customer side, plus a way to whack the device back into setup mode when you need it.