UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Meister Mopper]

@alero sagte in [Neuer Adapter] Proxmox VM:

kann ich das dann so machen?

KA, ich nutze das nicht.

[Ein ehemaliger Benutzer]

@alero sagte in [Neuer Adapter] Proxmox VM:

IP, Port, User und PW sind richtig. Damit kann ich mich auf dem Proxmox Server anmelden. Muss ich noch was im Proxmox freigeben?

Moin,

war zu faul, alles zu lesen, Du hast die falsche Domäne, das ist immer PAM, nicht PVE

VG
Bernd

[Alero]

@dp20eic
hi,
ja mit pam ging es auch nicht . erst als ich nichts eingetragen habe hat es geklappt.

erst mal vielen Dank für eure Hilfe.

[Negalein]

Hallo

Hat noch jemand das Problem mit has no existing object, this might lead to an error in future versions?

Issue hab ich gerade erstellt.

[arteck]

@negalein welche adapter version..ahh ich seh 2.2.0

da wurde das object nicht angelegt

proxmox.0.storage_proxmox_local-lvm

lösche den mal .. und starte den adapter neu

[Ein ehemaliger Benutzer]

@arteck

wenn du grad an dem Thema bist, ich hab mal alle Objects von Proxmox geloescht und den Adapter dann neu gestartet, hier kommt das bei den vmid , Adapter Version 2.2.0 :

2023-10-27 09:16:32.292  - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860
2023-10-27 09:16:33.146  - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14
2023-10-27 09:16:33.156  - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json
2023-10-27 09:16:33.605  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.672  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.742  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.789  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.826  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.902  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.960  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.023  - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.054  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.141  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.219  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.275  - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.335  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:32.256  - info: host.themachine "system.adapter.proxmox.0" enabled
2023-10-27 09:16:32.292  - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860
2023-10-27 09:16:33.146  - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14
2023-10-27 09:16:33.156  - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json
2023-10-27 09:16:33.605  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.672  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.742  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.789  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.826  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.902  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:33.960  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.023  - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.054  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.141  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.219  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.275  - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number"
2023-10-27 09:16:34.335  - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number"

[arteck]

@ilovegym schau ich mir an.. welche proxmox version ?? 6,7,8 ?

[Ein ehemaliger Benutzer]

@arteck

Proxmox V8.0.4

[ticaki]

Adapter v2.2.0
Proxmox v8.0.4

Löschen der Objekte und restart.

Ich habe den String proxmox.0.lxc_pihole.vmid nicht in den letzten 2 Tagen im Log gefunden, scheint also nur bei/mit/vor/nach dem Erstellen der States zu passieren. :)

2023-10-27 09:59:39.426 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_pihole.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:39.738 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_zigbee2mqtt.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:39.998 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mqtt.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:40.287 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_influxdb.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:40.466 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bind.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:40.774 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mariadb.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:41.163 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_grafana.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:41.600 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_samba.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:41.718 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_scrypted.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.019 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_plex.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.223 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wireguard.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.431 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_openssl.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.627 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.794 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_iobroker-test.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:42.932 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_tautulli.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:43.177 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wikijs.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:43.307 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mediamtx.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:43.619 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_redis.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:43.760 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker-devel.vmid" has to be type "string" but received type "number"
2023-10-27 09:59:43.917 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bookworm-template-sudo-tim.vmid" has to be type "string" but received type "number"

[arteck]

isch guck später nach

[Ein ehemaliger Benutzer]

@arteck sagte in [Neuer Adapter] Proxmox VM:

isch guck später nach

... wenn du schon dabei bist... hier kam gerade waehrend des Backups des LXC, indem iobroker laeuft, diese Errors:

Spoiler

