Have piglet persist config in a file

[andrewdavidmackenzie]

when a config is sent to a piglet, but then power cycles or it is rebooted, or piglet app restarts for any reason, then the config is lost and it will restart with no config and not do anything to GPIO hardware.

When the config is sent over network, persist it to a file, that is checked for on every start as the default config.... so if it restarts for some reason the same config will be reapplied and we continue where we left off.

[andrewdavidmackenzie]

It should probably respond with the config when connected to also, so that the UI reflects the actual state :-/

[andrewdavidmackenzie]

This should persist each and every config change sent to it also... so maybe store each pin config separately with a different key in the ekv?

Then a config can simply be broken down and each pin stored separately.