@zach this is an extremely cool feature you guys are adding.
A couple of questions though.
In Manual/SemiAutomatic modes, is it possible to run the Usercode while the wifi is establishing?
If the Spark Core is not connected to the cloud. It would be nice that if I flashed an OTA update via the web interface, that the OTA would be pending until the Spark Core comes online again? Currently if I do a deep_sleep and do an OTA, it’ll fail. I have to reset the Spark Core…
Some of the connection steps are blocking - in particular, the one that often blocks longest is the connect() call (where the device is flashing cyan). So your usercode will run but will be interrupted by blocking calls. You should test extensively to understand the impact this will have on the code.
Great point, and this leads to a whole big long conversation about message caching, which is an important and significant feature that we hope to get to sometime later this year. We will definitely be putting in place mechanisms for caching messages in the cloud, but we haven't yet figured out how this will work.
So, any clue exactly when this week the code will drop?
An intern working with me is using this as part of her project, and somewhat humorously (but not for her) the cool factor for her final presentation of work this week will depend in part on having this function working.
If she needs it now, she can build locally, this functionality is all part of the master branch of the core-firmware repository, just hasn’t been pushed out to the IDE yet
Probably still a few weeks away; our current priority is bug fixes, stability improvements, and testing infrastructure, rather than new features. That said, I’ll keep it in mind for prioritization in the near future.