Closed jk-ozlabs closed 4 years ago
The phosphor-dbus-interfaces spec defines sensor values as int64. From the spec :
int64
properties: - name: Value type: int64 description: > The sensor reading.
However, the dbus-sensors implementation exports values as double:
double
# busctl introspect xyz.openbmc_project.HwmonTempSensor /xyz/openbmc_project/sensors/temperature/Temp xyz.openbmc_project.Sensor.Value NAME TYPE SIGNATURE RESULT/VALUE FLAGS .MaxValue property d 127 emits-change .MinValue property d -128 emits-change .Value property d 0 emits-change writable
This causes issues for processes trying to read the sensor values using the standard interface.
Fix is here https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/11739
Brilliant, thanks. +1 from me.
Fixed in https://github.com/openbmc/phosphor-dbus-interfaces/commit/4ec6587fa908fe9df41cc0962ab6ff6446fbd54f , closing.
The phosphor-dbus-interfaces spec defines sensor values as
int64
. From the spec :However, the dbus-sensors implementation exports values as
double
:This causes issues for processes trying to read the sensor values using the standard interface.