Hi again, seems that this works for temp!! but not for smart sensors. Smartmontools is installed
Open this in your browser:
http://YOUR_PROXMOX_IP:9000/smart
If you don’t see disks there, the issue is NOT the integration.
Then run in Proxmox:
smartctl --scan-open
Ok This is my fault, something changed on HA and now atributes are in a detail section inside the sensor. Sorry about that and thanks for your help!
I’m glad you solved it.
That’s right, what used to be called attributes are now called details.
Explore the sensors, which come loaded with fascinating details. 
Enjoy the integration.
Hello Javi,
Here I go again, I’ve noticed that the integration mixed VM and LXC from different nodes but same ID. As you can see on the screenshot there are 2 buttons for every VM on the same sensor. This screen is from one node that have OMV ID 100 but it shows OPNSENSE that is from another node and ID 100
Hi!
Thanks for the detailed report — this is very helpful.
You are absolutely right: VM/CT IDs are not unique across nodes in Proxmox, and this can cause conflicts if the node is not included in the identifier.
It looks like the integration is currently not fully distinguishing between nodes when generating entities.
I will review this and fix it so that node + VMID are used as unique identifiers.
Thanks for reporting this 
This should now be fixed in the latest release (v3.0.2).
The update improves how VMs and LXC containers are identified across nodes, preventing collisions when the same VMID exists on different nodes.
Please update and let me know if you still see duplicated or mixed entities.
Updated the integration, re-add all nodes again and now all seems ok
Awesome, thanks for confirming!
Really appreciate the report — it helped track down and fix an edge case with multi-node setups.
Let me know if you run into anything else
Version 4 Highlights
New Cluster module with full overview sensors (backup, status, resources, tasks, firewall)
New Mounted Disks module with real mount detection (local + network, CIFS/NFS)
Improved hardware monitoring
- NVMe sensors with real device names and full temperature data
- Unified I/O Wait metric
- Enhanced CPU detection across multiple sensor types
New network sensors (RX/TX aggregated per node)
New backup monitoring sensors (progress, age, health)
Improvements
- Cleaner sensors (removed unused/invalid data like
Noneand unused path) - More reliable parsing across different hardware
- Better error handling and stability
- Simplified configuration options
- Optimized async coordinator and API calls
Result
- More accurate data
- Better Home Assistant UX
- Fully automation-ready sensors
- Improved compatibility across systems
Coming Next
- Improved PBS support (permissions handling and missing sensors)
- Optional enhancements for storage details (advanced metrics & enrichment)
- New derived sensors for smarter monitoring (health, warnings)
- Performance optimizations and further async improvements
- Ongoing compatibility improvements across different hardware and setups
1 Like
Bonjour
Merci pour cette superbe intégration 
Cependant j'ai un petit soucis avec le PBS
les boutons reboot et shutdown ne fonctionnent pas !! Sinon le reste fonctionne très bien
Proxmox Extended Sensors 4.0.0 Released
After a major rewrite and several months of development, Proxmox Extended Sensors 4.0.0 is now officially available.
V4 transforms the integration from a traditional metrics collector into a true infrastructure observability platform for Proxmox VE and PBS inside Home Assistant.
Highlights
- Cluster-wide monitoring
Mounted disks & CIFS/NFS monitoring- Intelligent infrastructure sensors
Advanced hardware & NVMe monitoring- Intelligent node network telemetry
- Fully redesigned async architecture
Improved PBS integration
Better authentication & permission handling
Updated multilingual documentation
One of the biggest additions is the new Proxmox Node sensor, capable of interpreting overall infrastructure health (Excellent, Warning, Critical, etc.) using aggregated infrastructure metrics and advanced node analysis.
V4 also introduces intelligent node RX/TX telemetry calculated directly from VM and CT traffic, something not exposed natively by the Proxmox API.
Important
The pve-sensors-api.py script MUST also be updated to obtain all V4 improvements and parser fixes.
Documentation and installation guides have been fully updated.
GitHub:
Special thanks to @CyberGWJ for hardware testing and parser debugging contributions during the V4 development cycle.
Hi!
I followed your instructions, but the card comes back with "Custom element doesn't exist: proxmox-speedometer.". Did all the clear cash stuff, also in Incognito-mode it gives errors. Must be something simple, but can't find it. Any help is appreciated.
For the speedometer to work correctly, you need to manually install the two custom JS files used by the card.
- Download these two files from:
https://github.com/Javisen/proxmox_panel/tree/main/HA/dashboard
Files:
gauge_mini.jsproxmox_speedometer.js
- Copy them to:
/config/www/proxmox_sensors
- Then in Home Assistant go to:
Settings → Dashboards
Top right 3-dot menu → Resources
- Add both files as resources:
/local/proxmox_sensors/gauge_mini.js
/local/proxmox_sensors/proxmox_speedometer.js
Resource type:
JavaScript Module
- Refresh the browser (sometimes a full browser cache refresh with Ctrl+F5 helps).
After that the speedometer should render correctly.
1 Like
Thanks you so much! That was the missing thing, indeed, adding it so the resources.
1 Like
I'm a complete Proxmox API NOOB, hence my question.
Is there a simple (NOOB friendly) summary of what I need to do to generate the proper authentication info to complete install and setup of this integration?
My Homelab has been Proxmox based for a long time but I've not yet used the Proxmox API for anything and have used only password based access to the Proxmox console (Webpage). Setting up this HACS integration sent me straight into asking for Token IDs and Token Secrets. So I went to the Proxmox API docs to figure out what to do. It looks like I'll need to read through their descriptions of "Ticket Cookies", "API Tokens", "CSRF" and whatnot several times climb the curve and piece together just what this integration needs me to provide.
This Integration sure looks like it will be useful to me. For example, every time a new monthly HA core release occurs I like to do a complete PVE backup of the VM running HA, the PostgreSQL VM storing recorder and LTSS data, as well as the built-in HA-configuration backup. Along with the great dashboard I'm hoping this neat integration will allow me to automate what is now a cumbersome manual process.
No worries 
You do not need to learn the Proxmox API documentation, CSRF, ticket cookies or anything advanced for this integration.
Everything required is already explained step-by-step in the README and documentation, including screenshots and beginner-friendly instructions.
The documentation is currently available in 7 languages to make the setup process as easy as possible and avoid missing any required steps.
You can find it here:
The most important guides are:
02-proxmox-config.md→ how to create the Proxmox user and API Token03-login-pve-pbs.md→ how to connect the integration to Home Assistant
In reality, the setup only requires:
-
creating a Proxmox user
-
creating an API Token
-
copying:
- User
- Token ID
- Token Secret
into the integration setup.
Once configured, the integration can absolutely help automate backup workflows and infrastructure monitoring
This is brilliant. Thanks for creating this. It makes monitoring Proxmox so much easier. 
1 Like
The instructions you pointed me to were excellent. I wish everyone would spell things out so clearly.
I did run into a couple errors however and have not gotten beyond the logon phase. I don't have time to troubleshoot them right now but will be back at it soon. I did want to send a thank you before going dark however.
FYI, the first error was a bit cryptic in that it complained about an "invalid flow". So I tried from the beginning again and now I get a connection error "please check server address". I tried the FDQDN (homeassistant.lan in my case) as well as the IP address.
One difference from your instructions is that I already had a user assigned for HA login so I just added the PVEAdmin permissions to that login (hass@pve). I used that login, token, and secret when attempting logging the integration in. For fun I tried username/passwd but still got the connection error. Normal access to the HA main webpage works so I'm clearly missing something on my end.
One other things is I noticed the visual how-to (very nice to have) was inconsistent with the written instructions. I.e. if following the written instructions the screen shots would be different in places. One thing I noticed was using "root@pve" for the username, which of course you don't recommend:-)
When I'm back I'll open the hood again.