2023-10-27 12:26:58.713  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:26:58.714  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:26:58.832  - info: mqtt.1 (1223) Client [Presence1221] connection closed: closed
2023-10-27 12:26:58.669  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: Querying lock state: unlocked
2023-10-27 12:26:58.713  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:26:58.714  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:26:58.832  - info: mqtt.1 (1223) Client [Presence1221] connection closed: closed
2023-10-27 12:27:01.065  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:01.121  - info: sonoff.0 (640) Client [S5V-4] connection closed: closed
2023-10-27 12:27:01.065  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:01.121  - info: sonoff.0 (640) Client [S5V-4] connection closed: closed
2023-10-27 12:27:02.964  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Querying lock battery state: failed
2023-10-27 12:27:02.964  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Querying lock battery state: failed
2023-10-27 12:27:03.716  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:03.716  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:08.116  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Reading config. Result: failed
2023-10-27 12:27:08.116  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Reading config. Result: failed
2023-10-27 12:27:08.719  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:08.719  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:09.061  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402429044_5996
2023-10-27 12:27:08.719  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:08.719  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:09.061  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402429044_5996
2023-10-27 12:27:11.065  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:11.065  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:12.460  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Reading advanced config. Result: failed
2023-10-27 12:27:12.460  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub BI: Reading advanced config. Result: failed
2023-10-27 12:27:13.721  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:13.721  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:18.723  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:18.723  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:18.723  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:18.723  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:21.064  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:21.064  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:23.725  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:23.725  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:28.727  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:28.727  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:28.727  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:28.727  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:31.066  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:31.066  - warn: tuya.0 (788) bf88c2fc494909d538nhnf.20: A set command is already in progress. Can not issue a second one that also should return a response.. Try to use cloud.
2023-10-27 12:27:32.385  - info: mqtt.1 (1223) Client [Presence1221] connection closed: timeout
2023-10-27 12:27:32.385  - info: mqtt.1 (1223) Client [Presence1221] connection closed: timeout
2023-10-27 12:27:33.730  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:33.730  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:38.732  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:38.732  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:38.732  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:38.732  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:43.734  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:43.734  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:48.735  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:48.736  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:48.735  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:48.736  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:53.738  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:53.738  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:27:56.752  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: unlocked
2023-10-27 12:27:56.752  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: unlocked
2023-10-27 12:27:58.740  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:58.740  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:58.740  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:27:58.740  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:02.713  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402482713_3323
2023-10-27 12:28:02.713  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402482713_3323
2023-10-27 12:28:03.321  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: unlocked
2023-10-27 12:28:03.742  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:03.321  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: unlocked
2023-10-27 12:28:03.742  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:08.744  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:08.744  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:08.744  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:08.744  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:13.746  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:13.746  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:17.676  - warn: synochat.0 (5912) Attempt to send message '8b032070-74b3-11ee-8289-9fa88030d194' failed due to too fast sending sequence: 'create post too fast' > Delaying the message for 1 second/s...
2023-10-27 12:28:17.676  - warn: synochat.0 (5912) Attempt to send message '8b032070-74b3-11ee-8289-9fa88030d194' failed due to too fast sending sequence: 'create post too fast' > Delaying the message for 1 second/s...
2023-10-27 12:28:18.748  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:18.748  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:18.748  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:18.748  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:23.750  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:23.750  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:28.752  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:28.752  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:28.752  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:28.752  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:33.753  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:33.753  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:38.756  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:38.756  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:38.756  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:38.756  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:41.532  - info: mqtt.1 (1223) Client [Presence1220] connection closed: timeout
2023-10-27 12:28:41.532  - info: mqtt.1 (1223) Client [Presence1220] connection closed: timeout
2023-10-27 12:28:43.758  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:43.758  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:48.760  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:48.760  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:48.890  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: unlocked
2023-10-27 12:28:48.760  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:48.760  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:48.890  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: Querying lock state: Querying lock state: Querying lock state: unlocked
2023-10-27 12:28:53.762  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:53.762  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:28:58.764  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:58.764  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:58.764  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:28:58.764  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:01.064  - info: mqtt.1 (1223) Client [Presence1222] connection closed: timeout
2023-10-27 12:29:01.064  - info: mqtt.1 (1223) Client [Presence1222] connection closed: timeout
2023-10-27 12:29:02.932  - info: mqtt.1 (1223) Client [Presence1221] connection closed: closed
2023-10-27 12:29:02.932  - info: mqtt.1 (1223) Client [Presence1221] connection closed: closed
2023-10-27 12:29:03.766  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:03.766  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:07.889  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: unlocked
2023-10-27 12:29:07.889  - info: javascript.0 (461) script.js.common.Nuki.mqtt2log: NUKI Hub WT: Querying lock state: Querying lock state: unlocked
2023-10-27 12:29:08.769  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:08.769  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:08.769  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:08.769  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:13.229  - info: mqtt.1 (1223) Client [Presence1220] connected with secret 1698402553186_4082
2023-10-27 12:29:13.229  - info: mqtt.1 (1223) Client [Presence1220] connected with secret 1698402553186_4082
2023-10-27 12:29:13.771  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:13.771  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:16.778  - info: bluelink.0 (1435) Read new update for KMHKR81AFNU011963 directly from the car
2023-10-27 12:29:16.778  - info: bluelink.0 (1435) Read new update for KMHKR81AFNU011963 directly from the car
2023-10-27 12:29:18.773  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:18.773  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:18.773  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:18.773  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:21.407  - info: sonoff.0 (640) Client [nx4519-1] reconnected. Old secret 1698388565136_7187. New secret 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends publish. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends pingreq. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends publish. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.889  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402561878_5954
2023-10-27 12:29:21.407  - info: sonoff.0 (640) Client [nx4519-1] reconnected. Old secret 1698388565136_7187. New secret 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends publish. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends pingreq. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.506  - warn: sonoff.0 (640) Old client nx4519-1 with secret 1698388565136_7187 sends publish. Ignore! Actual secret is 1698402561404_1831
2023-10-27 12:29:21.889  - info: mqtt.1 (1223) Client [Presence1221] connected with secret 1698402561878_5954
2023-10-27 12:29:23.775  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:23.775  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:28.777  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:28.777  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:28.777  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:28.777  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:31.327  - info: mqtt.1 (1223) Client [Presence1222] connected with secret 1698402571314_8823
2023-10-27 12:29:31.327  - info: mqtt.1 (1223) Client [Presence1222] connected with secret 1698402571314_8823
2023-10-27 12:29:32.379  - info: tuya.0 (788) 30530530c45bbedb673e: Connect locally to device
2023-10-27 12:29:32.380  - info: tuya.0 (788) 30530530c45bbedb673e Init with IP=10.1.12.106, Key=>':x*F6`S#`J14cF, Version=3.3
2023-10-27 12:29:32.379  - info: tuya.0 (788) 30530530c45bbedb673e: Connect locally to device
2023-10-27 12:29:32.380  - info: tuya.0 (788) 30530530c45bbedb673e Init with IP=10.1.12.106, Key=>':x*F6`S#`J14cF, Version=3.3
2023-10-27 12:29:33.779  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:33.779  - error: proxmox.0 (78860) Unable to update ticket: -1
2023-10-27 12:29:37.865  - info: bluelink.0 (1435) Update for KMHKR81AFNU011963 successfull
2023-10-27 12:29:37.865  - info: bluelink.0 (1435) Update for KMHKR81AFNU011963 successfull
2023-10-27 12:29:38.781  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:38.781  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:38.781  - error: proxmox.0 (78860) Use Next Proxmox Host because of communication failure https://192.168.0.210:8006/api2/json/nodes/hpg380/storage/VMBackup/content
2023-10-27 12:29:38.781  - error: proxmox.0 (78860) Error received response from /nodes/hpg380/storage/VMBackup/content

[arteck]

@ilovegym sagte in [Neuer Adapter] Proxmox VM:

/nodes/hpg380/storage/VMBackup/content

da ist der storage nicht da.. und da du nur 1 node hast oder nur angegeben hast, kann der nicht switchen

früher war die meldung unterdrückt

[Ein ehemaliger Benutzer]

@arteck

ja, weil er gerade am backup schreiben ist.. hmmpff d.h. die Meldung kommt jetzt immer, wenn ich ein Backup mache in Proxmox.. ? mit dem LXC.. ?
Kann man da das Timeout hoeher setzen.. fuer den Fehler? er kommt genau einmal, wie im Logfile, dann ist wieder ruhe..

[Negalein]

@arteck sagte in [Neuer Adapter] Proxmox VM:

lösche den mal .. und starte den adapter neu

Danke, funktioniert wieder.

[arteck]

@ilovegym dann guckemal jetzt

[bahnuhr]

@arteck

habe auch von git installiert.

Bitte noch überprüfen:
maxmem wird bei den Objekten nicht aktualisiert.

sowohl dies:

als auch dies:

[arteck]

@bahnuhr

vm :
doch..die maschiene muss aber laufen..

node schau ich noch

das ist die einstellung

[bahnuhr]

@arteck
Na klar ist die Maschine an.

Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.

Die anderen DP von mem werden dagegen regelmäßig (so alle 30 Sek.) aktualisiert.

[arteck]

@bahnuhr guckmal jetzt

ausserdem macht der nur eine Aktualisierung wenn sich was geändert hat...

[Ein ehemaliger Benutzer]

@bahnuhr sagte in [Neuer Adapter] Proxmox VM:

Und ja, der DP wird bei start der Instanz aktualisiert.
Aber dann nicht mehr.

Moin,

max Mem. ist ja eher ein statischer Wert, der sich nicht laufend ändert, wohin gegen Mem. sich zur Laufzeit schon veränder, Du muss mal mit der Einstellung von MaxMem, spielen und dann schauen, ob die Änderung angezeigt wird.

VG
Bernd