Allow device configuration with configuration file

[zehnm]

Enhance the app and hardware configuration handling.

Expected Behavior or Design

The following features should be implemented:

• Hardware configuration:
  • Option to enable / disable each device.
    If a device is disabled then simply use the mock implementation.
  • Configure i2c bus and device address id in configuration file.
  • Configure GPIO pins in configuration file.
  • Enhance json schema file to allow configuration file validation.
• General:
  • Possibility to use a different app or hardware configuration file.
    At the moment the configuration file names are hard coded.
  • Configuration profile support:
  • Load entirely different configurations based on a profile specified at app startup.

Current Behavior or Design

Only a small part of the hardware devices can be configured in hardware.json. However, the devices are mostly prepared to be configured in the hardware factory. What is missing is some glue code, enhancing the configuration file and exposing missing parameters in the devices.

Possible Solution

• Add command line options for different configuration files.
• Profile support:
  • Add optional command line parameter which loads different configuration files.
    E.g. add profile name as configuration file suffix
  • Propagate profile name to concrete hardware factory implementation.
    This allows to the factory to do whatever it needs to do for a specific profile.

[zehnm]

Enhancements are merged into develop branch and will be included in the next release.

Command line options:

mzehnder$ ./remote --help
Aufruf: ./remote [Optionen]
YIO remote app

Optionen:
  -h, --help            Zeigt diese Hilfe an.
  -v, --version         Zeigt Versionsinformation an.
  -p, --profile <NAME>  Use configuration profile.
  -c, --cfg <FILE>      Use configuration file.
  --cfg-schema <FILE>   Use configuration schema file.
  --hw-cfg <FILE>       Use hardware configuration file.
  --hw-schema <FILE>    Use hardware configuration schema file.
  --validate            Validate json configuration files and exit.

Note: German texts are default Qt strings and auto-translated based on OS country settings. The custom texts still need to be translated.

• The --profile option allows simple configuration profiles.
  E.g. using a profile name foobar will try to load config-foobar.json and hardware-foobar.json (with their corresponding schema files).
• The --validate options only validates the json configuration files and then exit.
  This is used to quickly validate configuration files and also to compare the validation implementation against other validators (e.g. NPM's ajv validate -s config-schema.json -d config.json) since the validator doesn't fully support json schema v7!
• The other cfg parameters can be used to overwrite a single configuration file