SensorPanel Manager: Smart Sensor Replacement (NEW Feature)!!

[Surjeet]

Hi AIDA Team,

AIDA64 does an excellent job of intelligently detecting available system sensors and grouping them into categories such as Temperature, Cooling Fans, and Voltage etc.:

Building on this smart sensor grouping, I’d like to suggest a new feature for the SensorPanel Manager - a streamlined “Replace Sensor” option.

This new feature in SensorPanel Manager where one can easily replace sensor items (if required and also helps when certain sensors do not show values and show N/A😞

Current Method:
To replace a sensor (e.g., replacing a CPU Temperature sensor with a GPU or motherboard sensor), we have to:

• Select the sensor item
• Click “Modify”
• Manually browse and choose a replacement from the full list

Proposed Feature:
A new, more intuitive “Replace” function could work like this:

• Right-click on a sensor item in the SensorPanel
• A “Replace” option appears in the context menu
• Selecting “Replace” shows a refined list of compatible sensor options
• The list is filtered intelligently based on the current sensor category

For example, if I’m replacing a CPU Temperature sensor, only Temperature sensors are shown. (if not possible, complete list populates)

This would make the process faster, more user-friendly, and visually more appealing - leveraging AIDA’s existing smart grouping capabilities.

@Fiery @BHSY @COSTAJUNIOR @JariKoi @Loyd : What you guys think and vote for this new approach?

Looking forward to your thoughts!

[JariKoi]

7 hours ago, Surjeet said:

Hi AIDA Team,

AIDA64 does an excellent job of intelligently detecting available system sensors and grouping them into categories such as Temperature, Cooling Fans, and Voltage etc.:

Building on this smart sensor grouping, I’d like to suggest a new feature for the SensorPanel Manager - a streamlined “Replace Sensor” option.

This new feature in SensorPanel Manager where one can easily replace sensor items (if required and also helps when certain sensors do not show values and show N/A😞

Current Method:
To replace a sensor (e.g., replacing a CPU Temperature sensor with a GPU or motherboard sensor), we have to:

• Select the sensor item
• Click “Modify”
• Manually browse and choose a replacement from the full list

Proposed Feature:
A new, more intuitive “Replace” function could work like this:

• Right-click on a sensor item in the SensorPanel
• A “Replace” option appears in the context menu
• Selecting “Replace” shows a refined list of compatible sensor options
• The list is filtered intelligently based on the current sensor category

For example, if I’m replacing a CPU Temperature sensor, only Temperature sensors are shown. (if not possible, complete list populates)

This would make the process faster, more user-friendly, and visually more appealing - leveraging AIDA’s existing smart grouping capabilities.

@Fiery @BHSY @COSTAJUNIOR @JariKoi @Loyd : What you guys think and vote for this new approach?

Looking forward to your thoughts!

This is a very good suggestion and would definitely help if any sensor doesn't work. Additionally, if you have created a 100 state sensor, you wouldn't always have to reset the sensor readings, but they would remain as they were created. I support this if it is possible to create. However, nowadays I make such sensors less frequently because they strain the panel and it can freeze or operate sluggishly. Or if you add more large graph sensors, panel starts to lag. I personally prefer lighter panels. But I do support this reform.👍🏻

[Loyd]

sounds great

 

[BHSY]

15 hours ago, Surjeet said:

Hi AIDA Team,

AIDA64 does an excellent job of intelligently detecting available system sensors and grouping them into categories such as Temperature, Cooling Fans, and Voltage etc.:

Building on this smart sensor grouping, I’d like to suggest a new feature for the SensorPanel Manager - a streamlined “Replace Sensor” option.

This new feature in SensorPanel Manager where one can easily replace sensor items (if required and also helps when certain sensors do not show values and show N/A😞

Current Method:
To replace a sensor (e.g., replacing a CPU Temperature sensor with a GPU or motherboard sensor), we have to:

• Select the sensor item
• Click “Modify”
• Manually browse and choose a replacement from the full list

Proposed Feature:
A new, more intuitive “Replace” function could work like this:

• Right-click on a sensor item in the SensorPanel
• A “Replace” option appears in the context menu
• Selecting “Replace” shows a refined list of compatible sensor options
• The list is filtered intelligently based on the current sensor category

For example, if I’m replacing a CPU Temperature sensor, only Temperature sensors are shown. (if not possible, complete list populates)

This would make the process faster, more user-friendly, and visually more appealing - leveraging AIDA’s existing smart grouping capabilities.

@Fiery @BHSY @COSTAJUNIOR @JariKoi @Loyd : What you guys think and vote for this new approach?

Looking forward to your thoughts!

I like this idea. The 100 states (a total of 8 sensors) contain different min/max values. If the value can be retained without reverting to its default value when selecting a different sensor, for example, changing CPU temp to GPU temp, I would like this feature implemented. If not, there is no point in using the REPLACE shortcut. The REPLACED shortcut would be useful for other sensors that don't require the 100 states sensor.

 

[Surjeet]

Thank you @JariKoi, @Loyd and @BHSY Really appreciate your thoughts!!

Lets ask Fiery if this request is possible as this will be another Game Changer if added!

@Fiery, please let us know if this request makes any sense and is possible to be implemented! Look forward to your continued patronage as always!!

[Fiery]

5 hours ago, Surjeet said:

Thank you @JariKoi, @Loyd and @BHSY Really appreciate your thoughts!!

Lets ask Fiery if this request is possible as this will be another Game Changer if added!

@Fiery, please let us know if this request makes any sense and is possible to be implemented! Look forward to your continued patronage as always!!

@JariKoi @Loyd @BHSY

At first my thought was: "Hey, we already do this but you guys never noticed!" Because when you import a SensorPanel layout, AIDA64 does the smart replacement automatically, by using fuzzy logic to pick a sensor similar to one that is missing on the current system.

But then I realized you want this for a manual process and it would also become useful in other scenarios too.  So we will do it.

[Fiery]

Do you guys prefer to have the label updated to the label of the new source, or keep everything intact?  An example: if you have a CPU temperature sensor item placed on your layout, and its label is "CPU", and you select CPU Package as the new source, should the label be automatically updated to "CPU Package" or left unchanged?

[Surjeet]

44 minutes ago, Fiery said:

Do you guys prefer to have the label updated to the label of the new source, or keep everything intact?  An example: if you have a CPU temperature sensor item placed on your layout, and its label is "CPU", and you select CPU Package as the new source, should the label be automatically updated to "CPU Package" or left unchanged?

 

   😍 First of all, Heartiest Thank you for checking and working on this new feature request 😍

 

Behaviour may vary depending on the user’s specific use case.

However, if labels could automatically update (when used) while maintaining the same font style, that would be a fantastic improvement - both visually appealing and time-saving!

We all are curious and excited to know regarding this:

One of the most important aspects for users is whether the Minimum and Maximum values remain unchanged when a sensor item is replaced.

For example, in a setup using 100 states (with 8 sensors), each sensor typically has unique Min/Max values. If these values persist and remain intact after replacing a sensor, it would be a huge benefit - eliminating the need to manually re-enter values. This makes the system far more user-friendly, especially for users who might not be familiar with the exact Min/Max configurations.

[COSTAJUNIOR]

58 minutes ago, Surjeet said:

 

   😍 First of all, Heartiest Thank you for checking and working on this new feature request 😍

 

Behaviour may vary depending on the user’s specific use case.

However, if labels could automatically update (when used) while maintaining the same font style, that would be a fantastic improvement - both visually appealing and time-saving!

We all are curious and excited to know regarding this:

One of the most important aspects for users is whether the Minimum and Maximum values remain unchanged when a sensor item is replaced.

For example, in a setup using 100 states (with 8 sensors), each sensor typically has unique Min/Max values. If these values persist and remain intact after replacing a sensor, it would be a huge benefit - eliminating the need to manually re-enter values. This makes the system far more user-friendly, especially for users who might not be familiar with the exact Min/Max configurations.

Absolutely, I’m fully on board!

For setups using 100 states across 8 sensors, this would definitely make a huge difference.

Keeping the minimum and maximum values preserved when switching sensors isn’t just convenient — it’s essential for anyone managing complex layouts. It saves time, reduces errors, and makes the whole process much smoother. 👊

[BHSY]

14 hours ago, Fiery said:

Do you guys prefer to have the label updated to the label of the new source, or keep everything intact?  An example: if you have a CPU temperature sensor item placed on your layout, and its label is "CPU", and you select CPU Package as the new source, should the label be automatically updated to "CPU Package" or left unchanged?

Thank you for working on this new feature😉

As Surjeet mentioned, it all depends on the user’s specific use case. If a user chose to show the label on their layout, it would be convenient and time-saving for them if the label could be changed accordingly when selecting a different sensor. Still, a user might use a different label, for example, he chooses to use 'Utilization' instead of 'CPU Utilization'. So, not just to retain the min/max value, the label should be retained as well, if can. For me, I don't usually use the label so if I replaced a different sensor, the label shouldn't appear on my layout.

The most important part is that the min/max values are preserved when replaced with a new sensor, especially for usage and temperature. I also use a different value for a 15 state (a single custom gauge sensor). For example, the CPU temperature minimum value is 80 and the maximum is 100. This is to alert the user if the CPU temperature reaches around 80 degrees, a bright red LED image will appear on the panel.

Edited Tuesday at 09:51 AM by BHSY

[Fiery]

14 hours ago, Surjeet said:

 

   😍 First of all, Heartiest Thank you for checking and working on this new feature request 😍

 

Behaviour may vary depending on the user’s specific use case.

However, if labels could automatically update (when used) while maintaining the same font style, that would be a fantastic improvement - both visually appealing and time-saving!

We all are curious and excited to know regarding this:

One of the most important aspects for users is whether the Minimum and Maximum values remain unchanged when a sensor item is replaced.

For example, in a setup using 100 states (with 8 sensors), each sensor typically has unique Min/Max values. If these values persist and remain intact after replacing a sensor, it would be a huge benefit - eliminating the need to manually re-enter values. This makes the system far more user-friendly, especially for users who might not be familiar with the exact Min/Max configurations.

@BHSY @COSTAJUNIOR

Okay, so only the sensor item source will be updated with the one you select from the list of similar type sensor items.  The label and every other aspect of the sensor item will be left intact.  It's coming with the next beta update

[BHSY]

21 minutes ago, Fiery said:

@BHSY @COSTAJUNIOR

Okay, so only the sensor item source will be updated with the one you select from the list of similar type sensor items.  The label and every other aspect of the sensor item will be left intact.  It's coming with the next beta update

Cool. Looking forward to it. Thank you🙏.

[Surjeet]

1 hour ago, Fiery said:

@BHSY @COSTAJUNIOR

Okay, so only the sensor item source will be updated with the one you select from the list of similar type sensor items.  The label and every other aspect of the sensor item will be left intact.  It's coming with the next beta update

Once again, the legendary Fiery delivers! 🙌
Your dedication never fails to amaze - thank you for turning ideas into reality. Truly grateful. 😍🙏

[COSTAJUNIOR]

4 hours ago, Fiery said:

@BHSY @COSTAJUNIOR

Okay, so only the sensor item source will be updated with the one you select from the list of similar type sensor items.  The label and every other aspect of the sensor item will be left intact.  It's coming with the next beta update

Thanks a ton for always responding so quickly and bringing these awesome improvements to the community. Can’t wait to try out the next beta!
Now all that’s left is that legendary update everyone’s dreaming of: the glorious animated GIF! 😂🔥

[Fiery]

3 hours ago, COSTAJUNIOR said:

Thanks a ton for always responding so quickly and bringing these awesome improvements to the community. Can’t wait to try out the next beta!
Now all that’s left is that legendary update everyone’s dreaming of: the glorious animated GIF! 😂🔥

🤣  We have other goodies to deliver too, like the new colour picker panel and the SensorPanel Manager grouping.

Thank you for your kind words!

[Fiery]

@BHSY @COSTAJUNIOR @Surjeet @Loyd @JariKoi

We've implemented the new Change Source item in the right-click context menu of the SensorPanel Manager in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how you like it.

[Surjeet]

1 hour ago, Fiery said:

@BHSY @COSTAJUNIOR @Surjeet @Loyd @JariKoi

We've implemented the new Change Source item in the right-click context menu of the SensorPanel Manager in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how you like it.

  ❤️ ❤️ Truly Grateful  😍🙏 - Incredible Work 🔥🔥🔥🔥 

 

Thank you so much for the incredibly FAST turnaround - this truly exceeded my EXPECTATIONS, and its IMPRESSIVE!

Everything is working exactly as we discussed and agreed upon, and it looks absolutely AWESOME. Your attention to detail shines through 🙏

There’s just one minor thing I noticed:

- For the first sensor in the image below, I swapped GPU Power with CPU Package
- The replacement went flawlessly: the sensor updated correctly, min/max values stayed intact, and even the icon changed beautifully from GPU to CPU - just as expected
- The only thing that didn’t update was the name - it still shows as “GPU” instead of reflecting the new sensor name “CPU Package”

I hope we did not consider this name as a "Label" and I hope this is not at my end only!!

Once again, thank you so much for this feature and it is incredible!!

[BHSY]

On 6/11/2025 at 5:32 PM, Fiery said:

@BHSY @COSTAJUNIOR @Surjeet @Loyd @JariKoi

We've implemented the new Change Source item in the right-click context menu of the SensorPanel Manager in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how you like it.

Thank you so much for implementing the 'Change Souce'.🩷

Everythings works as we hope, especially the min/max values were retained as it was. However, the sensor description did not change.

Please refer to the IMAGE 1 below, I have duplicated all the CPU sensors and change them to GPU sensors. However, the description still shows as CPU. It should changed accordingly to the 'Item type' in the Modify Item. 

Add: Is it possbile to select all the same 8 custom sensor gauges and change them all at once, instead of one at a time?

 

As for the IMAGE 2, the item type is a 'Simple sensor item'. I duplicated the CPU Utilization and change it to GPU Utilization but the description still showed as CPU Utilization. The only way for me to change the description is to enable the 'Show label' and type in GPU Utilization. Also, I think it is better for the 'Show Label' to changed too when we change to a different sensor, regardless if the 'Show Label' was enable or disable?

Thank you!

 

[JariKoi]

4 minutes ago, BHSY said:

Thank you so much for implementing the 'Change Souce'.🩷

Everythings works as we hope, expecially the min/max values were retained as it was. However, the sensor description did not change.

Please refer to the IMAGE 1 below, I have duplicated all the CPU sensors and change them to GPU sensors. However, the description still shows as CPU. It should changed accordingly to the 'Item type' in the Modify Item. 

Add: Is it possbile to select all the same 8 custom sensor gauges and change them all at once, instead of one at a time?

 

As for the IMAGE 2, the item type is a 'Simple sensor item'. I duplicated the CPU Utilization and change it to GPU Utilization but the description still showed as CPU Utilization. The only way for me to change the description is to enable the 'Show label' and type in GPU Utilization. Also, I think it is better for the 'Show Label' to changed too when we change to a different sensor, regardless if the 'Show Label' was enable or disable?

Thank you!

 

Absolutely, just like that. I agree with BHSY.✅🙇‍♂️🥷

[COSTAJUNIOR]

4 hours ago, Fiery said:

@BHSY @COSTAJUNIOR @Surjeet @Loyd @JariKoi

We've implemented the new Change Source item in the right-click context menu of the SensorPanel Manager in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how you like it.

Thank you again for the update. However, in my case, it had no practical effect, even after applying it. When I replace a sensor — for example, switching the CPU temperature sensor to the GPU — the minimum and maximum values are not preserved. I'm specifically referring to the use of sensors with 100 states distributed across 8 custom sensors.

I would also like to suggest adding the option to select all 8 custom sensors at once and change them simultaneously, instead of having to modify each one individually.

[Fiery]

On 6/11/2025 at 12:57 PM, Surjeet said:

  ❤️ ❤️ Truly Grateful  😍🙏 - Incredible Work 🔥🔥🔥🔥 

 

Thank you so much for the incredibly FAST turnaround - this truly exceeded my EXPECTATIONS, and its IMPRESSIVE!

Everything is working exactly as we discussed and agreed upon, and it looks absolutely AWESOME. Your attention to detail shines through 🙏

There’s just one minor thing I noticed:

- For the first sensor in the image below, I swapped GPU Power with CPU Package
- The replacement went flawlessly: the sensor updated correctly, min/max values stayed intact, and even the icon changed beautifully from GPU to CPU - just as expected
- The only thing that didn’t update was the name - it still shows as “GPU” instead of reflecting the new sensor name “CPU Package”

I hope we did not consider this name as a "Label" and I hope this is not at my end only!!

Once again, thank you so much for this feature and it is incredible!!

Label is the default name for a sensor item.  E.g. "CPU Package" is the label for ... well... CPU Package temperature  When you change the source, the label is not updated right now.  When you have the label overridden and shown on your layout, updating the label automatically may be something you'd prefer not to happen.  When the label is now shown on the layout, then I suppose updating it would be best since then in the list of items (in the SensorPanel Manager) you'd better understand and follow the source changes you may apply.

[Fiery]

On 6/11/2025 at 2:16 PM, BHSY said:

Thank you so much for implementing the 'Change Souce'.🩷

Everythings works as we hope, expecially the min/max values were retained as it was. However, the sensor description did not change.

Please refer to the IMAGE 1 below, I have duplicated all the CPU sensors and change them to GPU sensors. However, the description still shows as CPU. It should changed accordingly to the 'Item type' in the Modify Item. 

Add: Is it possbile to select all the same 8 custom sensor gauges and change them all at once, instead of one at a time?

As for the IMAGE 2, the item type is a 'Simple sensor item'. I duplicated the CPU Utilization and change it to GPU Utilization but the description still showed as CPU Utilization. The only way for me to change the description is to enable the 'Show label' and type in GPU Utilization. Also, I think it is better for the 'Show Label' to changed too when we change to a different sensor, regardless if the 'Show Label' was enable or disable?

Thank you!

1) We'll implement changing source for multiple selected items in the next AIDA64 beta update.

2) As for the label update issue, we wanted to tread lightly and avoid updating it automatically because we got from the discussion above that it's not something you'd prefer to have.  However, there may be multiple use cases: maybe the label shouldn't be updated only when it's shown on the layout?  So when you don't have the label enabled (for Sensor Items and Simple Sensor Items) and when the label is not a visual part of the item (for Gauges and Graphs) we can freely update it automatically, can't we?

[Fiery]

On 6/11/2025 at 4:27 PM, COSTAJUNIOR said:

Thank you again for the update. However, in my case, it had no practical effect, even after applying it. When I replace a sensor — for example, switching the CPU temperature sensor to the GPU — the minimum and maximum values are not preserved. I'm specifically referring to the use of sensors with 100 states distributed across 8 custom sensors.

It's strange, it works for others.  And we've checked, and the minium/maximum values aren't altered at all.

[BHSY]

5 hours ago, Fiery said:

1) We'll implement changing source for multiple selected items in the next AIDA64 beta update.

