Customized defaults profile that can be enabled (use customized defaults) / disabled (Outback firmware defaults). Example use for this is battery configuration wizard for supported battery modules that can populate a customized default settings profile. Enter battery chemistry and listed battery module and quantity of each (mixing battery module types being supported by at least SimpliPhi) in a list, next your strategies i.e. temperature range and 80% DoD / 90% DoD / 100% DoD, and a confirmation page which shows the new settings and asks for clarification on settings that are different between modules listed (like Ah) or existing customized defaults settings and further links for the user to read about in the application notes. Lastly the wizard saves all of the selected customized default settings to be saved to the custom default settings profile slot. The OpticsRE (and potentially other UI-having devices via firmware update) would thus now have a "Display Customized Defaults" enable/disable. None of the customized defaults profile actually changes any settings unless the user takes further action to "Reset to customized defaults" or goes through all the settings in OpticsRE and visually assesses the new defaults alongside the existing values. It is just an advanced feature that can guide the user to have settings that make the most sense for their system. Customized defaults profile should be exportable "save as" and importable "reload from SD and confirm changes" through a similar wizard to the SD card and/or downloaded and uploaded. Allow a nickname field to be assigned to the active customized defaults profile with a so that they can be shared and stored unambiguously although always under the same filename on the SD card as we do with power grid data. The beautiful detail to this feature is no device firmwares need to be modified but if they are later updated they can add support for this after OpticsRE has implemented it. Also by having a battery configuration wizard or generator start wizard and so on that re-uses the validation final steps to only confirm newly suggested customized defaults that are different from the existing customized defaults profile and allows to pick which ones are saved, plus a capability to reset the customized default settings slot to equal the firmware default settings, we bake in a way to correct for changes in datatypes that are stored while also building a basis for users and OE's to build their own wizards. Wizards could be OpticsRE-only but the customized defaults profile slot could be implemented by SD card file and/or OpticsRE. In the case of two competing customized defaults profiles from different devices, the one that is local to the method of access should win, until, some method is invoked which would seek to modify either customized defaults profile(s) and then it would go as already said to resolve the conflicts by asking the user for clarification. In this way OpticsRE and possibly the Mate3s gateway could be used as the editing and creation tools, while all devices benefit or ignore the feature without needing any support at all. It's 2019 y'all, even my $29 wifi router has this level of functionality.