Use LED display to inform users about "things happening" (WiFi config, updates, etc.)

george08 commented 6 years ago

We're thinking it would be good to introduce:

[ ] Bi-directional Larson scanner action when we're broadcasting 'museuminabox' network, and someone's trying to join it
[ ] Left-to-right Larson scanner action when they're setting up their own network
[ ] Ideally, some kind of error state (random?) if there's a problem
[ ] Flashing happy big green LED for a bit when they're all done and online

george08 commented 5 years ago

See #89

amcewen commented 5 years ago

ISTR there was a bit of a problem with trying to change the LEDs from inside NodeRED (apart from the big green one that NodeRED turns on itself). I assume it's because they get accessed by the progress script outside the NodeRED instance, but didn't spend lots of time getting to the bottom of it.

As I mentioned when closing #89, I think it makes more sense to work out what we might want to use the LEDs to display. Seems there are three general scenarios this would be useful:

During WiFi config, as listed above
When downloading new audio files in the background
During software updates (when you put the "check for updates" card onto the box) (see #55 for more background)

george08 commented 4 years ago

When the box says "I'll just restart" after using the Update card, the lights should all go off except the left-most orange one, and the normal progress startup lighting should happen, with a "Ready" at the end.

museuminabox / brain

Use LED display to inform users about "things happening" (WiFi config, updates, etc.) #49