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. ioBroker Allgemein
  4. Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    2.1k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    936

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.2k

Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
75 Beiträge 8 Kommentatoren 1.5k Aufrufe 7 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.
  • M Offline
    M Offline
    marcelinho
    schrieb am zuletzt editiert von
    #64

    weiß jemand wieso mein Backitup bei Influxdb nicht geht, habe die Token neu erstellt mit allen rechten aber irgendwie läuft es nicht:

    19:56:58.888DEBUGinfluxDBInfluxDB-Backup started ...
    19:56:58.892DEBUGinfluxDBStart InfluxDB Backup ...
    19:56:58.901DEBUGinfluxDBInfluxDB Backup tmp directory created
    [DEBUG] [influxDB] -
    19:56:59.372ERRORinfluxDBError: Command failed: influx backup --bucket admin --host http://localhost:8086 -t tX9aUgElHh8iiEJKoYay0Zhsxjr1OTuAnSaiR73lfwUAXzYlD3MlJeu_g6_WbjAnLKMFsAPylqSJ2f7Ke4BfZg== "/opt/iobroker/backups/influxDB_2026_01_10-19_56_58_backupiobroker"
    2026/01/10 19:56:59 INFO: Downloading metadata snapshot
    Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
    19:56:59.382DEBUGinfluxDBInfluxDB-Backup for is finish
    19:56:59.385DEBUGinfluxDBdone
    

    Die Tokens stimmen, die Adapter sind grün. Wüsste nicht wo es hakt. Kann es mit Debian 13 zu tun haben bei Influx 2.x ? auf meiner anderen Micro SD mit Debian 12 geht es mit den Einstellungen.

    HomoranH Thomas BraunT crunchipC 3 Antworten Letzte Antwort
    0
    • M marcelinho

      weiß jemand wieso mein Backitup bei Influxdb nicht geht, habe die Token neu erstellt mit allen rechten aber irgendwie läuft es nicht:

      19:56:58.888DEBUGinfluxDBInfluxDB-Backup started ...
      19:56:58.892DEBUGinfluxDBStart InfluxDB Backup ...
      19:56:58.901DEBUGinfluxDBInfluxDB Backup tmp directory created
      [DEBUG] [influxDB] -
      19:56:59.372ERRORinfluxDBError: Command failed: influx backup --bucket admin --host http://localhost:8086 -t tX9aUgElHh8iiEJKoYay0Zhsxjr1OTuAnSaiR73lfwUAXzYlD3MlJeu_g6_WbjAnLKMFsAPylqSJ2f7Ke4BfZg== "/opt/iobroker/backups/influxDB_2026_01_10-19_56_58_backupiobroker"
      2026/01/10 19:56:59 INFO: Downloading metadata snapshot
      Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
      19:56:59.382DEBUGinfluxDBInfluxDB-Backup for is finish
      19:56:59.385DEBUGinfluxDBdone
      

      Die Tokens stimmen, die Adapter sind grün. Wüsste nicht wo es hakt. Kann es mit Debian 13 zu tun haben bei Influx 2.x ? auf meiner anderen Micro SD mit Debian 12 geht es mit den Einstellungen.

      HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #65

      @marcelinho sagte in Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana:

      Die Tokens stimmen, die Adapter sind grün

      das heisst gar nix!
      für backitup brauchst du das admin token

      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      1 Antwort Letzte Antwort
      0
      • M marcelinho

        weiß jemand wieso mein Backitup bei Influxdb nicht geht, habe die Token neu erstellt mit allen rechten aber irgendwie läuft es nicht:

        19:56:58.888DEBUGinfluxDBInfluxDB-Backup started ...
        19:56:58.892DEBUGinfluxDBStart InfluxDB Backup ...
        19:56:58.901DEBUGinfluxDBInfluxDB Backup tmp directory created
        [DEBUG] [influxDB] -
        19:56:59.372ERRORinfluxDBError: Command failed: influx backup --bucket admin --host http://localhost:8086 -t tX9aUgElHh8iiEJKoYay0Zhsxjr1OTuAnSaiR73lfwUAXzYlD3MlJeu_g6_WbjAnLKMFsAPylqSJ2f7Ke4BfZg== "/opt/iobroker/backups/influxDB_2026_01_10-19_56_58_backupiobroker"
        2026/01/10 19:56:59 INFO: Downloading metadata snapshot
        Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
        19:56:59.382DEBUGinfluxDBInfluxDB-Backup for is finish
        19:56:59.385DEBUGinfluxDBdone
        

        Die Tokens stimmen, die Adapter sind grün. Wüsste nicht wo es hakt. Kann es mit Debian 13 zu tun haben bei Influx 2.x ? auf meiner anderen Micro SD mit Debian 12 geht es mit den Einstellungen.

        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #66

        @marcelinho sagte in Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana:

        Kann es mit Debian 13 zu tun haben bei Influx 2.x ?

        Nein.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        1 Antwort Letzte Antwort
        0
        • M marcelinho

          weiß jemand wieso mein Backitup bei Influxdb nicht geht, habe die Token neu erstellt mit allen rechten aber irgendwie läuft es nicht:

          19:56:58.888DEBUGinfluxDBInfluxDB-Backup started ...
          19:56:58.892DEBUGinfluxDBStart InfluxDB Backup ...
          19:56:58.901DEBUGinfluxDBInfluxDB Backup tmp directory created
          [DEBUG] [influxDB] -
          19:56:59.372ERRORinfluxDBError: Command failed: influx backup --bucket admin --host http://localhost:8086 -t tX9aUgElHh8iiEJKoYay0Zhsxjr1OTuAnSaiR73lfwUAXzYlD3MlJeu_g6_WbjAnLKMFsAPylqSJ2f7Ke4BfZg== "/opt/iobroker/backups/influxDB_2026_01_10-19_56_58_backupiobroker"
          2026/01/10 19:56:59 INFO: Downloading metadata snapshot
          Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
          19:56:59.382DEBUGinfluxDBInfluxDB-Backup for is finish
          19:56:59.385DEBUGinfluxDBdone
          

          Die Tokens stimmen, die Adapter sind grün. Wüsste nicht wo es hakt. Kann es mit Debian 13 zu tun haben bei Influx 2.x ? auf meiner anderen Micro SD mit Debian 12 geht es mit den Einstellungen.

          crunchipC Offline
          crunchipC Offline
          crunchip
          Forum Testing Most Active
          schrieb am zuletzt editiert von
          #67

          @marcelinho sagte in Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana:

          habe die Token neu erstellt

          https://docs.influxdata.com/influxdb/v2/admin/backup-restore/backup/
          The root authorization token (the token created for the first user in the InfluxDB setup process).
          https://docs.influxdata.com/influxdb/v2/admin/tokens/

          umgestiegen von Proxmox auf Unraid

          1 Antwort Letzte Antwort
          0
          • M Offline
            M Offline
            marcelinho
            schrieb am zuletzt editiert von
            #68

            versteht jemand warum ich mich beim Backup im Kreis drehe? Bei der InfluxDB Adapter ist grün Daten kommen in Grafana an. Token läuft. Aber wenn ich ein All Access API Token erstelle kommt immer der Fehler:
            "401 Unauthorized"

            pi@raspberrypi:~ $ rm influxdb2-client-2.7.5-linux-amd64.tar.gz
            pi@raspberrypi:~ $ rm -rf ~/.influxdbv2
            pi@raspberrypi:~ $ rm -f ~/influxdb2-client-*.tar.gz
            rm -rf ~/.influxdbv2
            sudo rm -f /usr/bin/influx
            sudo rm -f /usr/local/bin/influx
            pi@raspberrypi:~ $ curl -sL https://repos.influxdata.com/influxdata-archive.key | sudo gpg --dearmor -o /usr/share/keyrings/influxdata-archive.gpg
            echo "deb [signed-by=/usr/share/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main" | sudo tee /etc/apt/sources.list.d/influxdata.list
            sudo apt update
            File '/usr/share/keyrings/influxdata-archive.gpg' exists. Overwrite? (y/N) y
            deb [signed-by=/usr/share/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main
            Hit:1 http://deb.debian.org/debian trixie InRelease
            Hit:2 http://deb.debian.org/debian trixie-updates InRelease
            Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
            Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
            Hit:5 https://repos.influxdata.com/debian stable InRelease
            Hit:6 https://apt.grafana.com stable InRelease
            Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
            All packages are up to date.
            Warning: https://deb.nodesource.com/node_24.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
            pi@raspberrypi:~ $ sudo apt install influxdb2-cli -y
            Installing:
              influxdb2-cli
            
            Summary:
              Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
              Download size: 0 B / 11.0 MB
              Space needed: 24.7 MB / 20.9 GB available
            
            Selecting previously unselected package influxdb2-cli.
            (Reading database ... 115732 files and directories currently installed.)
            Preparing to unpack .../influxdb2-cli_2.7.5-3_arm64.deb ...
            Unpacking influxdb2-cli (2.7.5-3) ...
            Setting up influxdb2-cli (2.7.5-3) ...
            pi@raspberrypi:~ $ influx version
            Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:26Z
            pi@raspberrypi:~ $ export INFLUX_TOKEN=xjIUdQBiweNaUi4jNnq7t0QiCRMYahTp1k8O91CNfOHobTWtFNfjI6R3gaeA8msuoxeeouI_eIGu6g7KmRfxew==
            pi@raspberrypi:~ $ influx org list
            ID                      Name
            9fc10391e54f07c7        admin
            pi@raspberrypi:~ $ mkdir -p /home/pi/influx-backup-test
            influx backup --org admin /home/pi/influx-backup-test
            2026/01/13 15:06:54 INFO: Downloading metadata snapshot
            Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
            pi@raspberrypi:~ $ rm -rf /home/pi/influx-backup-test
            pi@raspberrypi:~ $
            
            
            Marc BergM 1 Antwort Letzte Antwort
            0
            • M marcelinho

              versteht jemand warum ich mich beim Backup im Kreis drehe? Bei der InfluxDB Adapter ist grün Daten kommen in Grafana an. Token läuft. Aber wenn ich ein All Access API Token erstelle kommt immer der Fehler:
              "401 Unauthorized"

              pi@raspberrypi:~ $ rm influxdb2-client-2.7.5-linux-amd64.tar.gz
              pi@raspberrypi:~ $ rm -rf ~/.influxdbv2
              pi@raspberrypi:~ $ rm -f ~/influxdb2-client-*.tar.gz
              rm -rf ~/.influxdbv2
              sudo rm -f /usr/bin/influx
              sudo rm -f /usr/local/bin/influx
              pi@raspberrypi:~ $ curl -sL https://repos.influxdata.com/influxdata-archive.key | sudo gpg --dearmor -o /usr/share/keyrings/influxdata-archive.gpg
              echo "deb [signed-by=/usr/share/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main" | sudo tee /etc/apt/sources.list.d/influxdata.list
              sudo apt update
              File '/usr/share/keyrings/influxdata-archive.gpg' exists. Overwrite? (y/N) y
              deb [signed-by=/usr/share/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main
              Hit:1 http://deb.debian.org/debian trixie InRelease
              Hit:2 http://deb.debian.org/debian trixie-updates InRelease
              Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
              Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
              Hit:5 https://repos.influxdata.com/debian stable InRelease
              Hit:6 https://apt.grafana.com stable InRelease
              Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
              All packages are up to date.
              Warning: https://deb.nodesource.com/node_24.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
              pi@raspberrypi:~ $ sudo apt install influxdb2-cli -y
              Installing:
                influxdb2-cli
              
              Summary:
                Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
                Download size: 0 B / 11.0 MB
                Space needed: 24.7 MB / 20.9 GB available
              
              Selecting previously unselected package influxdb2-cli.
              (Reading database ... 115732 files and directories currently installed.)
              Preparing to unpack .../influxdb2-cli_2.7.5-3_arm64.deb ...
              Unpacking influxdb2-cli (2.7.5-3) ...
              Setting up influxdb2-cli (2.7.5-3) ...
              pi@raspberrypi:~ $ influx version
              Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:26Z
              pi@raspberrypi:~ $ export INFLUX_TOKEN=xjIUdQBiweNaUi4jNnq7t0QiCRMYahTp1k8O91CNfOHobTWtFNfjI6R3gaeA8msuoxeeouI_eIGu6g7KmRfxew==
              pi@raspberrypi:~ $ influx org list
              ID                      Name
              9fc10391e54f07c7        admin
              pi@raspberrypi:~ $ mkdir -p /home/pi/influx-backup-test
              influx backup --org admin /home/pi/influx-backup-test
              2026/01/13 15:06:54 INFO: Downloading metadata snapshot
              Error: failed to backup metadata: failed to download metadata snapshot: 401 Unauthorized: read:authorizations is unauthorized
              pi@raspberrypi:~ $ rm -rf /home/pi/influx-backup-test
              pi@raspberrypi:~ $
              
              
              Marc BergM Offline
              Marc BergM Offline
              Marc Berg
              Most Active
              schrieb am zuletzt editiert von
              #69

              @marcelinho sagte in Hilfestellung Raspi4: Zigbee2Mqtt, InfluxDB, Grafana:

              All Access API Token

              Falscher Token-Typ. Schau bitte in die Doku zum Backitup Adapter

              https://github.com/simatec/ioBroker.backitup/wiki/Diverse-Anleitungen-für-ioBroker.backitup#operator-token-für-influxdb-2x-wiederherstellen

              NUC10I3+Ubuntu+Docker+ioBroker+influxDB2+Node Red+EMQX+Grafana

              Pi-hole, Traefik, Checkmk, Conbee II+Zigbee2MQTT, ESPSomfy-RTS, LoRaWAN, Arduino, KiCad

              Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

              1 Antwort Letzte Antwort
              0
              • M Offline
                M Offline
                marcelinho
                schrieb am zuletzt editiert von
                #70

                @marc-berg danke vielmals, hat geklappt.
                Jetzt habe ich alles konfiguriert :) Nur noch eine "Fehlermeldung" ist die zu vernachlässigen?

                pi@raspberrypi:~ $ sudo apt update
                Hit:1 http://deb.debian.org/debian trixie InRelease
                Hit:2 http://deb.debian.org/debian trixie-updates InRelease
                Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
                Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
                Hit:5 https://repos.influxdata.com/debian stable InRelease
                Hit:6 https://apt.grafana.com stable InRelease
                Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                Fetched 43.4 kB in 0s (88.8 kB/s)
                All packages are up to date.
                Warning: https://deb.nodesource.com/node_24.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
                pi@raspberrypi:~ $
                
                
                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • M marcelinho

                  @marc-berg danke vielmals, hat geklappt.
                  Jetzt habe ich alles konfiguriert :) Nur noch eine "Fehlermeldung" ist die zu vernachlässigen?

                  pi@raspberrypi:~ $ sudo apt update
                  Hit:1 http://deb.debian.org/debian trixie InRelease
                  Hit:2 http://deb.debian.org/debian trixie-updates InRelease
                  Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
                  Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
                  Hit:5 https://repos.influxdata.com/debian stable InRelease
                  Hit:6 https://apt.grafana.com stable InRelease
                  Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                  Fetched 43.4 kB in 0s (88.8 kB/s)
                  All packages are up to date.
                  Warning: https://deb.nodesource.com/node_24.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
                  pi@raspberrypi:~ $
                  
                  
                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #71

                  @marcelinho

                  Ja, für den Moment vernachlässigen.
                  In nächster Zeit müssten aber die Schlüssel für das nodesource Repo aktualisiert werden.
                  Die sind aber noch nicht verfügbar.

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  1 Antwort Letzte Antwort
                  0
                  • M marcelinho

                    @crunchip ich weis nicht genau was du meinst. Ich hatte Mosquitto wohl nur für Testzwecke installiert (damals nur Benutzer und Passwort aufgeschrieben) mqtt Adapter ist auf Server mit 0.0.0.0:1885 eingestellt gewesen. Der Z2M war auf Websocket. Da ich mir meine alte Karte Debian 12 wohl mit Trixie upgrade zerschossen hab und nicht mehr per SSH drauf komme kann ich leider nicht mehr schauen welcher Port Mosquitto war. Die alte Karte geht noch, aber per SSH leider nicht mehr. Ich würde ungern alle meine Geräte neu einbinden müssen. Obwohl ich denke das ich seit 1 Woche schon versuche Yaml, mqtt und z2m anzupassen es schon längst erledigt wäre. Ich versteh glaube ich das ganze Konstrukt nicht wirklich. Wer mit wem kommuniziert und wer was genau braucht. Wenn ich es schaffe die Adapter grün zu bekommen dann bekomme ich nicht die Geräte rein durch das Backup. Irgendwie dreh ich mich leider im Kreis...

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

                    @marcelinho

                    na was heisst den wer mit wem kommuniziert..

                    z2m braucht ein mqtt .punkt.,. obs der mosquitto oder der iobroker mqtt server.. oder den startet das z2m nicht
                    der Adapter z2m hingegen braucht z2m um zu starten. diesen kann st du per WS = websocket oder so dass dieser auf den externen mqtt server horcht einstellen

                    ODER

                    du macht per mit diesem adapter einen mqtt server auf.. das gaht auch.. dann musst du z2m auf diesenauch konfigurieren

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

                    1 Antwort Letzte Antwort
                    2
                    • M Offline
                      M Offline
                      marcelinho
                      schrieb am zuletzt editiert von
                      #73

                      Guten Morgen zusammen, ist die Meldung kritisch?

                      pi@raspberrypi:~ $ sudo apt update
                      Hit:1 http://deb.debian.org/debian trixie InRelease
                      Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
                      Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
                      Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.8 kB]
                      Hit:5 https://repos.influxdata.com/debian stable InRelease
                      Hit:6 https://deb.nodesource.com/node_24.x nodistro InRelease
                      Get:7 https://apt.grafana.com stable InRelease [7,660 B]
                      Get:8 http://deb.debian.org/debian-security trixie-security/main armhf Packages                              [93.0 kB]
                      Get:9 http://archive.raspberrypi.com/debian trixie/main arm64 Packages [376 kB]
                      Err:6 https://deb.nodesource.com/node_24.x nodistro InRelease
                        Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing                              key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No bin                             ding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non-revoc                             ation signature (PositiveCertification) requiring second pre-image resistance                                because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                      Get:10 http://deb.debian.org/debian-security trixie-security/main arm64 Packages                              [99.0 kB]
                      Get:11 https://apt.grafana.com stable/main arm64 Packages [421 kB]
                      Get:12 http://deb.debian.org/debian-security trixie-security/main Translation-en                              [63.2 kB]
                      Get:13 http://archive.raspberrypi.com/debian trixie/main armhf Packages [371 kB]
                      Get:14 https://apt.grafana.com stable/main armhf Packages [491 kB]
                      Fetched 2,067 kB in 2s (1,108 kB/s)
                      10 packages can be upgraded. Run 'apt list --upgradable' to see them.
                      Warning: An error occurred during the signature verification. The repository is                              not updated and the previous index files will be used. OpenPGP signature verific                             ation failed: https://deb.nodesource.com/node_24.x nodistro InRelease: Sub-proce                             ss /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F7                             1F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signat                             ure at time 2026-01-19T15:30:12Z   because: Policy rejected non-revocation signa                             ture (PositiveCertification) requiring second pre-image resistance   because: SH                             A1 is not considered secure since 2026-02-01T00:00:00Z
                      Warning: Failed to fetch https://deb.nodesource.com/node_24.x/dists/nodistro/InR                             elease  Sub-process /usr/bin/sqv returned an error code (1), error message is: S                             igning key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:                                         No binding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non                             -revocation signature (PositiveCertification) requiring second pre-image resista                             nce   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                      Warning: Some index files failed to download. They have been ignored, or old one                             s used instead.
                      pi@raspberrypi:~ $ sudo apt upgrade
                      Upgrading:
                        grafana   libc-dev-bin  libc6      libssl3t64  openssl
                        libc-bin  libc-l10n     libc6-dev  locales     openssl-provider-legacy
                      
                      Summary:
                        Upgrading: 10, Installing: 0, Removing: 0, Not Upgrading: 0
                        Download size: 204 MB
                        Space needed: 872 kB / 19.0 GB available
                      
                      Continue? [Y/n] y
                      Get:1 http://deb.debian.org/debian-security trixie-security/main arm64 openssl-p                             rovider-legacy arm64 3.5.4-1~deb13u2 [307 kB]
                      Get:2 http://archive.raspberrypi.com/debian trixie/main arm64 libc6-dev arm64 2.                             41-12+rpt1+deb13u1 [2,353 kB]
                      Get:3 http://deb.debian.org/debian-security trixie-security/main arm64 libssl3t6                             4 arm64 3.5.4-1~deb13u2 [2,750 kB]
                      Get:4 https://apt.grafana.com stable/main arm64 grafana arm64 12.3.2 [185 MB]
                      Get:5 http://archive.raspberrypi.com/debian trixie/main arm64 libc-dev-bin arm64                              2.41-12+rpt1+deb13u1 [62.1 kB]
                      Get:6 http://archive.raspberrypi.com/debian trixie/main arm64 libc6 arm64 2.41-1                             2+rpt1+deb13u1 [5,184 kB]
                      Get:7 http://archive.raspberrypi.com/debian trixie/main arm64 libc-bin arm64 2.4                             1-12+rpt1+deb13u1 [765 kB]
                      Get:8 http://archive.raspberrypi.com/debian trixie/main arm64 libc-l10n all 2.41                             -12+rpt1+deb13u1 [1,654 kB]
                      Get:9 http://archive.raspberrypi.com/debian trixie/main arm64 locales all 2.41-1                             2+rpt1+deb13u1 [5,108 kB]
                      Get:10 http://deb.debian.org/debian-security trixie-security/main arm64 openssl                              arm64 3.5.4-1~deb13u2 [1,459 kB]
                      Fetched 204 MB in 1min 58s (1,739 kB/s)
                      Reading changelogs... Done
                      Preconfiguring packages ...
                      (Reading database ... 115736 files and directories currently installed.)
                      Preparing to unpack .../libc6-dev_2.41-12+rpt1+deb13u1_arm64.deb ...
                      Unpacking libc6-dev:arm64 (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Preparing to unpack .../libc-dev-bin_2.41-12+rpt1+deb13u1_arm64.deb ...
                      Unpacking libc-dev-bin (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Preparing to unpack .../libc6_2.41-12+rpt1+deb13u1_arm64.deb ...
                      Unpacking libc6:arm64 (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Setting up libc6:arm64 (2.41-12+rpt1+deb13u1) ...
                      (Reading database ... 115736 files and directories currently installed.)
                      Preparing to unpack .../libc-bin_2.41-12+rpt1+deb13u1_arm64.deb ...
                      Unpacking libc-bin (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Setting up libc-bin (2.41-12+rpt1+deb13u1) ...
                      (Reading database ... 115736 files and directories currently installed.)
                      Preparing to unpack .../openssl-provider-legacy_3.5.4-1~deb13u2_arm64.deb ...
                      Unpacking openssl-provider-legacy (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1)                              ...
                      Setting up openssl-provider-legacy (3.5.4-1~deb13u2) ...
                      (Reading database ... 115736 files and directories currently installed.)
                      Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_arm64.deb ...
                      Unpacking libssl3t64:arm64 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1) ...
                      Setting up libssl3t64:arm64 (3.5.4-1~deb13u2) ...
                      (Reading database ... 115736 files and directories currently installed.)
                      Preparing to unpack .../libc-l10n_2.41-12+rpt1+deb13u1_all.deb ...
                      Unpacking libc-l10n (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Preparing to unpack .../locales_2.41-12+rpt1+deb13u1_all.deb ...
                      Unpacking locales (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                      Preparing to unpack .../grafana_12.3.2_arm64.deb ...
                      Unpacking grafana (12.3.2) over (12.3.1) ...
                      Preparing to unpack .../openssl_3.5.4-1~deb13u2_arm64.deb ...
                      Unpacking openssl (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1) ...
                      Setting up libc-l10n (2.41-12+rpt1+deb13u1) ...
                      Setting up locales (2.41-12+rpt1+deb13u1) ...
                      Generating locales (this might take a while)...
                        en_GB.UTF-8... done
                      Generation complete.
                      Setting up libc-dev-bin (2.41-12+rpt1+deb13u1) ...
                      Setting up openssl (3.5.4-1~deb13u2) ...
                      Setting up grafana (12.3.2) ...
                      Restarting grafana-server service... OK
                      Setting up libc6-dev:arm64 (2.41-12+rpt1+deb13u1) ...
                      Processing triggers for systemd (257.9-1~deb13u1) ...
                      Processing triggers for man-db (2.13.1-1) ...
                      Processing triggers for libc-bin (2.41-12+rpt1+deb13u1) ...
                      pi@raspberrypi:~ $ sudo apt update
                      Hit:1 http://deb.debian.org/debian trixie InRelease
                      Hit:2 http://deb.debian.org/debian trixie-updates InRelease
                      Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
                      Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
                      Hit:5 https://repos.influxdata.com/debian stable InRelease
                      Hit:6 https://apt.grafana.com stable InRelease
                      Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                      Err:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                        Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing                              key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No bin                             ding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non-revoc                             ation signature (PositiveCertification) requiring second pre-image resistance                                because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                      All packages are up to date.
                      Warning: An error occurred during the signature verification. The repository is                              not updated and the previous index files will be used. OpenPGP signature verific                             ation failed: https://deb.nodesource.com/node_24.x nodistro InRelease: Sub-proce                             ss /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F7                             1F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signat                             ure at time 2026-01-19T15:30:12Z   because: Policy rejected non-revocation signa                             ture (PositiveCertification) requiring second pre-image resistance   because: SH                             A1 is not considered secure since 2026-02-01T00:00:00Z
                      Warning: Failed to fetch https://deb.nodesource.com/node_24.x/dists/nodistro/InR                             elease  Sub-process /usr/bin/sqv returned an error code (1), error message is: S                             igning key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:                                         No binding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non                             -revocation signature (PositiveCertification) requiring second pre-image resista                             nce   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                      Warning: Some index files failed to download. They have been ignored, or old one                             s used instead.
                      pi@raspberrypi:~ $
                      
                      
                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • M marcelinho

                        Guten Morgen zusammen, ist die Meldung kritisch?

                        pi@raspberrypi:~ $ sudo apt update
                        Hit:1 http://deb.debian.org/debian trixie InRelease
                        Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
                        Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
                        Get:4 http://archive.raspberrypi.com/debian trixie InRelease [54.8 kB]
                        Hit:5 https://repos.influxdata.com/debian stable InRelease
                        Hit:6 https://deb.nodesource.com/node_24.x nodistro InRelease
                        Get:7 https://apt.grafana.com stable InRelease [7,660 B]
                        Get:8 http://deb.debian.org/debian-security trixie-security/main armhf Packages                              [93.0 kB]
                        Get:9 http://archive.raspberrypi.com/debian trixie/main arm64 Packages [376 kB]
                        Err:6 https://deb.nodesource.com/node_24.x nodistro InRelease
                          Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing                              key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No bin                             ding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non-revoc                             ation signature (PositiveCertification) requiring second pre-image resistance                                because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                        Get:10 http://deb.debian.org/debian-security trixie-security/main arm64 Packages                              [99.0 kB]
                        Get:11 https://apt.grafana.com stable/main arm64 Packages [421 kB]
                        Get:12 http://deb.debian.org/debian-security trixie-security/main Translation-en                              [63.2 kB]
                        Get:13 http://archive.raspberrypi.com/debian trixie/main armhf Packages [371 kB]
                        Get:14 https://apt.grafana.com stable/main armhf Packages [491 kB]
                        Fetched 2,067 kB in 2s (1,108 kB/s)
                        10 packages can be upgraded. Run 'apt list --upgradable' to see them.
                        Warning: An error occurred during the signature verification. The repository is                              not updated and the previous index files will be used. OpenPGP signature verific                             ation failed: https://deb.nodesource.com/node_24.x nodistro InRelease: Sub-proce                             ss /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F7                             1F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signat                             ure at time 2026-01-19T15:30:12Z   because: Policy rejected non-revocation signa                             ture (PositiveCertification) requiring second pre-image resistance   because: SH                             A1 is not considered secure since 2026-02-01T00:00:00Z
                        Warning: Failed to fetch https://deb.nodesource.com/node_24.x/dists/nodistro/InR                             elease  Sub-process /usr/bin/sqv returned an error code (1), error message is: S                             igning key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:                                         No binding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non                             -revocation signature (PositiveCertification) requiring second pre-image resista                             nce   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                        Warning: Some index files failed to download. They have been ignored, or old one                             s used instead.
                        pi@raspberrypi:~ $ sudo apt upgrade
                        Upgrading:
                          grafana   libc-dev-bin  libc6      libssl3t64  openssl
                          libc-bin  libc-l10n     libc6-dev  locales     openssl-provider-legacy
                        
                        Summary:
                          Upgrading: 10, Installing: 0, Removing: 0, Not Upgrading: 0
                          Download size: 204 MB
                          Space needed: 872 kB / 19.0 GB available
                        
                        Continue? [Y/n] y
                        Get:1 http://deb.debian.org/debian-security trixie-security/main arm64 openssl-p                             rovider-legacy arm64 3.5.4-1~deb13u2 [307 kB]
                        Get:2 http://archive.raspberrypi.com/debian trixie/main arm64 libc6-dev arm64 2.                             41-12+rpt1+deb13u1 [2,353 kB]
                        Get:3 http://deb.debian.org/debian-security trixie-security/main arm64 libssl3t6                             4 arm64 3.5.4-1~deb13u2 [2,750 kB]
                        Get:4 https://apt.grafana.com stable/main arm64 grafana arm64 12.3.2 [185 MB]
                        Get:5 http://archive.raspberrypi.com/debian trixie/main arm64 libc-dev-bin arm64                              2.41-12+rpt1+deb13u1 [62.1 kB]
                        Get:6 http://archive.raspberrypi.com/debian trixie/main arm64 libc6 arm64 2.41-1                             2+rpt1+deb13u1 [5,184 kB]
                        Get:7 http://archive.raspberrypi.com/debian trixie/main arm64 libc-bin arm64 2.4                             1-12+rpt1+deb13u1 [765 kB]
                        Get:8 http://archive.raspberrypi.com/debian trixie/main arm64 libc-l10n all 2.41                             -12+rpt1+deb13u1 [1,654 kB]
                        Get:9 http://archive.raspberrypi.com/debian trixie/main arm64 locales all 2.41-1                             2+rpt1+deb13u1 [5,108 kB]
                        Get:10 http://deb.debian.org/debian-security trixie-security/main arm64 openssl                              arm64 3.5.4-1~deb13u2 [1,459 kB]
                        Fetched 204 MB in 1min 58s (1,739 kB/s)
                        Reading changelogs... Done
                        Preconfiguring packages ...
                        (Reading database ... 115736 files and directories currently installed.)
                        Preparing to unpack .../libc6-dev_2.41-12+rpt1+deb13u1_arm64.deb ...
                        Unpacking libc6-dev:arm64 (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Preparing to unpack .../libc-dev-bin_2.41-12+rpt1+deb13u1_arm64.deb ...
                        Unpacking libc-dev-bin (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Preparing to unpack .../libc6_2.41-12+rpt1+deb13u1_arm64.deb ...
                        Unpacking libc6:arm64 (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Setting up libc6:arm64 (2.41-12+rpt1+deb13u1) ...
                        (Reading database ... 115736 files and directories currently installed.)
                        Preparing to unpack .../libc-bin_2.41-12+rpt1+deb13u1_arm64.deb ...
                        Unpacking libc-bin (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Setting up libc-bin (2.41-12+rpt1+deb13u1) ...
                        (Reading database ... 115736 files and directories currently installed.)
                        Preparing to unpack .../openssl-provider-legacy_3.5.4-1~deb13u2_arm64.deb ...
                        Unpacking openssl-provider-legacy (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1)                              ...
                        Setting up openssl-provider-legacy (3.5.4-1~deb13u2) ...
                        (Reading database ... 115736 files and directories currently installed.)
                        Preparing to unpack .../libssl3t64_3.5.4-1~deb13u2_arm64.deb ...
                        Unpacking libssl3t64:arm64 (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1) ...
                        Setting up libssl3t64:arm64 (3.5.4-1~deb13u2) ...
                        (Reading database ... 115736 files and directories currently installed.)
                        Preparing to unpack .../libc-l10n_2.41-12+rpt1+deb13u1_all.deb ...
                        Unpacking libc-l10n (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Preparing to unpack .../locales_2.41-12+rpt1+deb13u1_all.deb ...
                        Unpacking locales (2.41-12+rpt1+deb13u1) over (2.41-12+rpt1) ...
                        Preparing to unpack .../grafana_12.3.2_arm64.deb ...
                        Unpacking grafana (12.3.2) over (12.3.1) ...
                        Preparing to unpack .../openssl_3.5.4-1~deb13u2_arm64.deb ...
                        Unpacking openssl (3.5.4-1~deb13u2) over (3.5.4-1~deb13u1+rpt1) ...
                        Setting up libc-l10n (2.41-12+rpt1+deb13u1) ...
                        Setting up locales (2.41-12+rpt1+deb13u1) ...
                        Generating locales (this might take a while)...
                          en_GB.UTF-8... done
                        Generation complete.
                        Setting up libc-dev-bin (2.41-12+rpt1+deb13u1) ...
                        Setting up openssl (3.5.4-1~deb13u2) ...
                        Setting up grafana (12.3.2) ...
                        Restarting grafana-server service... OK
                        Setting up libc6-dev:arm64 (2.41-12+rpt1+deb13u1) ...
                        Processing triggers for systemd (257.9-1~deb13u1) ...
                        Processing triggers for man-db (2.13.1-1) ...
                        Processing triggers for libc-bin (2.41-12+rpt1+deb13u1) ...
                        pi@raspberrypi:~ $ sudo apt update
                        Hit:1 http://deb.debian.org/debian trixie InRelease
                        Hit:2 http://deb.debian.org/debian trixie-updates InRelease
                        Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
                        Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
                        Hit:5 https://repos.influxdata.com/debian stable InRelease
                        Hit:6 https://apt.grafana.com stable InRelease
                        Hit:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                        Err:7 https://deb.nodesource.com/node_24.x nodistro InRelease
                          Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing                              key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No bin                             ding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non-revoc                             ation signature (PositiveCertification) requiring second pre-image resistance                                because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                        All packages are up to date.
                        Warning: An error occurred during the signature verification. The repository is                              not updated and the previous index files will be used. OpenPGP signature verific                             ation failed: https://deb.nodesource.com/node_24.x nodistro InRelease: Sub-proce                             ss /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F7                             1F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signat                             ure at time 2026-01-19T15:30:12Z   because: Policy rejected non-revocation signa                             ture (PositiveCertification) requiring second pre-image resistance   because: SH                             A1 is not considered secure since 2026-02-01T00:00:00Z
                        Warning: Failed to fetch https://deb.nodesource.com/node_24.x/dists/nodistro/InR                             elease  Sub-process /usr/bin/sqv returned an error code (1), error message is: S                             igning key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:                                         No binding signature at time 2026-01-19T15:30:12Z   because: Policy rejected non                             -revocation signature (PositiveCertification) requiring second pre-image resista                             nce   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
                        Warning: Some index files failed to download. They have been ignored, or old one                             s used instead.
                        pi@raspberrypi:~ $
                        
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von Thomas Braun
                        #74

                        @marcelinho

                        Ja, der aktuelle Schlüssel fehlt.
                        Installier da wieder nodejs@22:

                        iob nodejs-update
                        

                        Rückfragen des Skripts mit y beantworten.

                        Siehe auch:

                        https://forum.iobroker.net/topic/83744/nodesource-repo-openpgp-signature-verification-failed

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        • M Offline
                          M Offline
                          marcelinho
                          schrieb am zuletzt editiert von
                          #75

                          @thomas-braun lieben Dank, hat geklappt. Schönen Sonntag noch.

                          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
                          FAQ Cloud / IOT
                          HowTo: Node.js-Update
                          HowTo: Backup/Restore
                          Downloads
                          BLOG

                          350

                          Online

                          32.6k

                          Benutzer

                          82.2k

                          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