We have our Photons and having great fun blinking. At the moment when we travel between work/home we seem to have to re-register them to get them to work with the online dev env.
We do this by pressing and holding the left button for 10 seconds.
My question is, if I integrate one of these in to a product, and test it at our offices and then ship to a customer, how do they get it to connect so that it can start feeding data back. We can’t expect them to download the Phone App and do the reset thingy can we?
I would really be great if someone could explain this to me - or point me to where it is written.
Holding the mode button for 10 seconds will actually erase all credentials. Holding the mode button for 3 seconds until it starts blinking blue (listening mode), will allow you to enter new credentials. These will be stored on a FIFO principle, for a given amount of credentials (I remember the Core stores 7), whereby the device will cycle through them until it finds a matching one.
An alternative is to write a program that turns on Serial every time is it plugged in and maybe a special character like “w” will prompt the user for Wifi credentials. Actually the same as how Listening mode works now
I think what I need is a recipe for users that wish to produce commercial products, how do I do this, what techniques do I use, which parts of the API etc.
I Think I’ll put a post in the general section on this.
I haven’t integrated this on the photon yet… This is spark core stuff… But if I don’t connect to a network in 90 seconds I go into “listen mode” and allow the user to provide the device with new credentials… If I am in “listen mode” and I don’t get new credentials for 4 minutes. I try to connect again using my current credentials (in case the network was down temporarily). The unit toggle between modes until it connects to the particle cloud.
@ScruffR I’m also interested in adding wifi credentials via a browser without the app. I’ve read about softAP in multiple places, but have seen a lot of fragmented answers on this. Is there a solution for easily changing/updating wifi info this way?
We have built a fully working Particle based solution for our electric car charging product
However we cannot deploy our solution because I am concerned about reliability of particle network set up procedure
Here is the issue
Using a clean module registered to our account. Select Setup Option
Once network credentials are added by Our Mobile App or using Particle Web App or Tinker App Wifi setup is reliable with no problem.
Press the Select Setup Button to initiate connection to new Wifi Network
The process is appears very unreliable.
We get loads of failures (at least 70% during testing with Photon Dev modules)
Connecting to the Photon module during setup from a desktop or laptop using win 10 results in the following behaviour
a) Particle Connection being refused
b) Particle Hotspot Connection established for a few seconds before a RED LED flashing and disconnecting again from the setup PC
In its current state we are unable to deploy a Particle based solution to our customers without causing massive customer service issues
Can anyone advice of a fix or is this known problem with Particles hardware/software?
First, to assist we’d need to know what system version your devices run on.
We’d also need how your code is handling the setup process.
When you mention red flashing, stating the actual red pattern you see would be good.
Connect how (wired/wireless) to what (device to cloud, computer to device, mobile device to device)?
Yes, what kind of and how often exactly?
One possible pattern would be SOS (… — …) x slow blinks (… — …).
Are you using the default SoftAP http sample code, or a reworked version?
If reworked, how does it now look?
With or without SYSTEM_THREAD(ENABLED)?
I have played a lot with SoftAP and had a ~100% success rate, but then I know what not to do in the SoftAP handlers.
Also the rest of your code might be so close to the memory limits that engaging the Listening Mode SoftAP might tip the device over the edge.