--- title: "Proxmox VE Custom" description: "Proxmox VE Custom is a Marketplace integration for Home Assistant. It has 5.7k installs sharing analytics, works locally and was last updated October 26, 2026." canonical: "https://vulpo.app/integrations/marketplace/dougiteixeira-proxmoxve" url: "https://vulpo.app/integrations/marketplace/dougiteixeira-proxmoxve.md" last-updated: "2026-10-22" version: "1.4" --- # Proxmox VE Custom > Proxmox VE Custom is a Marketplace integration for Home Assistant. It has 5.7k installs sharing analytics, works locally and was last updated October 26, 2026. Proxmox VE Custom is an integration that reads Proxmox VE state into Home Assistant and lets it act on nodes and clusters. It talks to the Proxmox API locally with the given credentials, either a user password or an API token, and installs nothing on the nodes. It covers clusters, nodes, virtual machines, containers and storage, with sensors, binary sensors, buttons and a software update entity for pending package upgrades. Buttons start, stop, reboot, suspend or back up guests, and a backup action exposes vzdump options. Options include automatic tracking of everything the credentials can see, monitoring of physical disk health, failed tasks and a choice between standard and prefixed entity id schemes. It replaces the core Proxmox integration when installed, is added as a custom repository, and is configured in the UI. Automatic summary of the README and code of dougiteixeira/proxmoxve. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) Not in the Marketplace catalog. Add as a custom repository in the Marketplace. ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Add its repository to the Marketplace as a custom repository and install it, then restart Home Assistant and add it under Settings, Devices and services. ### Enter the address - **Host** - **Password or token value** - **Token name** - **Port** - **Realm** - **Username** - **Verify SSL certificate** Also asked when changing the connection. ### Expose - **Nodes** - **Virtual Machines (QEMU)** - **Linux Containers (LXC)** - **Storages** - **Monitor physical disks**: Read the model, size, temperature, wearout and SMART health of each node's physical disks as a device of its own. If you spin disks down, switch this off - the SMART read wakes them on every poll otherwise. - **Track everything automatically**: Track every node, virtual machine, container and storage the credentials can see, and follow the cluster from then on: whatever is added is picked up, whatever is removed is dropped. The selection above is ignored while this is on. Templates are never tracked. - **Entity id scheme**: Standard: Home Assistant's device then name, qemu\_win11\_108\_cpu\_used. Extended: prefix, kind, id, name, item - pve\_qemu\_108\_win11\_cpu\_used - so a search or a recorder filter catches everything by the prefix and a list sorts by id. Applies to entities created from now on; ids that exist keep them. - **Prefix for the extended scheme**: The first part of every entity id under the extended scheme; pve unless you choose otherwise. Not used by the standard scheme. ### Reauthenticate Integration - **Password or token value** - **Username** - **Token name** - **Realm** ### After setup - **Password or token value** - **Token name** - **Realm** - **Username** - **Verify SSL certificate** - **Username**: Leave empty (along with the fields below) to disable the Arm/Disarm HA buttons and the HA managed sensor. - **Token name** - **Password or token value**: Needs Sys.Console (arm/disarm) and Sys.Audit (HA resource list) on '/' — not the scoped permissions recommended for the main integration user. - **Realm** - **Linux Containers (LXC)** - **Nodes** - **Virtual Machines (QEMU)** - **Storages** - **Track everything automatically**: Track every node, virtual machine, container and storage the credentials can see, and follow the cluster from then on: whatever is added is picked up, whatever is removed is dropped. The selection above is ignored while this is on. Templates are never tracked. - **Monitor physical disks**: Read the model, size, temperature, wearout and SMART health of each node's physical disks as a device of its own. If you spin disks down, switch this off - the SMART read wakes them on every poll otherwise. - **Monitor failed tasks**: Track and report failed tasks from the last 24 hours on the selected nodes, as a sensor. Read every five minutes. - **Monitor package updates**: Read the pending package upgrades of each node into an update entity and a count sensor. Needs Sys.Modify on the node; switch this off to run without that privilege - or without the entities. - **Polling interval**: How often nodes, guests, storage and backups are read. 60 seconds unless changed; Proxmox itself refreshes guest figures about every 10 seconds. Certificates, subscriptions and Ceph are read hourly, failed tasks every five minutes, whatever is set here. - **Guest file path to monitor (QEMU, requires guest agent)**: Absolute path of a file inside each tracked QEMU guest to read via the guest agent and expose as a sensor. Leave empty to disable. Requires the QEMU guest agent to be running in the guest. - **Backup storage for the backup buttons**: Where the "Back up now" and "Back up all" buttons write their backups (snapshot mode). The buttons exist only while a storage is picked here and the credentials hold VM.Backup. Storages that accept backups are listed; any other name can be typed in. - **Entity id scheme**: Standard: Home Assistant's device then name, qemu\_win11\_108\_cpu\_used. Extended: prefix, kind, id, name, item - pve\_qemu\_108\_win11\_cpu\_used - so a search or a recorder filter catches everything by the prefix and a list sorts by id. Applies to entities created from now on; ids that exist keep them. - **Prefix for the extended scheme**: The first part of every entity id under the extended scheme; pve unless you choose otherwise. Not used by the standard scheme. Texts from the code of [dougiteixeira/proxmoxve](https://github.com/dougiteixeira/proxmoxve). ## Entities - **Binary sensors**: Status, Backup running, Health, Locked, Guest agent, Updates packages, HA managed, Replication failing, Quorate, CRM master stale, Storage active, Storage enabled, and 2 more - **Buttons**: Start all, Stop all, Shutdown, Reboot, Start, Stop, Unlock, Resume, Suspend, Reset, Wake-on-LAN, Arm HA, and 5 more - **Sensors**: CPU used, CPU used of host, CPU pressure, CPU pressure stalled, IO pressure, IO pressure stalled, Memory pressure, Memory pressure stalled, Memory used on host, IP address, Snapshots, CPUs, and 59 more - **Updates**: Software update ## Actions - **Back up guests**: Starts backup runs (vzdump) for the targeted guests, nodes or cluster - or for the node and guest ids named. One run per node; returns their task ids. Fields: Node, Guests, All, Storage, Mode, Compression, Notes, Skip if running ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. - **Repair notices**: Notices it can show in Settings, Repairs: Guest agent not readable, Guest file not readable ## From the README > 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. From the README of [dougiteixeira/proxmoxve](https://github.com/dougiteixeira/proxmoxve#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Computers and network](https://vulpo.app/integrations/category/computers-and-network.md), NAS and servers - Brand: [Proxmox](https://vulpo.app/integrations/proxmox.md) - Number: 5.7k installs sharing analytics; 985 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Added as a custom repository in the Marketplace - Latest version: 5.3.4, last updated October 26, 2026 - Domain: `proxmoxve` - Source: - Issues: In Vulpo: Button card, Chart card, Apple Watch ## Other ways in for Proxmox | Name | Kind | Installs or stars | Connection | Upkeep | | --- | --- | --- | --- | --- | | [Proxmox VE](https://vulpo.app/integrations/core/proxmoxve.md) | Built-in integration | 9k installs sharing analytics | Works locally | Part of Home Assistant | | [Proxmox Extended Sensors](https://vulpo.app/integrations/marketplace/javisen-proxmox-sensors.md) | Marketplace integration | 680 installs sharing analytics | Works locally | Updated in the last 6 months | | [Proxmox Guest Updates](https://github.com/Niiikoc/ha-pveupdate) | Marketplace integration | 1 installs sharing analytics | Works locally | Updated in the last 6 months | | [Proxmox Cards for Home Assistant](https://github.com/chsegala/proxmox-cards-for-home-assistant) | Dashboard card | 1 GitHub stars | Connection not stated | Updated in the last 6 months | Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/dougiteixeira-proxmoxve --- - HTML version of this page: https://vulpo.app/integrations/marketplace/dougiteixeira-proxmoxve - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml