Good morning Adam,
I found (my) problem.
The sensor was delivering a value above the precision scale of the oid
"entPhySensorPrecision".
By adjusting the precision the sensor was identified perfectly well.
Again I apologize for this.
Everyone have a great weekend.
Hugs,
--
Kleber Coelho
Campus F
Hi Adam, I really like your way of communicating. huahua!!
As I said in the first message, I would like to understand if there is any
other identification mechanism to adapt MY code.
In my tests I changed the value of the oid " entPhySensorType " and the
observium was recognizing sensors of other
Have you actually verified that the device is returning the correct data?
It seems unlikely that out of millions of temperature sensors monitored
via ENTITY-SENSOR-MIB, yours would be the only one that doesn't get
identified as temperature, no?
Thanks,
adam.
Kleber Cristiano Santilli Coelho
Hi Adam, how are you?
Thanks for the feedback.
The sensor is not recognized as being 'temperature', it is left as unknown.
So it doesn't generate the graph automatically.
Thanks
--
Kleber Coelho
Campus Fernando Costa
Universidade de São Paulo
(19) 3565-4321
Em sex., 23 de set. de 2022 às 10:3
What doesn't work?
Kleber Cristiano Santilli Coelho via observium wrote on 23/09/2022 14:22:
Good Morning!
I hope you're all well.
I apologize if the question is inappropriate.
I'm developing an IOT module and I use the "ENTITY" MIB for the sensors.
I saw that Observium handles this MIB automat
Good Morning!
I hope you're all well.
I apologize if the question is inappropriate.
I'm developing an IOT module and I use the "ENTITY" MIB for the sensors.
I saw that Observium handles this MIB automatically, using the
entPhySensorType OID to distinguish the sensor types and it works great,
excep
