The way I interpret the integration guide the formatting is handled by the lib itself. config_load merely offers you a way to store the config in an independent way in non-volatile memory. config_load parses the config byte array from bsec_serialized_configurations_iaq.c and places the result in the work_buffer. The parsed work buffer is then handed to bsec_set_configuration. So in summary, the lib should be handling the parsing, bsec_set_configuration is then loading the config Regards, Tobi
... View more