For a few days, I can’t blinkup my imp004 devices when I start them. Then I found this:
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
Am I the only one who find this change extremly dangerous, with a high risk to brick a device? The only solution I found is to clear the device settings at the exact second it starts. Then I have several seconds to configure it with my WiFi credentials.
For the devices that are online, I must provide a patch to quickly fix them, calling imp.enableblinkup() with I dont know what: true or false? at startup of after 60 seconds ?
Here are my needs:
- I want to be able to blink up in the 1st 60 seconds
- In my code, I don’t call imp.enableblinkup() so far, but I use the ConnectionManager lib that implicitly deals with it
- I often call cm.connect() and cm.disconnect() to reduce power, and I don’t want the LED to blink at connection or disconnection. So I guess none of the “blinkupBehavior” from that lib would match my needs.
I guess I would need to open a ticket in the ConnectionManager github to ask for a “NoBlinkUpBehaviour”, but what should I manually do with the imp.enableblinkup to get back to the previous behaviour?
Thanks for your advice