Workflow: Embedded device discovery

[jonnor]

All these scenarios are assuming that the Flowhub (Chrome) app is installed, and that the devices do not come bundled with MicroFlo/NoFlo out-of-the-box. It also does not yet consider when a device is plugged into another device with NoFlo on it.

WiFi-enabled uC (Spark Core/mbed)

• Enable WiFi connectivity between device<->computer/tablet
• Flash MicroFlo onto device (Allow to flash (pre-built) image onto microcontroller microflo/microflo#53)
• Runtime UUID put in EEPROM (Support storing runtime UUID in EEPROM microflo/microflo#51)
• Device announces itself w/UUID over Zeroconf (ZeroConf/Bonjour discovery of local runtimes #205)
• Flowhub shows notification that new runtime is available, allows to register to your user

USB/BT/serial uC (Arduino/Teensy/*)

• Plug device into computer
• Flash MicroFlo onto device
• Detect runtime over USB (USB/serial automatic discovery microflo/microflo#52)
• Flowhub shows new runtime notification

Embedded Linux w/Ethernet or WiFi (BeagleBone/Raspberry Pi)

• Connect Ethernet
• Install NoFlo to device (TODO: images/installables)
• Device announces itself w/UUID over Zeroconf (ZeroConf/Bonjour runtime announcement  noflo-nodejs#6)
• Flowhub shows new runtime notification

From here things go into monitoring & debugging (#275).

[bergie]

The new live mode in the fluxify branch should help quite a bit here.