Try using Particle CLI and tell it the security type yourself. That got my first core online and then after that anytime I reset it has worked from the app. Let it update after it connects, will flash magenta, reboot…leave it be until it goes into a cyan breathing state.
Is there a lot of traffic on the client’s wifi network? I’m not positive (maybe somebody at particle can elucidate), but due to the way that the Core’s (or really, the Broadcom SoC’s) Smart Config works, I imagine that high-traffic could cause the wifi setup to fail.
If possible, it might be worth trying the config at a time when you’re sure that the network is pretty quiet.
@dougal thanks, I don’t think it is problem. He is home alone at the moment. @LukeUSMC I may have to… the know process is pretty easy, I just remember that installing node.js can be non-trivial.
If you should happen to have problems with node.js you’d only need any serial terminal (e.g. PuTTY).
If you can do it via TeamViewer or any other remote assistance program, you might safe on telephone time too
Huh? That part of the docs seems to have vanished (got lost during the recent overhaul).
But in short, when putting your device into Listening Mode, it opens an USB serial port and listens to a few one-letter commands.
The most important are “w” for entering the WiFi credentials and “i” to get the device ID for claiming the device e.g. via Particle Build.