{"full_name":"dougiteixeira/proxmoxve","owner":"dougiteixeira","name":"proxmoxve","shard":"1","url":"https://github.com/dougiteixeira/proxmoxve","description":"Proxmox VE Custom Integration Home Assistant","homepage":null,"topics":[],"tag_pages":[],"language":"Python","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/31328123?u=5e1002e33789e27d4442f536c1992e1525bf3fef&v=4","created_at":"2022-07-15T01:28:46Z","pushed_at":"2026-11-16T00:34:05Z","metrics":{"stars":997,"forks":82,"watchers":5,"issues":188,"prs":435,"releases":51,"issues_open":8,"issues_closed":180,"prs_open":0,"prs_closed":105,"prs_merged":330,"discussions":101},"growth":{"day":{"stars":1,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[994,995,995,995,996,996,997],"forks":[82,82,82,82,82,82,82],"watchers":[null,5,5,5,5,5,5],"issues_open":[null,8,8,8,8,8,8],"prs_open":[null,0,0,0,0,0,0]},"boards":{},"same_owner":[],"issues":[{"number":595,"title":"Entities of newly added node becoming unavailable","comments":13,"created_at":"2025-12-06T11:22:31Z"},{"number":711,"title":"Software update entity shows \"up to date\" when pending updates don't include pve-manager","comments":4,"created_at":"2026-10-08T23:33:49Z"},{"number":692,"title":"Cluster fallback not working when primary node is down during HA startup","comments":4,"created_at":"2026-09-22T16:49:07Z"},{"number":706,"title":"hardware sensor data missing (pve-mod renamed)","comments":1,"created_at":"2026-10-01T17:27:05Z"},{"number":702,"title":"sensor.node_proxmox_total_updates listing packages by description","comments":1,"created_at":"2026-09-29T13:35:29Z"},{"number":616,"title":"Cannot be used with your own domain (proxmox. ... .de)","comments":1,"created_at":"2026-02-12T12:52:08Z"},{"number":613,"title":"Integration blocks Home Assistant shutdown (SyncWorker hang in poll_api)","comments":1,"created_at":"2026-02-08T23:18:22Z"},{"number":723,"title":"Intermittent RemoteDisconnected during polling near pveproxy's five-second keep-alive expiry (5.3.4)","comments":0,"created_at":"2026-11-04T20:24:51Z"}],"discussions":[{"number":722,"title":"Separating the Custom Integration from the Offlicial Integration","comments":0,"category":"Feature request","created_at":"2026-11-04T09:19:50Z"},{"number":703,"title":"sensor uptime","comments":1,"category":"Feature request","created_at":"2026-09-30T12:01:55Z"},{"number":694,"title":"list of security-only updates","comments":1,"category":"Feature request","created_at":"2026-09-23T16:56:00Z"},{"number":685,"title":"Add sensors to detect memory pressure for VMs / LXCs","comments":2,"category":"Feature request","created_at":"2026-09-18T12:29:43Z"},{"number":671,"title":"Failed Task Monitoring","comments":1,"category":"Feature request","created_at":"2026-08-21T11:39:54Z"},{"number":645,"title":"Real Update entity for available updates","comments":3,"category":"Feature request","created_at":"2026-04-02T15:29:44Z"},{"number":622,"title":"Join forces with official integration?","comments":3,"category":"Ideas","created_at":"2026-03-05T16:36:43Z"},{"number":611,"title":"Disk type","comments":1,"category":"Feature request","created_at":"2026-01-27T09:02:21Z"}],"latest_release":{"name":"5.3.4","tag":"5.3.4","published_at":"2026-10-12T11:26:22Z","body":"## Fixed\n\n- 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](https://github.com/dougiteixeira/proxmoxve/issues/712)).\n- 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 reading it from its own form — so every save looked like \"disks turned off\". Home Assistant restores the device, which is why this looked harmless, but the entities come back as new: with *Enable newly added entities* off they come back disabled and disk health stops reporting without an error. Thank you, @ItsColby, for a report that named the commit ([#713](https://github.com/dougiteixeira/proxmoxve/issues/713)).\n- The `Software update` entity no longer says \"up to date\" while packages are pending. The version it reports carries the pending counts as `-p7-d2`, which Home Assistant's version comparison reads as a pre-release — ranking it below the installed version, so with no `pve-manager` among the pending packages the entity compared itself into silence. Thank you, @DrNiKa, for working the mechanism out ([#711](https://github.com/dougiteixeira/proxmoxve/issues/711)).\n- The hardware sensors are found again under PVE-mods v2. It renamed the field twice — `PveMod_JsonSensorInfo`, `PveMods_JsonSensorInfo`, `PveMods_SensorInfo` — and v2.1.0 also changed the shape: the chips moved to `enhanced_sensors`, keyed by the raw sensor id, and a reading became an object instead of a flat number. All three are read, and the label still names the entity, so upgrading PVE-mods neither renames the sensors nor loses their history. Thank you, @atfua, for finding the rename ([#706](https://github.com/dougiteixeira/proxmoxve/issues/706)).\n- The QEMU guest agent is only asked while it can answer. Proxmox answers every `agent/*` read with a 500 while the agent is not enabled or the VM is not running, and the `agent` flag in the status read is the VM's configuration — set on a stopped VM too, which cost some 2,900 failed requests a day for a single stopped VM. Thank you, @BadFlo, for the fix and the measurements ([#708](https://github.com/dougiteixeira/proxmoxve/pull/708)).\n","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}