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

Particle.connect/disconnect docs suggestion #445

Open
towynlin opened this issue Jul 27, 2016 · 1 comment
Open

Particle.connect/disconnect docs suggestion #445

towynlin opened this issue Jul 27, 2016 · 1 comment

Comments

@towynlin
Copy link
Contributor

https://community.particle.io/t/unlocked-device-in-company-approved-device-wont-upgrade-to-released-firmware-unless-it-is-reset/24508/4?u=zachary

"In most cases, you do not need to call Particle.connect(); it is called automatically when the device turns on. Typically you only need to call Particle.connect() after disconnecting with Particle.disconnect() or when you change the system mode."

My understanding now is that you must call Particle.disconnect() and Particle.connect() if you expect firmware updates to occur automatically from a corporate dashboard. In addition, it does sound like you need a minimum time of being disconnected in order for a connect to work properly. If I'm understanding this correctly, you may need to document that as well.

@monkbroc
Copy link
Member

From the discussion today the OTA happens on handshake. Do we have a known way to trigger a new handshake or another way to force the firmware to check for new product firmware? Particle.connect doesn't look like the right call for this.

@monkbroc monkbroc added this to TODO in Docs prioritization Feb 27, 2017
@monkbroc monkbroc moved this from TODO to Prioritized in Docs prioritization Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Docs prioritization
  
Prioritized (Mesh prep)
Development

No branches or pull requests

2 participants