Thank you.

5 hours ago, Fiery said:

2) As for the label update issue, we wanted to tread lightly and avoid updating it automatically because we got from the discussion above that it's not something you'd prefer to have.  However, there may be multiple use cases: maybe the label shouldn't be updated only when it's shown on the layout?  So when you don't have the label enabled (for Sensor Items and Simple Sensor Items) and when the label is not a visual part of the item (for Gauges and Graphs) we can freely update it automatically, can't we?

I see, I get what you mean and you are right. No need to make any changes to the Simple sensor item' label.

Edited 18 hours ago by BHSY

[BHSY]

6 hours ago, Fiery said:

Label is the default name for a sensor item.  E.g. "CPU Package" is the label for ... well... CPU Package temperature  When you change the source, the label is not updated right now.  When you have the label overridden and shown on your layout, updating the label automatically may be something you'd prefer not to happen.  When the label is now shown on the layout, then I suppose updating it would be best since then in the list of items (in the SensorPanel Manager) you'd better understand and follow the source changes you may apply.

Correct me if I'm wrong but I think the label you mention to Surjeet refers to the 'Simple sensor item', am I right?

What about the gauge/custom gauge? Can the gauge/custom gauge description be changed automatically on the SensorPanel Manager?  For example, after I duplicate the CPU temperature gauge and change it to GPU temperature gauge using the 'Change Source', only the icon has changed but the description still shows as CPU Utilization (Please take a look at the attached image). The only way to change it is to go back to the Modify window but that defeats the purpose of using the 'Change Source'.

Edited 18 hours ago by BHSY
Added a screenshot