Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Entwicklung
  4. [Neuer Adapter] Proxmox VM

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.6k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.1k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.8k

[Neuer Adapter] Proxmox VM

Geplant Angeheftet Gesperrt Verschoben Entwicklung
proxmox
486 Beiträge 75 Kommentatoren 113.1k Aufrufe 58 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • A Alero

    @meister-mopper
    ok
    hier der weg den ich gehe wenn ich die Seite das erste mal aufrufen ( gelöschter Browser Cache) Chrome
    4cb7ad77-04f8-4336-89de-fcad74aca70f-image.png
    f16cb65f-9d8d-4c38-b08e-bbbf7bc02caa-image.png
    dann erweitert drücken
    dann Weiter zu 192.168.42.90 (unsicher)
    4f5dbde2-a1a4-4fc9-84d7-539ee22543ac-image.png
    hier sehe ich das ich pam ausgewählt habe. mit pve komme ich mit meinem User nicht rein. dann melde ich mich an.

    Meister MopperM Abwesend
    Meister MopperM Abwesend
    Meister Mopper
    schrieb am zuletzt editiert von
    #284

    @alero

    Und somit wird auch bei dir via https kommuniziert. Der PAM-login ist richtig, da dies auch über ssh funktioniert.

    PVE-User können sich nur in der GUI einloggen.

    Proxmox und HA

    A 1 Antwort Letzte Antwort
    0
    • Meister MopperM Meister Mopper

      @alero

      Und somit wird auch bei dir via https kommuniziert. Der PAM-login ist richtig, da dies auch über ssh funktioniert.

      PVE-User können sich nur in der GUI einloggen.

      A Offline
      A Offline
      Alero
      schrieb am zuletzt editiert von Alero
      #285

      @meister-mopper
      hi,

      leider nein

      1b8d50d2-d292-4669-8c15-d5892cfa964b-image.png
      das würde ich gerne noch hin bekommen.

      Meister MopperM 1 Antwort Letzte Antwort
      0
      • A Alero

        @meister-mopper
        hi,

        leider nein

        1b8d50d2-d292-4669-8c15-d5892cfa964b-image.png
        das würde ich gerne noch hin bekommen.

        Meister MopperM Abwesend
        Meister MopperM Abwesend
        Meister Mopper
        schrieb am zuletzt editiert von
        #286

        @alero sagte in [Neuer Adapter] Proxmox VM:

        das würde ich gerne noch hin bekommen.

        Im Chrome und Edge bleibt dieser Hinweis. Wenn du ihn nicht magst, musst du dich wohl mit ACME und Proxmox auseinandersetzen müssen :man-shrugging:

        Proxmox und HA

        A 1 Antwort Letzte Antwort
        0
        • Meister MopperM Meister Mopper

          @alero sagte in [Neuer Adapter] Proxmox VM:

          das würde ich gerne noch hin bekommen.

          Im Chrome und Edge bleibt dieser Hinweis. Wenn du ihn nicht magst, musst du dich wohl mit ACME und Proxmox auseinandersetzen müssen :man-shrugging:

          A Offline
          A Offline
          Alero
          schrieb am zuletzt editiert von Alero
          #287

          @meister-mopper
          habe heirzu schon ein Video gefunden. kann ich das dann so machen?
          Proxmox SSL Certificates with Let's Encrypt
          Zertifikate ist nicht so meins. Habe angst das mein proxmox nachher nicht mehr läuft bzw. ich mich nicht mehr anmelden kann.

          Meister MopperM 1 Antwort Letzte Antwort
          0
          • A Alero

            @meister-mopper
            habe heirzu schon ein Video gefunden. kann ich das dann so machen?
            Proxmox SSL Certificates with Let's Encrypt
            Zertifikate ist nicht so meins. Habe angst das mein proxmox nachher nicht mehr läuft bzw. ich mich nicht mehr anmelden kann.

            Meister MopperM Abwesend
            Meister MopperM Abwesend
            Meister Mopper
            schrieb am zuletzt editiert von
            #288

            @alero sagte in [Neuer Adapter] Proxmox VM:

            kann ich das dann so machen?

            KA, ich nutze das nicht.

            Proxmox und HA

            1 Antwort Letzte Antwort
            0
            • A Alero

              hi,
              habe mir den proxmox adapter installiert leider bekomme ich keine Verbindung:

              
proxmox.0
2023-10-13 15:31:07.983	error	401: wrong User data, could not log in, please try again with correct user and pw

proxmox.0
2023-10-13 15:31:07.983	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

proxmox.0
2023-10-13 15:31:07.982	error	Unable to authenticate with Proxmox host. Please check your credentials

