From fc2818b927e8331daf6be974e2cd821f14fc7f3f Mon Sep 17 00:00:00 2001 From: Andrew Welker Date: Tue, 21 Apr 2020 08:56:12 -0600 Subject: [PATCH] Updated ConfigurationStructure (markdown) --- ConfigurationStructure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ConfigurationStructure.md b/ConfigurationStructure.md index 63251de..d61b7e8 100644 --- a/ConfigurationStructure.md +++ b/ConfigurationStructure.md @@ -139,7 +139,7 @@ Some additional details about specific properties that are important to note: * "key": This value needs to be unique in the array of devices objects * "uid": This value also needs to be unique for reasons related to configuration tools and template/system merging -* "type": Think of this as a way to identify what specific module you might associate with this device.  In Essentials, this value is used to determine what class will be instantiated for the device (ex. "necUniversal" or "samsungMdc" for two types of displays) +* "type": Think of this as a way to identify what specific module you might associate with this device.  In Essentials, this value is used to determine what class will be instantiated for the device (ex. "necmpsx" or "samsungMdc" for two types of displays) * "properties":  This object is used to store both specific and miscellaneous data about the device. * Specific data, like that shown above in the "control" object has a pre-defined structure. * Other data must be stored as objects or new properties inside the "properties" object such as "someCustomProperty" in the example above.