Naming convention when creating sensors...please!

[FabienD74]

Hi,
I just installed this.in my DEV environemnt... and i'm impressed by the quantity of info returned ..... BUT:
It is creating A LOT, in my case 40 services and 681 entities.....
and surprise surprise, sensors created don't start with a "keyword" ,

So sensors looks like :
sensor.lxc_ct_docmost_109_cpu_used
sensor.node_proxmox1_containers_running
sensor.zfs_proxmox1_zfs_pool_raid_data1_free_percentage

How can i easily filter include/exclude in the "recoder" => nearly impossible
How can i search something ??? =>hard.

could you add something like "pve_" as a prefix to the technical name when creating the sensor.
That would make life way easier ...
In fact the DOMAIN should be added when creating the unique_id.

ps: In the current state, i won't install it it in my production system. Too messy.
ps2: hopefully, we can identify sensors using {{ integration_entities('proxmoxve') }} :-)

Thx.

[mZ738]

5.2.0 adds an entity id scheme choice at setup: Standard is Home Assistant's device-then-name as before; Extended puts a common prefix first and the id before the name — sensor.pve_qemu_108_win11_cpu_used, sensor.pve_node_pve_cpu_used — so a search or recorder filter catches everything by the prefix and a list sorts by id. The prefix is pve unless you type another. Entities that exist keep their ids — the scheme applies to entities registered from then on, and there is deliberately no bulk rename. https://github.com/dougiteixeira/proxmoxve/releases/tag/5.2.0

[FabienD74]

NICE, but unfortunately i'm not using proxmoxveanymore.
I have found a better solution to all my needs.
I'm using a tool called pulse ( https://github.com/rcourtman/Pulse ) to fetch docker/proxmox/PBS information.
Then I created a tool in bash to:

• use API to retreive the information i need from Pulse (cpu,disk,storage,... )
• fill MQTT the right way.
  => automatic discovery of entiities via MQTT, noting to do in Home Assistant, FULL automatic.