What you said isn’t entirely correct, @Mohammad.hakim.a . The display_name property of the object is set to be the exact same as the _name input and this is intended to be a human-readable way to identify the object you have made. However, all honeybee objects also have a unique identifier, which follows the object though the simulation engines and is what’s used by the rest of the software to uniquely identify the object.
You raise a good point, which is that, if we are going to expose something on the Grasshopper GUI, it should be the display name instead of the identifier so we may update the behavior in your screenshot soon.
I’ll also offer one other option, which is really only suitable when you are building definitions solely for you own machine (you never intend to share them) or you have some means generating your own IDs that are unique enough to avoid ID conflicts with other users and other machines. You can use the “HB Set Identifier” component to manually override the ID that is assigned to any object:
Set_Unique_ID.gh (9.7 KB)
Just bear in mind that you are playing with fire when you use this component and you really need to be sure that your _id is unique in order to avoid issues ID collisions.