tree 953ff60b16ee3c92ec32de18e0ab3549ffc3ce94
parent 2da370eef3a4bf6410a442c735bb0509d94e0887
author Josh Lehan <krellan@google.com> 1572537118 -0700
committer Josh Lehan <krellan@google.com> 1572981475 +0000

PSUSensor: Individual customization of sensors

This is a large patch, but it adds a great new feature.

In the "Exposes" stanza of your Entity Manager JSON file,
you can now customize the properties of each individual sensor.

Each sensor, identified by one of the Labels strings,
now accepts 4 optional parameters. They are x_Name, x_Scale,
x_Min, x_Max, where x is the Labels string.

This lets you customize the PSUProperty dynamically at runtime.

If x_Name is given, it will take precedence, overriding
the prefix/suffix synthesis usually performed by PSUSensor.
If any of these parameters are not given,
the hardcoded PSUProperty table will still be used as defaults.

Example usage:
{
  "Address": "0x34",
  "Bus": 12,
  "Name": "MyDevice",
  "Labels": ["vin", "vout1", "iin", "iout1"],
  "vin_Name": "MyDevice_Vin",
  "vin_Scale": 500,
  "vin_Min": 10.0,
  "vin_Max": 90.0,
  "vout1_Name": "MyDevice_Vout",
  "vout1_Scale": 1000,
  "vout1_Min": 5.0,
  "vout1_Max": 45.0,
  ...
}

Signed-off-by: Josh Lehan <krellan@google.com>
Change-Id: I741b61d8192a3bff364461247f31ca20edda2198