I figured out the root cause is the sensor type I am using is ADT75 rather = than TMP75. So it works after I changed the "Type": "ADT75&q= uot; in the JSON configuration file and added ADT75 in the devices.hpp.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[ 33.154935] lm75 6-0049: hwmon1: sensor 'adt75'

[ 33.160287] i2c i2c-6: new_device: Instantiated device adt75 a= t 0x49

[ 33.169894] lm75 6-004c: hwmon2: sensor 'adt75'

[ 33.175201] i2c i2c-6: new_device: Instantiated device adt75 a= t 0x4c

[ 33.184658] lm75 6-004d: hwmon3: sensor 'adt75'

[ 33.190007] i2c i2c-6: new_device: Instantiated device adt75 at 0x4= d

root@hudsonbay-obmc:~# cat /sys/bus/i2c/devices/6-004d/hwmon/hwmon3/temp1_i= nput

41312

root@hudsonbay-obmc:~# cat /sys/bus/i2c/devices/6-004d/hwmon/hwmon3/te= mp1_input

41375

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

Thank you for your support.

Regards,

Chris Chen

=D0=F6=CB=EC=ED=BA: Andrei = Kartashev <a.kartashev@yadro.com>
=D0=F6=CB=EC=EC=ED=D1=A2: 2021=D2=B410=EA=C529=EC=ED =F9=BB=E7=ED 05= :45
=E2=A5=CB=EC=ED=BA: Chris Chen (TPI) <Chris.Chen3@flex.com> =F1=AB=F2=A9: Re: =FC=DE=DC=DD: [entity-manager] Question about temp= erature sensor stops update

Oh, that sounds really strange. Are you sure? = ;
When you read it raw (cat /sys/bus/i2c/devices/6-
004d/hwmon/hwmon3/temp1_input) is it also always same? If yes, then, it
is something in kernel - try to experiment with new_device sysfs
interface.

