v2.1.1 - Initial HACS Release

[D-N91]

This is the initial HACS release 2. The code remains the same to v2.0.2.

---

This discussion was created from the release v2.1.1 - Initial HACS Release.

[ljhardy]

Hi Thanks for this! A couple of questions on the setup:

1. for cpu_sensor - is that the system monitor load sensor?
2. for ram and disk sensor - is that free or used?

Thanks!

[D-N91]

Hi!

Great questions. The score logic relies on Percentage (%) values where "higher = worse".

CPU: Use the Processor Use sensor (in %), e.g., sensor.processor_use. Do not use the "Load" sensor (which gives 1min/5min/15min averages), as the scale is different.  

RAM & Disk: Use the Used (%) sensors.

RAM: sensor.memory_use_percent

Disk: sensor.disk_use_percent_home (or whichever drive you want to monitor).

If you use "Free" sensors, a healthy system (e.g., 90% free) would be interpreted as "90% full" and destroy your score! 😉

[ljhardy]

Thank you. Is there a way to check the configuration / what sensors I chose? Or do I have to remove the integration and reinstall it?

[D-N91]

currently, you need to remove the integration and reinstall it to change or view the selected sensors. i haven't implemented a "reconfigure" button yet, but it is on the roadmap for the next update!

[ljhardy]

Why would a cpu load of 11% impact the score negatively? ( Unless I have the wrong sensor attached to CPU. :-) )

recommendations: ⚡ Optimization: CPU load is impacting score (11.0%).

[D-N91]

you likely have the correct sensor. haghs uses "heavyweight cpu tiers" where the first minor penalty starts at 11%.
the logic is that a truly idle, lean system should hover under 10%. however, we are aware that for many modern setups, 11-15% is a normal baseline. haghs is just being a very strict judge here to encourage absolute optimization. we are considering relaxing the first threshold to 15% in a future update to avoid "perma-penalties" on modern hardware.