As an aside, due to how the kernel guys have designed /sys, I was actually able to follow block devices back through their paths in /sys to arrive at the right hwmon directory for that device, which is how inxi now defaults to getting nvme and drive temps. Not all hdd have this data available, for those you still have to use hddtemp, but those are also being mapped more and more internally to the hwmon directories I believe, which is why inxi can now increasingly show drive/nvme temps without root or hddtemp.
inxi was not however able to reverse that detection and start with sensors output and arrive at the right drive, I could find no way to match that data to a specific drive/block device.
I may in the future try creating a /sys direct based sensors output option, I half started that, but stopped because honestly, the sensors guys have already done it for me, so there is little to be gained by having inxi recreate the data that is already in sensors output going straight to /sys for it.
inxi was not however able to reverse that detection and start with sensors output and arrive at the right drive, I could find no way to match that data to a specific drive/block device.
I may in the future try creating a /sys direct based sensors output option, I half started that, but stopped because honestly, the sensors guys have already done it for me, so there is little to be gained by having inxi recreate the data that is already in sensors output going straight to /sys for it.