On Fri, 2021-10-29 at 08:50 +0000, Chris Chen (TPI) wrote:
> Hi Andrei,
>
> Thanks for your prompt reply and the explanation of #2, I understood > now.
>
> For question #1, let me rephrase it, please. I mean the temperature > value I read is always the same. The value always shows 40.187, it
> wouldn't be changed even I read it again after a while. But if I
> declare the temp sensors on the I2C bus node in my dts, the value will=
> change all the time. Do you have any idea about this?
>
>
> Regards,
> Chris Chen
>
> =D0=F6=CB=EC=ED=BA: Andrei Kartashev <a.kartashev@yadro.com>
> =D0=F6=CB=EC=EC=ED=D1=A2: 2021=D2=B410=EA=C529=EC=ED =F9=BB=E7=ED 04:3= 3
> =E2=A5=CB=EC=ED=BA: Chris Chen (TPI) <Chris.Chen3@flex.com>; ope= nbmc@lists.ozlabs.org
> <openbmc@lists.ozlabs.org>
> =F1=AB=F2=A9: Re: [entity-manager] Question about temperature sensor s= tops
> update
> Hello,
>
> I didn't catch, what is your problem. As I see from the logs,
> everything is fine: temp sensors instantiated, dbus objects created, > readings present. What's wrong?
>
> As for FruDevice: yes, it's kind of weird behaviour: it exposes not > only actual FRU devices but also other I2C devices. You can introspect=
> that objects and see that they exposes
> xyz.openbmc_project.Inventory.Item.I2CDevice interface instead of
> xyz.openbmc_project.FruDevice
>
> On Fri, 2021-10-29 at 08:02 +0000, Chris Chen (TPI) wrote:FruDevice > > Hi everyone,
> >
> > Actually, I have 2 questions as below:
> >    1. I got understood from others on the mailing = list, that I don't
> > have to declare EEPROM or temp sensors on the I2C bus node in my = dts,
> > and it should be fine even I did it at the beginning. So I tried = to
> > remove this declaration in dts, then the sensor value I got is fi= xed,
> > no update. Can someone help to take look at why it is?
> >      Here are som= e logs that appeared automatically after the
> > system booted up.  It looks like that entity-manager wo= rks fine. And
> > the commands I used to check value.
> >      =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >      [ 23.= 713596] lm75 6-0049: hwmon1: sensor 'tmp75'
> >      [ 23.= 718894] i2c i2c-6: new_device: Instantiated
> > device tmp75 at 0x49
> >      [ 23.= 728520] lm75 6-004c: hwmon2: sensor 'tmp75'
> >      [ 23.= 733779] i2c i2c-6: new_device: Instantiated
> > device tmp75 at 0x4c
> >     [ 23.7= 43707] lm75 6-004d: hwmon3: sensor 'tmp75'
> >     [ 23.7= 49042] i2c i2c-6: new_device: Instantiated device
> > tmp75 at 0x4d
> >
> >      # busctl int= rospect xyz.openbmc_project.HwmonTempSensor
> > /xyz/openbmc_project/sensors/temperature/DIMM_P1_EFGH
> >      xyz.openbmc_= project.Sensor.Value = ;
> > interface - - &nb= sp; &= nbsp; -
> >      .MaxValue &n= bsp; = = ;
> > property d 127 &n= bsp; = emits-
> > change
> >      .MinValue &n= bsp; = = ;
> > property d -128 &= nbsp; = emits-
> > change
> >      .Unit = &nbs= p; &n= bsp;
> > property s "xyz.openbmc_pr= oject.Sensor.Value.Uni... emits-
> > change
> >      .Value = ; &nb= sp; &= nbsp;
> > property d 40.187 &= nbsp; = emits-
> > change writable
> >
> >      # cat /sys/b= us/i2c/devices/6-
> > 004d/hwmon/hwmon3/temp1_input
> >     40187
> >     =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >    1. From my understanding, there is "detect= ion daemon" which scans
> > I2C bus looking for EEPROMs with IPMI FRU data. However, I found = all
> > devices on the I2C buses would be listed, not only Fru devices, w= hen
> > I used the command below. Is this correct?
> >     # busctl tree= xyz.openbmc_project.FruDevice
> >     `-/xyz
> >       `-/xyz= /openbmc_project
> >       = `-/xyz/openbmc_project/FruDevice
> >       = |-/xyz/openbmc_project/FruDevice/0_80
> >       = |-/xyz/openbmc_project/FruDevice/0_88
> >       = |-/xyz/openbmc_project/FruDevice/2_108
> >       = |-/xyz/openbmc_project/FruDevice/2_112
> >       = |-/xyz/openbmc_project/FruDevice/2_68
> >       = |-/xyz/openbmc_project/FruDevice/2_72
> >       = |-/xyz/openbmc_project/FruDevice/3_22
> >       = |-/xyz/openbmc_project/FruDevice/3_50
> >       = |-/xyz/openbmc_project/FruDevice/4_56
> >       = |-/xyz/openbmc_project/FruDevice/5_48
> >       = |-/xyz/openbmc_project/FruDevice/5_81
> >       = |-/xyz/openbmc_project/FruDevice/6_73
> >       = |-/xyz/openbmc_project/FruDevice/6_76
> >       = |-/xyz/openbmc_project/FruDevice/6_77
> >       = |-/xyz/openbmc_project/FruDevice/7_80
> >       = |-/xyz/openbmc_project/FruDevice/7_88
> >       = |-/xyz/openbmc_project/FruDevice/8_101
> >      = ; `-/xyz/openbmc_project/FruDevice/hudsonbay    = =A9=AC
> > this is the probe name we define in JSON configuration
> >
> > Thanks.
> >
> > Regards,
> > Chris Chen
> > Legal Disclaimer :
> > The information contained in this message may be privileged and > > confidential.
> > It is intended to be read only by the individual or entity to who= m it
> > is addressed
> > or by their designee. If the reader of this message is not the > > intended recipient,
> > please immediately notify the sender and delete or destroy any co= py
> > of this message!
>

--
Best regards,
Andrei Kartashev

--_000_DM6PR08MB5514B899D36CC4D70D02A1A2DC8A9DM6PR08MB5514namp_--