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.

Sign up for GitHub

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

Jump to bottom

CM_BLINK_NEVER is hazardous with impOS 42 #35

Open
gjanvier opened this issue Dec 17, 2020 · 1 comment
Open

CM_BLINK_NEVER is hazardous with impOS 42 #35

gjanvier opened this issue Dec 17, 2020 · 1 comment

Comments

@gjanvier
Copy link

From impOS 42 and up, there will no longer be any period for which BlinkUp will always remain active after the code imp.enableblinkup(false); has run, even if the host imp is still in the BOOTING phase

So when we use a connection manager with blinkupBehavior set to CM_BLINK_NEVER, you may just brick your device if it cannot connect to the latest configured WiFi.
gjanvier referenced this issue in gjanvier/ConnectionManager Dec 17, 2020
Add option CM_BLINK_DONT_MESS_WITH_ME
52d00f3 
If you prefer to manage blinkup out of the ConnectionManager
@sourav-gadgeon
Copy link

Given the 10-second window for BlinkUp during a cold boot, we can utilize this period to perform BlinkUp. If this approach doesn't work, clearing the credentials during this window and then performing BlinkUp should resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gjanvier @sourav-gadgeon