Domoticz

I have a secondary instance of Domoticz running on my home Windows server and have been using OpenHardwareMonitor / LibreHardwareMonitor for a number of years so that I can keep track of load & temperature.

I've noticed that if new items are added to HardwareMonitor it screws up the reporting and readings are offset to a Domoticz device further up or down the list. For example CPUTotal might be 20th on the list within the HardwareMonitor GUI but if the program is restarted for some reason and a new item appears above it, the stats within the GUI remain correct but the Domoticz device for CPUTotal now relates to something else & the actual values might appear under something like CPUCoreMax which was originally 21st on the list within the HardwareMonitor GUI.

I seem to remember seeing something about this in the past but can't find it in the forum now.

Has anyone else experienced this & is there any way around it rather than deleting the hardware, allowing it to recreate all devices with the correct names then replacing the devices in my main Domoticz instance to retain the history?

You are using the motherboard integration for this or something else? https://wiki.domoticz.com/Adding_intern ... ws_systems

That's the one. I see that the WMI IDs changing over time is referenced there but the supposed fix either was never fully implemented / stable or it's broken again.

Here's an example of my issue - left are the correct temperatures including the CPU, right are the post reboot ones with the correct CPU highlighted


I should point out that this is using LibreHardwareMonitor which is a fork or the original OpenHardwareMonitor that is still developed.

Has anyone managed to find a way around this?

Currently I have to delete the hardware item on my secondary Domoticz then manually remap things after any reboot