proxmox.0
2023-10-13 15:31:04.888	debug	Use Proxmox API: https://192.168.42.90:8006/api2/json

              334674f2-5975-4423-b459-326e4b23a1d1-image.png

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

              ? Offline
              ? Offline
              Ein ehemaliger Benutzer
              schrieb am zuletzt editiert von
              #289

              @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
              4973da7c-6635-4d28-bb40-403acb9f94a4-grafik.png

              VG
              Bernd

              A 1 Antwort Letzte Antwort
              0
              • ? 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
                4973da7c-6635-4d28-bb40-403acb9f94a4-grafik.png

                VG
                Bernd

                A Offline
                A Offline
                Alero
                schrieb am zuletzt editiert von
                #290

                @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.

                1 Antwort Letzte Antwort
                0
                • NegaleinN Offline
                  NegaleinN Offline
                  Negalein
                  Global Moderator
                  schrieb am zuletzt editiert von
                  #291

                  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.

                  ° Node.js: 20.17.0 NPM: 10.8.2
                  ° Proxmox, Ubuntu 22.04.3 LTS
                  ° Fixer ---> iob fix

                  arteckA 1 Antwort Letzte Antwort
                  0
                  • NegaleinN 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.

                    arteckA Offline
                    arteckA Offline
                    arteck
                    Developer Most Active
                    schrieb am zuletzt editiert von arteck
                    #292

                    @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

                    zigbee hab ich, zwave auch, nuc's genauso und HA auch

                    ? NegaleinN 2 Antworten Letzte Antwort
                    1
                    • arteckA 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

                      ? Offline
                      ? Offline
                      Ein ehemaliger Benutzer
                      schrieb am zuletzt editiert von Ein ehemaliger Benutzer
                      #293

                      @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"
                      arteckA 1 Antwort Letzte Antwort
                      0
                      • ? 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"
                        arteckA Offline
                        arteckA Offline
                        arteck
                        Developer Most Active
                        schrieb am zuletzt editiert von arteck
                        #294

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

                        zigbee hab ich, zwave auch, nuc's genauso und HA auch

                        ? 1 Antwort Letzte Antwort
                        0
                        • arteckA arteck

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

                          ? Offline
                          ? Offline
                          Ein ehemaliger Benutzer
                          schrieb am zuletzt editiert von
                          #295

                          @arteck

                          Proxmox V8.0.4

                          1 Antwort Letzte Antwort
                          0
                          • T Nicht stören
                            T Nicht stören
                            ticaki
                            schrieb am zuletzt editiert von ticaki
                            #296

                            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"

                            Weather-Warnings Espresense NSPanel-Lovelace-ui Tagesschau

                            Spenden

                            1 Antwort Letzte Antwort
                            0
                            • arteckA Offline
                              arteckA Offline
                              arteck
                              Developer Most Active
                              schrieb am zuletzt editiert von
                              #297

                              isch guck später nach

                              zigbee hab ich, zwave auch, nuc's genauso und HA auch

                              ? 1 Antwort Letzte Antwort
                              0
                              • arteckA arteck

                                isch guck später nach

                                ? Offline
                                ? Offline
                                Ein ehemaliger Benutzer
                                schrieb am zuletzt editiert von
                                #298

                                @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:

                                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

                                arteckA 1 Antwort Letzte Antwort
                                0
                                • ? 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:

                                  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

                                  arteckA Offline
                                  arteckA Offline
                                  arteck
                                  Developer Most Active
                                  schrieb am zuletzt editiert von arteck
                                  #299

                                  @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

                                  zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                  ? 1 Antwort Letzte Antwort
                                  0
                                  • arteckA 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

                                    ? Offline
                                    ? Offline
                                    Ein ehemaliger Benutzer
                                    schrieb am zuletzt editiert von
                                    #300

                                    @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..

                                    arteckA 1 Antwort Letzte Antwort
                                    0
                                    • arteckA 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

                                      NegaleinN Offline
                                      NegaleinN Offline
                                      Negalein
                                      Global Moderator
                                      schrieb am zuletzt editiert von
                                      #301

                                      @arteck sagte in [Neuer Adapter] Proxmox VM:

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

                                      Danke, funktioniert wieder.

                                      ° Node.js: 20.17.0 NPM: 10.8.2
                                      ° Proxmox, Ubuntu 22.04.3 LTS
                                      ° Fixer ---> iob fix

                                      1 Antwort Letzte Antwort
                                      0
                                      • ? 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..

                                        arteckA Offline
                                        arteckA Offline
                                        arteck
                                        Developer Most Active
                                        schrieb am zuletzt editiert von
                                        #302

                                        @ilovegym dann guckemal jetzt

                                        zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                        bahnuhrB 1 Antwort Letzte Antwort
                                        0
                                        • arteckA arteck

                                          @ilovegym dann guckemal jetzt

                                          bahnuhrB Online
                                          bahnuhrB Online
                                          bahnuhr
                                          Forum Testing Most Active
                                          schrieb am zuletzt editiert von bahnuhr
                                          #303

                                          @arteck

                                          habe auch von git installiert.

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

                                          sowohl dies:
                                          9ee736f7-41b3-48f8-9de2-277d157592bd-image.png

                                          als auch dies:
                                          77ef60ee-ba2c-47db-8f83-fdfd9aa269e7-image.png

                                          Wenn ich helfen konnte, dann Daumen hoch (Pfeil nach oben)!
                                          Danke.
                                          gute Forenbeiträge: https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge
                                          ScreenToGif :https://www.screentogif.com/downloads.html

                                          arteckA 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          817

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden
                                          • Du hast noch kein Konto? Registrieren
                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe