newly added VMs don't show up in HA

Jarod2801 commented 1 year ago

Checklist

[X] I have updated to the latest available Proxmox VE Custom Integration version.

Describe the issue you are experiencing

I am running 3 Proxmox Servers (8.0.4) with in total 7 VMs spread over the Proxmox servers.

The integration works fine so far. All nodes and VMs including all entities are discovered. Today I created a new VM on one PVE host, but the VM doesn't show up in HA.

I already reloaded the entries of the 3 PVE hosts and also restarted the whole HA.

But issue still exists.

Anyone experiencing the same behaviour?

In which version of Home Assistant Core do you have the problem?

2023.11.1

What version of Proxmox VE Custom Integration has the issue?

2.0.4

What version of Proxmox VE do you have the problem?

8.0.4

Additional information

No response

dougiteixeira commented 1 year ago

Can you provide the debug logs? Include this in your config file:

logger:
  default: warning
  logs:
    custom_components.proxmoxve: debug
    proxmoxer: debug

This could be a user permissions issue, so please confirm that the user used in the integration has access to this new VM.

Jarod2801 commented 1 year ago

Added the logger to the conf. Where can I see them?

Permission on the Proxmox-Host is fine, as I created the user and group as described in here. And the 2 other VMs are monitored fine.

EDIT: I found it in the logs, but don't know how to copy the lines. I am using the SSH Addon. Ctrl +C doesn't work. Also right-click "copy line" doens't work.

This is the debug when refreshing the entry for the host the new VM is running on. The 2 existing VM are recognized, but the third is missing without any errors.

dougiteixeira commented 1 year ago

EDIT: I found it in the logs, but don't know how to copy the lines. I am using the SSH Addon. Ctrl +C doesn't work. Also right-click "copy line" doens't work.

You can access the logs directly through the browser: Settings > System > Logs, click the Download Full Logs button.

It is expected to see information from your Proxmox API in the debug logs. To do this, you have to include the code snippet above in your configuration.yaml file and restart Home Assistant. After that, download the log file and upload it here.

Jarod2801 commented 1 year ago

home-assistant_2023-11-09T22-51-41.869Z.log

Attached the debug log. The node the 3 VMs are running at is called "proxmox3". The VMs are called "plex", "librenms" and "helper-1".

helper-1 is missing in HA.

dougiteixeira commented 1 year ago

@Jarod2801 I included in version 2.1 the ability to download a diagnostic file, please, can you update, download the diagnostic file (see here how to download) and send it here so I can analyze it better?

Jarod2801 commented 1 year ago

config_entry-proxmoxve-2871cbd147f78e9847f62c64a46008a6.json.txt Attached the diag file.

I noticed that the VM "helper-1" (the missing one) has some entries in the diag file, but cannot find the issue. I think @dougiteixeira you're the right one for that ;-)

dougiteixeira commented 1 year ago

I found your problem... new VM/Containers need to be exposed through the options in the integration configuration entry, just click on the CONFIGURE button and then on Add or remove Nodes, VMs or Containers.

Jarod2801 commented 12 months ago

I completely missed this menu entry. Thamk you very much for the hint. So it was definitely a layer 8 issue ;-)

But what I found was another issue: The entities are added, but looks like the integration is using different languages when adding initially or when adding a VM afterwards.

E.g. an initial entry ist called "sensor.qemu_librenms_101_uptime", same entity of the VM added via the menu is called "sensor.qemu_helper_1_102_betriebszeit".

So looks like it's using the UI language for naming the entities.

I will create a new issue for this.

Jarod2801 commented 12 months ago

Closed

dougiteixeira commented 12 months ago

But what I found was another issue: The entities are added, but looks like the integration is using different languages when adding initially or when adding a VM afterwards.

E.g. an initial entry ist called "sensor.qemu_librenms_101_uptime", same entity of the VM added via the menu is called "sensor.qemu_helper_1_102_betriebszeit".

So looks like it's using the UI language for naming the entities.

This is not an issue... entities are created according to the language configured in Configuration > System > General. What happened is that when your first entities were created there was no support for your language in the integration, but recently natives contributed to the translation of the integration into your language, so the entities created from there used your configured language.

So don't open a new issue.

dougiteixeira / proxmoxve