Clone this repo:

Branches

  1. 162a1bd Avoid redundant virtual sensor updates on unchanged values by George Liu · 2 days ago master
  2. 6f12834 Remove unused variable 'path' in handleDbusSignalPropChange by George Liu · 2 days ago
  3. f8fcdc2 meson: use non-deprecated systemd packageconfig by Patrick Williams · 3 weeks ago
  4. 8459766 clang-tidy: format with config-clang-tidy by Patrick Williams · 8 weeks ago
  5. 04605fa move daemons to libexec by Patrick Williams · 8 weeks ago

phosphor-virtual-sensor

phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json from one of three locations:

  1. The current directory.
  2. /var/lib/phosphor-virtual-sensor
  3. /usr/share/phosphor-virtual-sensor

By default the repository will install a sample config into (3).

There are two types of data in this file.

virtual sensor configuration information

See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.

information to get a virtual sensor configuration from D-Bus

For example:

{
  "Desc": {
    "Config": "D-Bus"
  }
}

Sensors added this way can only use a set of restricted calculations. Currently supported types are Average, Maximum, Minimum, Sum and ModifiedMedian.

The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.

The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json).