How to handle sensors

Configuration
1

Hi,

I have a problem with the one-wire server called OW-server. I am collecting information from the sensors using SNMP and it works well.

The problem is that after each reboot, the sensors show up in a different order (= different OID)
So after each reboot of OW server, the HA data would be corrupted unless sensor/OID mapping is updated

Any suggestions how to handle this? It would be nice with a mapping capability in HA so the ID (read from one OID) can be used when storing actual data (read from another OID)

/Peter

2

I have seen some other snmp devices that can reorder oids on rebooting. Some have a setting to persist the values. To me this appears to be a device issue Hass only looks at the oid information that is configured. Correct?

3

Well, depends I guess. I can add/remove 1-wire sensors at any time. Still I would like HA to map a specific 1-wire sensor ID (not OID) with a HA-sensor.
This problem cannot be solved by the device, only by HA.
Perhaps someone has solved this in some clever way?
/Peter

4

Sorry, it is a bit late, but Iā€™d like to point anyone else running into this to the Lock Order function in the OW-SERVER. It will have the OW-SERVER retain the sensor order through a reboot. You can use it by going to System Configuration>Lock Order on the OW-SERVER and clicking the link to set the order.

1 Like