Lock Health Values

Currently, librenms rewrites the values ​​defined in health every time a discovery occurs. For certain devices, health values ​​are set manually and should not be changed, but with each discovery (when a device goes down and then recovers, a discovery is performed again), it overwrites them. For example, we set a high temperature alert, but discovery overwrites them with a lower value, generating false alerts.

It would be interesting to have the option to lock these values, preventing discovery from overwriting them, except in cases where the sensor no longer exists (e.g., a switch that has been replaced with a different model).

We should only overwrite them if the device tells us to and we support detecting them from the device. Do you still want to lock them in that scenario as that seems sub-optimal.

If this is because of the auto-guessed values then they shouldn’t update on each discovery. This PR might help if you want to test it in that case: Use discovered sensor limits on update by eskyuu · Pull Request #18250 · librenms/librenms · GitHub

The problem is that it overwrites the defined values, maybe that’s a problem?

Have you tested that pull request?

I’ll be interested to see if that PR fixes APC humidity resetting to 30% when I manually set it to 20%.