Proxmox VE integration shows no information "about" my VMs/Containers

[bearhntr]

The problem

As per the documentation page, "Proxmox VE is an open-source server virtualization environment. This integration allows you to poll various data from your instance." you used to be able to see Disk Space, CPU, RAM, and other information from PVE. Now all I get is whether the VM is running or stopped. What happened? Where are all the other entities?

I followed the instructions to the letter, created the 'permissions' on the PVE server and then added the lines to the configuration.yaml file and when rebooting I get the Integration showing but there are no entities like I had before for 'monitoring' my VMs and containers.

What version of Home Assistant Core has the issue?

core-2024.12.4

What was the last working version of Home Assistant Core?

core-2024.10.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Proxmox VE

Link to integration documentation on our website

https://www.home-assistant.io/integrations/proxmoxve

Diagnostics information

No response

Example YAML snippet

# Proxmox VE is an open-source server virtualization environment. This integration allows you to poll various data from your instance.

proxmoxve:
  - host: 10.9.28.204
    username: hass@pve
    password: {{ my_password}}
    verify_ssl: false
    realm: pve
    nodes:
      - node: pve-ha
        vms:
          - 100
        containers:
          - 101

### Anything in the logs that might be useful for us?

```txt
There are multiples of these:

Logger: py.warnings
Source: components/proxmoxve/__init__.py:288
First occurred: 18:09:25 (1 occurrences)
Last logged: 18:09:25

/usr/local/lib/python3.13/site-packages/urllib3/connectionpool.py:1064: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.9.28.204'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings warnings.warn(

Additional information

No response

[home-assistant]

Hey there @jhollowe, @Corbeno, mind taking a look at this issue as it has been labeled with an integration (proxmoxve) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of proxmoxve can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign proxmoxve Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

proxmoxve documentation
proxmoxve source
_{^{(message by IssueLinks)}}

[Drakonas]

Wanted to chime in to say I get this exact error and no entities show up. I am using the numerical ID's for the VM's and containers, but I get this error in addition to the one in the OP:

Logger: homeassistant.components.proxmoxve
Source: components/proxmoxve/__init__.py:208
integration: Proxmox VE (documentation, issues)
First occurred: 3:02:16 PM (3 occurrences)
Last logged: 3:02:16 PM

Vm/Container 100 unable to be found in node xenove
Vm/Container 101 unable to be found in node xenove
Vm/Container 104 unable to be found in node xenove

Except the IP, username, and password in the OP, my configuration matches exactly. I have checked all formatting.

proxmoxve:
  - host: 10.0.0.133
    username: homeassistant@pve
    password: { pass }
    verify_ssl: false
    realm: pve
    nodes:
      - node: xenove
        vms:
          - 100
          - 101
          - 104

[hibbeldi]

Exactly the same here...

[oerix]

Any update on this please?

[EduardsSk]

Same here, though I'm running Home Assistant as a container.

[robbiedehand]

i think we can all agree this seems to be deprecatd, as it is an legacy integration.

[Drakonas]

i think we can all agree this seems to be deprecatd, as it is an legacy integration.

If it were deprecated, it wouldn't have code modifications within the last year, if not the last few months.

Legacy doesn't imply deprecated. It just means nobody has taken the time to migrate the code to modern design standards yet. Home Assistant still supports legacy integrations and the documentation doesn't state them as deprecated, only that it's "recommended" someone migrate to the new UI.

But you need someone willing to do that.

The fact that there's nobody trying to brainstorm or study why this integration isn't working for us is a different issue.

There's enough people with the same issue to warrant an investigation, especially when it's worked for a while seemingly, but something recently may have broke.

I'd hope the recent edits are trying to investigate or update things to fix this, but I'm not sure.

[007trains]

This fork by dougiteixeira
https://github.com/dougiteixeira/proxmoxve
Is in my opinion what the modern integration should be like, GUI config, working stats and under active development

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Drakonas]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

If you read the post, you will notice the reason it doesn't work is the integration is still legacy and hasn't been updated to the new workflow standard. It needs to be updated.

The only commit it's had over a year is just some "pre-work" for migrating to the new workflow, but it still hasn't been updated.

It still doesn't work.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.