I'm open to discussion on what the right course of action should be:
Preserve the breaking change and just note it in the changelog
Introduce logic to keep the same sensor IDs (but what to do with new users with systems that eventually see the motherboard hardware split in two, which would experience duplicate sensor IDs or a breaking change in IDs if we only introduced indices if multiple exist).
Introduce a config in OhmGraphite so the user can choose between 1 and 2 (and default to 2)
Option "2" was chosen as it allows us to punt the decision down the road in a "wait and see" scenario.
Another user visible change is that there is a new metric for storage metrics: "Read Activity" which is analogous to the already present Total and Write Activity sensors but for reading.
Add read activity to storage
Add support for MSI MPG X570 GAMING PLUS (MS-7C37)
Add support for ASUS ROG STRIX X670E-F GAMING WIFI
There's a breaking change in LHW with the introduction of the index of superIO identifier:
Before:
After:
I'm open to discussion on what the right course of action should be:
Preserve the breaking change and just note it in the changelogIntroduce a config in OhmGraphite so the user can choose between 1 and 2 (and default to 2)Option "2" was chosen as it allows us to punt the decision down the road in a "wait and see" scenario.
Another user visible change is that there is a new metric for storage metrics: "Read Activity" which is analogous to the already present Total and Write Activity sensors but for reading.