tinker and see if we want to use it instead of my polling

also ties in to which mode to operate

• simple client/server, could use the chipID to alway connect to lowest ID available
  • easiest to get up and running (+)
  • always connects to the same master device (-)
• mesh network
  • slower, lots of switching
  • how to know when to stop propogating messages?
  • how to know who is leader? (broadcast number of connected devices, connect to the largest?)

https://github.com/adafruit/piccolo/tree/master/ffft

instead of incrementing by one, increment as many times as necessary to catch up to where we should be

does the master blast out each LED color every cycle?
(would allow each google to share custom animations)

or

does the master occasionally send necessary values (hue, modeCounter, mode, millisSinceLastModeChange, etc.) and allow each subordinate to calculate the proper LEDs for each cycle?
(would require all units to have the same animation code, to be sync'd)

https://arduino-esp8266.readthedocs.io/en/latest/esp8266wifi/scan-examples.html#async-scan

mod the current pattern number variable so outdated goggles don't just freeze or something