1. clean up log
2. Make logging prompt a bit more beautiful
3. Get own logger for each module

under server/ introduce a common lib/ or helpers/ folder that contains the following files:

• mqtt/helpers
• lightshows/utilities/general.py
• lightshows/utilities/verifyparameters.py

Pattern Paint approach

• single column: led strip state during a particular frame
• row: time coordinate
• easy to edit with any pixel graphics program

variants

• flip rows and columns (better for widescreens)
• alpha channel is brightness

APNG

• no good editors for that
• easy to preview

create a driver interface for https://github.com/jgarff/rpi_ws281x

The open() method needs a Loader argument.
In configparser.py, get_configuration() has 2 open() calls that should be:
...
defaults = yaml.load(file, Loader=yaml.FullLoader)
...
user_config = yaml.load(file, Loader=yaml.FullLoader)

Benefits:

• make dependency management easier
• eliminate the need for sudo on raspi

have an abstract base class that drivers derive and use it throughout 102shows

it does the following:

• get the latest version from the stable/ branch
• (remove .git)
• install 102shows-server executable in /usr/bin
• provide further instructions

in base template

in class utilities

Unify p, p_verifier and p_preprocessor to p object with its own class, defined in server.lightshows.templates.base

Not sure if this is maintained anymore or not, but I could not get this to work on Raspbian Buster.

Got Node Red working.
Installed Mosquitto.
102shows/server/run.sh (per install doc) does not exist, tried server.py instead, looks like that works. Output:

2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO Starting MyLED
2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO Initializing LED strip...
2020-01-31 15:27:08 raspberrypi 102shows.drivers[10286] INFO sync-up
2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO Connecting to the MQTT Broker
2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO MyLED is ready
2020-01-31 15:27:08 raspberrypi 102shows.server.helpers.configparser[10286] INFO Successfully parsed defaults.yml as default configuration
2020-01-31 15:27:08 raspberrypi 102shows.server.helpers.configparser[10286] INFO Successfully parsed config.yml as user configuration
2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO Starting the show clear
2020-01-31 15:27:08 raspberrypi 102shows.server.mqttcontrol[10286] INFO subscription on Broker localhost for led/MyLED/show/+/start and led/MyLED/show/+/stop
2020-01-31 15:27:08 raspberrypi 102shows.drivers[10289] INFO sync-down

Went to myserverip:1880/ui and all I get is a blank screen.

similar to:
https://github.com/FastLED/FastLED/wiki/FastLED-Temporal-Dithering

We are doing this as an "idle" show. Must find an elegant way to start it directly after an other show ended

• refactor with cascading update trees of variable depth
• use attrdict instead of orderedattrdict
• offer logging facility, without logging in every case
• write tests

server-side realisation via MQTT will

To 512 or 1024 or 1000 values. Float representation?

there is:

• a new colour picker (seems a bit buggy)
• font awesome 4.7.0

advantages

• UI will be simpler
• presets are transparent and viewable via MQTT
• less complex MQTT messages

Exception classes are called with a debug string parameter, but init does not accept any parameters.

that makes it easier to share functionality between them

leave a toast notification for payloads in prefix/sys_name/notification

as implemented in #7

Max sent me a report about a similar chip to the APA102, SK9822: https://cpldcpu.com/2016/12/13/sk9822-a-clone-of-the-apa102/

To have full compatibility with the SK9822, an additional sending of the start frame must be added to the LEDStrip.show method.

as described here:
http://www.cambridgeincolour.com/tutorials/gamma-correction.htm
https://learn.adafruit.com/led-tricks-gamma-correction/

to wait for MQTT to be initialized. otherwise the presets will not be loaded properly

central question:
should we change num_steps_per_cycle or pause_sec or both?