These preference sets are actually used in the SmartHouses online simulation (in the menu for choosing a persona). I don't think having unsupported common terms that are not applicable to the SmartHouses is an issue - the online flow manager will take care of returning a payload with the supported settings only.

I can strip the unsupported settings out of those preference sets if you like but the sets themselves need to be present. I will add the smarthouses1.json and smarthouses2.json using common terms only. At this stage we don't have any application-specific terms defined.