+1
Daily
997
stars
82
forks
5
watchers
435
prs
188
issues
51
releases
README
Proxmox VE Custom Integration for Home Assistant Proxmox VE is an open-source server virtualization environment. This integration reads its state into Home Assistant and lets you act on it — for a single node as much as for a cluster. It began as @dougiteixeira's custom integration, built on the Home Assistant core integration and grown well beyond it; it replaces the core one when installed (what differs). Everything goes through the Proxmox API with the credentials you give it — nothing is installed on the nodes, except PVE-mods if you want hardware temperatures. What you get - Cluster — nodes online, guests running, CPU and memory across the cluster; HA status, backup coverage and Ceph health with the optional cluster credentials; shared storage as one device. - Nodes — status, CPU, memory, swap, disk, IO delay, load average, version; package updates as a Home Assistant update entity; last backup and failed tasks; replication, subscription and certificate expiry; hardware temperatures, fans and voltages via PVE-mods; physical disks with SMART; ZFS pools. - Virtual machines and containers — status with QEMU's finer run states, CPU (own and as a share of the host), memory, disk from the guest agent, network, uptime, a file read from inside the guest. - Storage — capacity and the active/enabled/shared flags, per node for local storage and once for shared. - Actions — start, stop, shutdown, reboot, suspend, resume, hibernate, reset, unlock, snapshot and backup buttons; bulk start/stop/suspend/backup per node; Wake on LAN; arm/disarm HA; and a proxmoxve.backup action with all of vzdump's options. - Behaviour — optional automatic discovery of everything the credentials can see, failover to another cluster node when the configured one goes down, no re-authentication after a node was off overnight, repairs that name the missing privilege, and buttons only where the privilege exists. Many entities are created disabled by default — the buttons that change things, and sensors most setups never need — and are enabled per entity, see Disabled entities. Documentation - Entities — every sensor, by cluster, node, guest and storage - Actions — buttons and the proxmoxve.backup action - Hardware sensors and physical disks — PVE-mods, SMART, when readings come and go - Proxmox permissions — roles, group, user and token, step by step - How it behaves — discovery, failover, nodes that are off, disabled entities, what I cannot test - Troubleshooting — debug logging, diagnostics, screenshots - Compared with the core integration — what the extra install gets you, feature by feature - Blueprints — a scheduled backup as a ready-made automation - Contributing Install Installation via HACS Have HACS installed, this will allow you to update easily. Adding Proxmox VE to HACS can be using this button: If the button above doesn't work, add https://github.com/dougiteixeira/proxmoxve as a custom repository of type Integration in HACS. Click Install
Top issues
#595Entities of newly added node becoming unavailable13 comments · 2025-12-06#711Software update entity shows "up to date" when pending updates don't include pve-manager4 comments · 2026-10-08#692Cluster fallback not working when primary node is down during HA startup4 comments · 2026-09-22#706hardware sensor data missing (pve-mod renamed)1 comments · 2026-10-01#702sensor.node_proxmox_total_updates listing packages by description1 comments · 2026-09-29#616Cannot be used with your own domain (proxmox. ... .de)1 comments · 2026-02-12#613Integration blocks Home Assistant shutdown (SyncWorker hang in poll_api)1 comments · 2026-02-08#723Intermittent RemoteDisconnected during polling near pveproxy's five-second keep-alive expiry (5.3.4)0 comments · 2026-11-04
Discussions
#722Separating the Custom Integration from the Offlicial Integration0 comments · 2026-11-04#703sensor uptime1 comments · 2026-09-30#694list of security-only updates1 comments · 2026-09-23#685Add sensors to detect memory pressure for VMs / LXCs2 comments · 2026-09-18#671Failed Task Monitoring1 comments · 2026-08-21#645Real Update entity for available updates3 comments · 2026-04-02#622Join forces with official integration?3 comments · 2026-03-05#611Disk type1 comments · 2026-01-27
Latest release
5.3.4 5.3.4 2026-10-12Fixed - A node that cannot be read no longer takes every other entity with it. The device description read a processor name that had never been assigned, and the resulting error failed the setup of the sensor and binary sensor platforms — so one unreadable node cost the entry all of its entities, the cluster's included. Thank you, @bilogic, for the log that showed it (712). - Saving Add or remove Nodes, VMs, Containers or Storages no longer deletes the node's disk and pool devices. The switch for physical disks moved to the Advanced configuration page in 5.2.0, and the selection step kept rea