Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Innogy Adapter im lokalen Netzt bleibt Gelb

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Innogy Adapter im lokalen Netzt bleibt Gelb

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      scout1978 @Thomas Braun last edited by

      @thomas-braun
      Ja Entschuldigung. Möchtest Du das Ergebnis aus der Konsole? Was sind CodeTags?

      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @scout1978 last edited by

        @scout1978 sagte in Innogy Adapter im lokalen Netzt bleibt Gelb:

        Möchtest Du das Ergebnis aus der Konsole? Was sind CodeTags?

        Ja. CodeTags:
        42b5b5af-6423-4f3a-973a-e57612666ae5-grafik.png

        Text zwischen die Steuerzeichen kopieren.

        S 1 Reply Last reply Reply Quote 0
        • S
          scout1978 @Thomas Braun last edited by Homoran

          @thomas-braun

          uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v                                       && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update &&                                       apt policy nodejs
          aarch64
          /usr/bin/nodejs
          /usr/bin/node
          /usr/bin/npm
          v16.17.0
          v16.17.0
          8.15.0
          4.0.23
          pi
          pi adm dialout cdrom sudo audio video plugdev games users input render netdev gp                                      io i2c spi iobroker
          /home/pi
          Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
          Hit:3 https://phoscon.de/apt/deconz bullseye InRelease
          Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
          Hit:5 https://repos.influxdata.com/debian bullseye InRelease
          Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
          Hit:7 https://packages.grafana.com/oss/deb stable InRelease
          Reading package lists... Done
          Building dependency tree... Done
          Reading state information... Done
          13 packages can be upgraded. Run 'apt list --upgradable' to see them.
          W: Target Packages (main/binary-arm64/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      2
          W: Target Packages (main/binary-armhf/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      2
          W: Target Packages (main/binary-all/Packages) is configured multiple times in /e                                      tc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
          W: Target Translations (main/i18n/Translation-en_GB) is configured multiple time                                      s in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.                                      list:2
          W: Target Translations (main/i18n/Translation-en) is configured multiple times i                                      n /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.lis                                      t:2
          W: Target Packages (main/binary-arm64/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      3
          W: Target Packages (main/binary-armhf/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      3
          W: Target Packages (main/binary-all/Packages) is configured multiple times in /e                                      tc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:3
          W: Target Translations (main/i18n/Translation-en_GB) is configured multiple time                                      s in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.                                      list:3
          W: Target Translations (main/i18n/Translation-en) is configured multiple times i                                      n /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.lis                                      t:3
          W: Target Packages (main/binary-arm64/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      2
          W: Target Packages (main/binary-armhf/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      2
          W: Target Packages (main/binary-all/Packages) is configured multiple times in /e                                      tc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:2
          W: Target Translations (main/i18n/Translation-en_GB) is configured multiple time                                      s in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.                                      list:2
          W: Target Translations (main/i18n/Translation-en) is configured multiple times i                                      n /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.lis                                      t:2
          W: Target Packages (main/binary-arm64/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      3
          W: Target Packages (main/binary-armhf/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      3
          W: Target Packages (main/binary-all/Packages) is configured multiple times in /e                                      tc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:3
          W: Target Translations (main/i18n/Translation-en_GB) is configured multiple time                                      s in /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.                                      list:3
          W: Target Translations (main/i18n/Translation-en) is configured multiple times i                                      n /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.lis                                      t:3
          nodejs:
           Installed: 16.17.0-deb-1nodesource1
           Candidate: 16.17.1-deb-1nodesource1
           Version table:
              16.17.1-deb-1nodesource1 500
                 500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
          *** 16.17.0-deb-1nodesource1 100
                 100 /var/lib/dpkg/status
              12.22.12~dfsg-1~deb11u1 500
                 500 http://security.debian.org/debian-security bullseye-security/main ar                                      m64 Packages
          pi@raspberrypi-Iobroker:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v                                       && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update &&                                       apt policy nodejs
          aarch64
          /usr/bin/nodejs
          /usr/bin/node
          /usr/bin/npm
          v16.17.0
          v16.17.0
          8.15.0
          4.0.23
          pi
          pi adm dialout cdrom sudo audio video plugdev games users input render netdev gp                                      io i2c spi iobroker
          /home/pi
          Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
          Hit:3 https://phoscon.de/apt/deconz bullseye InRelease
          Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
          Hit:5 https://repos.influxdata.com/debian bullseye InRelease
          Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
          Hit:7 https://packages.grafana.com/oss/deb stable InRelease
          Reading package lists... Done
          Building dependency tree... Done
          Reading state information... Done
          13 packages can be upgraded. Run 'apt list --upgradable' to see them.
          W: Target Packages (main/binary-arm64/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      2
          W: Target Packages (main/binary-armhf/Packages) is configured multiple times in                                       /etc/apt/sources.list.d/grafana.list:1 and /etc/apt/sources.list.d/grafana.list:                                      ^C@raspberrypi-Iobroker:~ $.debian.org/debian-security bullseye-security/main ar
          pi@raspberrypi-Iobroker:~ $
          
          
          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @scout1978 last edited by Thomas Braun

            @scout1978 sagte in Innogy Adapter im lokalen Netzt bleibt Gelb:

            OT, aber lösch die Doublette in der Datei /etc/apt/sources.list.d/grafana.list

            3e3957d5-5884-4dfa-b9fd-6ca27262f41b-grafik.png ```

            S 1 Reply Last reply Reply Quote 0
            • S
              scout1978 @Thomas Braun last edited by

              @thomas-braun
              Muss die Doublette gleich raus? Das wird dann für mich nämlich schon die nächte Baustelle. Bin da nicht so ganz firm.Brauchst du den Code nochmals in den Klammern?

              Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @scout1978 last edited by

                @scout1978

                Lösch die Zeile halt einfach raus.
                Mit nano z.B.

                sudo nano  /etc/apt/sources.list.d/grafana.list
                
                S 1 Reply Last reply Reply Quote 0
                • S
                  scout1978 @Thomas Braun last edited by

                  @thomas-braun said in Innogy Adapter im lokalen Netzt bleibt Gelb:

                  sudo nano /etc/apt/sources.list.d/grafana.list

                  ok hat geklappt

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @scout1978 last edited by

                    @scout1978

                    Dann patch jetzt dein System durch, inkl. upgrade von nodejs.

                    iob stop
                    sudo apt update
                    sudo apt full-upgrade
                    sudo reboot
                    
                    1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @scout1978 last edited by Homoran

                      @scout1978 sagte in Innogy Adapter im lokalen Netzt bleibt Gelb:

                      Brauchst du den Code nochmals in den Klammern?

                      der "Fehler" war nach dem @Thomas-Braun keine neue Zeile für di code-tags zu nehmen. hab ich gerade korrigiert

                      1 Reply Last reply Reply Quote 0
                      • S
                        scout1978 last edited by

                        @thomas-braun
                        Jetzt hab ich ausversehen node Js v18.11.0 erwischt, muss erst wieder zurück finden

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @scout1978 last edited by Thomas Braun

                          @scout1978
                          Wer hat denn IRGENDWAS von nodejs18 geschrieben?
                          Das ist in deinen Quellen überhaupt nicht aktiv gewesen, das KANNST du gar nicht 'erwischen'.

                          Du solltest NUR die vier Zeilen abarbeiten. Dann wäre die aktuelle Version von node16 eingespielt worden.

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            scout1978 @Thomas Braun last edited by

                            @thomas-braun
                            alles erledigt node Js aktuell und die 4 Zeilen abgearbeitet

                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @scout1978 last edited by Thomas Braun

                              @scout1978

                              Nix nacherzählen, Fakten liefern:

                              
                              uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                              
                              S 1 Reply Last reply Reply Quote 0
                              • S
                                scout1978 @Thomas Braun last edited by

                                @thomas-braun

                                :~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                aarch64
                                /usr/bin/nodejs
                                /usr/local/bin/node
                                /usr/local/bin/npm
                                v18.11.0
                                v16.18.0
                                8.19.2
                                4.0.23
                                pi
                                pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
                                /home/pi
                                Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
                                Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
                                Hit:3 https://repos.influxdata.com/debian bullseye InRelease
                                Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
                                Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
                                Hit:6 https://phoscon.de/apt/deconz bullseye InRelease
                                Hit:7 https://packages.grafana.com/oss/deb stable InRelease
                                Reading package lists... Done
                                Building dependency tree... Done
                                Reading state information... Done
                                All packages are up to date.
                                nodejs:
                                  Installed: 18.11.0-deb-1nodesource1
                                  Candidate: 18.11.0-deb-1nodesource1
                                  Version table:
                                 *** 18.11.0-deb-1nodesource1 100
                                        100 /var/lib/dpkg/status
                                     16.17.1-deb-1nodesource1 500
                                        500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages
                                     12.22.12~dfsg-1~deb11u1 500
                                        500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
                                pi@raspberrypi-Iobroker:~ $ :~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                aarch64
                                /usr/bin/nodejs
                                /usr/local/bin/node
                                /usr/local/bin/npm
                                v18.11.0
                                v16.18.0
                                8.19.2
                                4.0.23
                                pi
                                pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
                                /home/pi
                                Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
                                Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
                                Hit:3 https://repos.influxdata.com/debian bullseye InRelease
                                Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
                                Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
                                Hit:6 https://phoscon.de/apt/deconz bullseye InRelease
                                Hit:7 https://packages.grafana.com/oss/deb stable InRelease
                                Reading package lists... Done
                                Building dependency tree... Done
                                pi@raspberrypi-Iobroker:~ $.debian.org/debian-security bullseye-
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @scout1978 last edited by

                                  @scout1978

                                  Kannst du mir mal sagen wie du jetzt node18.11.0 und 16.18.0 'installiert' hast?

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    scout1978 last edited by

                                    @thomas-braun
                                    nein

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @scout1978 last edited by

                                      @scout1978

                                      Warum nicht? Ist doch erst wenige Minuten her.

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        scout1978 @Thomas Braun last edited by

                                        @thomas-braun
                                        So lieber Thomas wie du wohl festgestellt hast bin ich kein Profi, und hangel mich hier irgendwie durch.
                                        Vielen Dank für Deine Hilfe aber ich glaube auf die Art komme ich hier nicht weiter.

                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @scout1978 last edited by

                                          @scout1978

                                          Wie bist du denn zu den beiden Versionen gehangelt?
                                          Irgendeine Anleitung befolgt? Welche? Von alleine kommt der Kram ja nicht auf dein System.

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            scout1978 @Thomas Braun last edited by

                                            @thomas-braun
                                            Habe wie im Iobroker Masterkurs das update gemacht und die falsche Version eingegeben.Danach nach einem Youtube Video versucht das wieder zu ändern.

                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            455
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            118
                                            8159
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo