Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make wiki about bootloader modes, recovery modes, config mode #18

Closed
digistump opened this issue Jan 28, 2016 · 4 comments
Closed

Make wiki about bootloader modes, recovery modes, config mode #18

digistump opened this issue Jan 28, 2016 · 4 comments

Comments

@digistump
Copy link
Collaborator

@digistump digistump commented Jan 28, 2016

Conditions for entering wifi config:
WiFi configuration is missing or corrupted.
Still cannot connect to WiFi (not Particle, but WiFi) after 5 consecutive tries - aka no internet available.
OTA Update Failed - either the update itself failed, or the newly booted ROM failed.
There is no User ROM or User ROM is invalid/corrupt.
Pin 1 or 6 held LOW during boot (selectable at compile time).

@pfeerick
Copy link
Contributor

@pfeerick pfeerick commented Feb 25, 2016

This may not be the best place to discuss this, but I have a question about the behaviour associated with "Still cannot connect to WiFi (not Particle, but WiFi) after 5 consecutive tries - aka no internet available."

Can you make it so that it still retries to connect to it's last remembered AP, and if a connection is re-established, it jumps back into the user sketch.

Usage example - we had a 3ish hour power outage due to maintenance to the power lines. Both Oaks went into wifi config mode, and didn't auto-connect back to the configured wifi, as they were running on battery USB and survived the outage. This could have still been an issue if they were on wall-warts, as I don't know if the wifi would boot up into time to service the Oaks before they auto-entered wifi config mode. So I had to log into the wifi setup, and reconnect to the AP, and it's back to normal now.

@emardee
Copy link

@emardee emardee commented Feb 25, 2016

That was my immediate question too when reading how it now works... sounds like this needs to be a configurable option so we can tailor the behaviour to match our needs.

Also on same train of thought what are the security implications if the Wifi router drops, and therefore our Oaks start broadcasting on their own open wifi to get a new wifi config?

I could imagine scenarios where people would want their Oak to just keep hunting for just the existing secure pre-configured wifi only, and then ONLY re-enter the wifi config routine at a pin held LOW event or tge other valid scenarios given above etc.... but just not during a router / wifi / internet outage.

@digistump
Copy link
Collaborator Author

@digistump digistump commented Mar 23, 2016

This option is added in 1.0.1 coming out now

@digistump digistump closed this Mar 23, 2016
@emardee
Copy link

@emardee emardee commented Mar 23, 2016

Thanks Erik. Look forward to playing with that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants