Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter rpi2 2.x

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    Test Adapter rpi2 2.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • Moppedman
      Moppedman @Garfonso last edited by

      @garfonso Erst man vielen Dank das du das Startverhalten anpassen willst. Wenn du das fertig hast teste ich das gerne für dich. Einfach nur melden

      Hinsichtlich des Freischalten verstehe ich jetzt, das weder im alten noch im neunen Adapter die Ausgänge zurückgeschaltet werden.

      Kann es sein das im Betriebssystem für die GPIOs dieses Verhalten hinterlegt ist. Wenn ich das richtig gelesen habe wurden die GPIO von der Pi Foundation völlig neu aufgesetzt.

      Garfonso 2 Replies Last reply Reply Quote 0
      • S
        searcher57 @Garfonso last edited by

        @garfonso
        Hallo,
        was ist denn jetzt los? Auf einmal funktioniert der Gaszähler nicht mehr.
        Deinen Hinweis habe ich durchgeführt.

         sudo apt install libgpiod-dev
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
libgpiod-dev ist schon die neueste Version (1.6.3-1+b3).
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  linux-headers-6.6.47+rpt-common-rpi linux-kbuild-6.6.47+rpt
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

        Trotzdem kommen folgende Fehlermeldungen auf meinem Raspi 5:

        v7.1.5
13

Log-Größe: 135.0 KB
Zeit
	
rpi2.0
	2024-12-22 13:58:12.326	warn	If the library is installed and npm list | grep opengpio shows the npm library is also installed, please report this issue to the adapter developer with the model of your device and deboug output from an adapter start.
rpi2.0
	2024-12-22 13:58:12.326	warn	Please make sure that libgpiod-dev (on raspian/debian run sudo apt install libgpiod-dev) is installed in the system and then reinstall the adapter.
rpi2.0
	2024-12-22 13:58:12.325	warn	Cannot initialize GPIO: No chip found. GPIO functionality disabled!
rpi2.0
	2024-12-22 13:58:12.090	info	starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.18.1, js-controller: 7.0.3

        Hast Du vielleicht eine Erklärung? Bis gestern hat alles funktioniert, wie es soll.

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

          @searcher57

          sudo apt update
apt policy libgpiod*

          sagt? Und hast du den Adapter reinstalliert?
          Mal in

          raspi-config

          nach gpio geschaut?

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

            @thomas-braun said in Test Adapter rpi2 2.x:

            raspi-config

            So ich habe in der config I8 Remote GPIO Enable/disable remote access to GPIO pins aktiviert. Oder ist das falsch?

            @thomas-braun said in Test Adapter rpi2 2.x:

            @searcher57

            sudo apt update
apt policy libgpiod*

            sagt? Und hast du den Adapter reinstalliert?
            Mal in

            raspi-config

            nach gpio geschaut?

            Also ich habe GPIO aktiviert, oder war das falsch?

            Hier die Ausgabe:

            sudo apt update
apt policy libgpiod*
OK:1 http://deb.debian.org/debian bookworm InRelease
OK:2 http://deb.debian.org/debian-security bookworm-security InRelease
Holen:3 http://deb.debian.org/debian bookworm-updates InRelease [55,4 kB]
OK:4 http://archive.raspberrypi.com/debian bookworm InRelease
OK:5 https://repos.influxdata.com/debian stable InRelease
OK:6 https://deb.nodesource.com/node_20.x nodistro InRelease
OK:7 https://repo.mosquitto.org/debian bookworm InRelease
Es wurden 55,4 kB in 1 s geholt (85,0 kB/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
libgpiod-dev:
  Installiert:           1.6.3-1+b3
  Installationskandidat: 1.6.3-1+b3
  Versionstabelle:
 *** 1.6.3-1+b3 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        100 /var/lib/dpkg/status
libgpiod-doc:
  Installiert:           (keine)
  Installationskandidat: 1.6.3-1
  Versionstabelle:
     1.6.3-1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        500 http://deb.debian.org/debian bookworm/main armhf Packages
libgpiod2:
  Installiert:           1.6.3-1+b3
  Installationskandidat: 1.6.3-1+b3
  Versionstabelle:
 *** 1.6.3-1+b3 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        100 /var/lib/dpkg/status
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @searcher57 last edited by

              @searcher57 sagte in Test Adapter rpi2 2.x:

              Also ich habe GPIO aktiviert, oder war das falsch?

              Nein, das passt.

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

                @thomas-braun said in Test Adapter rpi2 2.x:

                @searcher57 sagte in Test Adapter rpi2 2.x:

                Also ich habe GPIO aktiviert, oder war das falsch?

                Nein, das passt.

                Bis jetzt kein Erfolg. In der Config habe ich vorher nie etwas eingestellt.

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

                  @searcher57
                  Und was verrät

                  cd /opt/iobroker/ && npm ls opengpio

                  Adapter nochmal drüber installiert?

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

                    @thomas-braun said in Test Adapter rpi2 2.x:

                    @searcher57
                    Und was verrät

                    cd /opt/iobroker/ && npm ls opengpio

                    pi@Raspi58GB:~ $ cd /opt/iobroker/ && npm ls opengpio
iobroker.inst@3.0.0 /opt/iobroker
└─┬ iobroker.rpi2@2.2.2
  └── opengpio@1.0.17

pi@Raspi58GB:/opt/iobroker $

                    Adapter gerade neu installiert, ohne Erfolg!

                    S Homoran 2 Replies Last reply Reply Quote 0
                    • S
                      searcher57 @searcher57 last edited by

                      @searcher57 said in Test Adapter rpi2 2.x:

                      @thomas-braun said in Test Adapter rpi2 2.x:

                      @searcher57
                      Und was verrät

                      cd /opt/iobroker/ && npm ls opengpio

                      pi@Raspi58GB:~ $ cd /opt/iobroker/ && npm ls opengpio
iobroker.inst@3.0.0 /opt/iobroker
└─┬ iobroker.rpi2@2.2.2
  └── opengpio@1.0.17

pi@Raspi58GB:/opt/iobroker $

                      Adapter gerade neu installiert, ohne Erfolg!

                      Hier nochmal das Protokoll:

                      pi2.0
	2024-12-22 16:20:54.990	warn	If the library is installed and npm list | grep opengpio shows the npm library is also installed, please report this issue to the adapter developer with the model of your device and deboug output from an adapter start.
rpi2.0
	2024-12-22 16:20:54.990	warn	Please make sure that libgpiod-dev (on raspian/debian run sudo apt install libgpiod-dev) is installed in the system and then reinstall the adapter.
rpi2.0
	2024-12-22 16:20:54.989	warn	Cannot initialize GPIO: No chip found. GPIO functionality disabled!
rpi2.0
	2024-12-22 16:20:54.675	info	starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.18.1, js-controller: 7.0.3
rpi2.0
	2024-12-22 16:20:50.340	info	terminating
rpi2.0
	2024-12-22 16:20:49.841	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
rpi2.0
	2024-12-22 16:20:49.840	info	terminating
rpi2.0
	2024-12-22 16:20:49.839	info	Got terminate signal TERMINATE_YOURSELF
rpi2.0
	2024-12-22 16:19:27.683	info	GPIO ports are not configured
rpi2.0
	2024-12-22 16:19:26.628	info	starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.18.1, js-controller: 7.0.3
rpi2.0
	2024-12-22 16:16:33.859	info	terminating
rpi2.0
	2024-12-22 16:16:33.359	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
rpi2.0
	2024-12-22 16:16:33.359	info	terminating
rpi2.0
	2024-12-22 16:16:33.358	info	Got terminate signal TERMINATE_YOURSELF
rpi2.0
	2024-12-22 16:05:28.448	warn	If the library is installed and npm list | grep opengpio shows the npm library is also installed, please report this issue to the adapter developer with the model of your device and deboug output from an adapter start.
rpi2.0
	2024-12-22 16:05:28.448	warn	Please make sure that libgpiod-dev (on raspian/debian run sudo apt install libgpiod-dev) is installed in the system and then reinstall the adapter.
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @searcher57 last edited by

                        @searcher57 sagte in Test Adapter rpi2 2.x:

                        Adapter gerade neu installiert, ohne Erfolg!

                        bist du sicher?

                        nicht nur die Instanz neu erstellt?

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          searcher57 @Homoran last edited by

                          @homoran said in Test Adapter rpi2 2.x:

                          @searcher57 sagte in Test Adapter rpi2 2.x:

                          Adapter gerade neu installiert, ohne Erfolg!

                          bist du sicher?

                          nicht nur die Instanz neu erstellt?

                          Ja, bin mir sicher. Den Adapter gelöscht und über beta neu installiert und konfiguriert.

                          c16f4753-a4f1-426c-aee9-8ad92f566160-grafik.png

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

                            @searcher57 sagte in Test Adapter rpi2 2.x:

                            Dann bitte:

                            please report this issue to the adapter developer with the model of your device and deboug output from an adapter start

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

                              @thomas-braun said in Test Adapter rpi2 2.x:

                              @searcher57 sagte in Test Adapter rpi2 2.x:

                              Dann bitte:

                              please report this issue to the adapter developer with the model of your device and deboug output from an adapter start

                              Danke für Deine Mühe! Habe ich schon gemacht!

                              Frohe Weihnachten!!

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

                                @searcher57

                                Hier?

                                https://github.com/iobroker-community-adapters/ioBroker.rpi2/issues

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

                                  @thomas-braun said in Test Adapter rpi2 2.x:

                                  @searcher57

                                  Hier?

                                  https://github.com/iobroker-community-adapters/ioBroker.rpi2/issues

                                  Nein, mache ich!

                                  1 Reply Last reply Reply Quote 0
                                  • Garfonso
                                    Garfonso Developer @Moppedman last edited by

                                    @moppedman

                                    Gerne die 2.3.0 testen, die bald im latest / auf npm erscheinen sollte.

                                    Da habe ich es jetzt so angepasst, dass Einfach nur Ausgang gar nicht beim starten gesetzt wird und die mit Startwert entsprechend einmal beim starten gesetzt werden, egal was jeweils im state (noch) steht.

                                    Moppedman 1 Reply Last reply Reply Quote 0
                                    • Garfonso
                                      Garfonso Developer @Moppedman last edited by

                                      @moppedman said in Test Adapter rpi2 2.x:

                                      Kann es sein das im Betriebssystem für die GPIOs dieses Verhalten hinterlegt ist. Wenn ich das richtig gelesen habe wurden die GPIO von der Pi Foundation völlig neu aufgesetzt.

                                      Ja, das ist meine Vermutung, dass es daran liegt. Ich habe extra nochmal in die alte Bibliothek reingeguckt, ob die da irgendwas macht. Aber da passiert beim beenden überall nichts.

                                      Wenn das wichtig ist, könnte man das vielleicht als zusätzlichen Konfigurationsparameter beim Ausgang mit dazu geben.

                                      1 Reply Last reply Reply Quote 0
                                      • Garfonso
                                        Garfonso Developer @searcher57 last edited by

                                        @searcher57
                                        debug log steht da. Bitte mal auf debug stellen und das log von nem Adapter start einfügen. Wenn wir Glück haben steht da was drinnen.... ansonsten hab ich spontan keine Idee, was da noch schief gehen soll. 😕

                                        Frohe Weihnachten trotzdem. 🙂

                                        S 2 Replies Last reply Reply Quote 0
                                        • S
                                          searcher57 @Garfonso last edited by

                                          @garfonso said in Test Adapter rpi2 2.x:

                                          @searcher57
                                          debug log steht da. Bitte mal auf debug stellen und das log von nem Adapter start einfügen. Wenn wir Glück haben steht da was drinnen.... ansonsten hab ich spontan keine Idee, was da noch schief gehen soll. 😕

                                          Frohe Weihnachten trotzdem. 🙂

                                          Habe ich in GitHub schon gemacht, aber hier nochmal:

                                          rpi2.0
	2024-12-24 11:25:59.212	warn	If the library is installed and npm list | grep opengpio shows the npm library is also installed, please report this issue to the adapter developer with the model of your device and deboug output from an adapter start.
rpi2.0
	2024-12-24 11:25:59.212	warn	Please make sure that libgpiod-dev (on raspian/debian run sudo apt install libgpiod-dev) is installed in the system and then reinstall the adapter.
rpi2.0
	2024-12-24 11:25:59.211	warn	Cannot initialize GPIO: No chip found. GPIO functionality disabled!
rpi2.0
	2024-12-24 11:25:58.956	info	starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.18.1, js-controller: 7.0.3
rpi2.0
	2024-12-24 11:25:51.507	info	terminating
rpi2.0
	2024-12-24 11:25:51.008	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
rpi2.0
	2024-12-24 11:25:51.008	info	terminating
rpi2.0
	2024-12-24 11:25:51.006	info	Got terminate signal TERMINATE_YOURSELF

                                          Auch Dir frohe und besinnliche Weihnachten!

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            searcher57 @Garfonso last edited by

                                            @garfonso said in Test Adapter rpi2 2.x:

                                            @searcher57
                                            debug log steht da. Bitte mal auf debug stellen und das log von nem Adapter start einfügen. Wenn wir Glück haben steht da was drinnen.... ansonsten hab ich spontan keine Idee, was da noch schief gehen soll. 😕

                                            Frohe Weihnachten trotzdem. 🙂

                                            So jetzt hab ich es!

                                            rpi2.0
	2024-12-26 16:37:21.190	debug	wlan disabled -> clean up.
rpi2.0
	2024-12-26 16:37:21.190	debug	-1
rpi2.0
	2024-12-26 16:37:21.190	debug	CURRENT = wlan false
rpi2.0
	2024-12-26 16:37:21.190	debug	uptime disabled -> clean up.
rpi2.0
	2024-12-26 16:37:21.189	debug	-1
rpi2.0
	2024-12-26 16:37:21.189	debug	CURRENT = uptime false
rpi2.0
	2024-12-26 16:37:21.189	debug	temperature disabled -> clean up.
rpi2.0
	2024-12-26 16:37:21.189	debug	-1
rpi2.0
	2024-12-26 16:37:21.189	debug	CURRENT = temperature false
rpi2.0
	2024-12-26 16:37:21.188	debug	swap disabled -> clean up.
rpi2.0
	2024-12-26 16:37:21.188	debug	-1
rpi2.0
	2024-12-26 16:37:21.188	debug	CURRENT = swap false
rpi2.0
	2024-12-26 16:37:21.188	debug	sdcard disabled -> clean up.
rpi2.0
	2024-12-26 16:37:21.188	debug	-1
rpi2.0
	2024-12-26 16:37:21.188	debug	CURRENT = sdcard false
rpi2.0
	2024-12-26 16:37:21.141	debug	SETSTATE FOR rpi2.0.network.net_send VALUE = 37315299695
rpi2.0
	2024-12-26 16:37:21.141	debug	---> POST: for net_send in [object Object]
rpi2.0
	2024-12-26 16:37:21.089	debug	SETSTATE FOR rpi2.0.network.net_received VALUE = -32564790012
rpi2.0
	2024-12-26 16:37:21.089	debug	VALUE: 32564790012 POST: $1*-1
rpi2.0
	2024-12-26 16:37:21.089	debug	---> POST: $1*-1 for net_received in [object Object]
rpi2.0
	2024-12-26 16:37:21.089	debug	-1
rpi2.0
	2024-12-26 16:37:21.088	debug	CURRENT = network true
rpi2.0
	2024-12-26 16:37:21.041	debug	SETSTATE FOR rpi2.0.memory.memory_available VALUE = 5125.67
rpi2.0
	2024-12-26 16:37:21.041	debug	VALUE: 5248688 POST: $1/1024
rpi2.0
	2024-12-26 16:37:21.040	debug	---> POST: $1/1024 for memory_available in [object Object]
rpi2.0
	2024-12-26 16:37:20.993	debug	SETSTATE FOR rpi2.0.memory.memory_free VALUE = 1112.42
rpi2.0
	2024-12-26 16:37:20.993	debug	VALUE: 1139120 POST: $1/1024
rpi2.0
	2024-12-26 16:37:20.992	debug	---> POST: $1/1024 for memory_free in [object Object]
rpi2.0
	2024-12-26 16:37:20.945	debug	SETSTATE FOR rpi2.0.memory.memory_total VALUE = 8052.33
rpi2.0
	2024-12-26 16:37:20.945	debug	VALUE: 8245584 POST: $1/1024
rpi2.0
	2024-12-26 16:37:20.945	debug	---> POST: $1/1024 for memory_total in [object Object]
rpi2.0
	2024-12-26 16:37:20.944	debug	-1
rpi2.0
	2024-12-26 16:37:20.944	debug	CURRENT = memory true
rpi2.0
	2024-12-26 16:37:20.898	debug	SETSTATE FOR rpi2.0.raspberry.mem_gpu VALUE = 4
rpi2.0
	2024-12-26 16:37:20.897	debug	---> POST: for mem_gpu in [object Object]
rpi2.0
	2024-12-26 16:37:20.852	debug	SETSTATE FOR rpi2.0.raspberry.mem_arm VALUE = 1020
rpi2.0
	2024-12-26 16:37:20.852	debug	---> POST: for mem_arm in [object Object]
rpi2.0
	2024-12-26 16:37:20.805	debug	SETSTATE FOR rpi2.0.raspberry.cpu_voltage VALUE = 0.77
rpi2.0
	2024-12-26 16:37:20.804	debug	---> POST: for cpu_voltage in [object Object]
rpi2.0
	2024-12-26 16:37:20.804	debug	-1
rpi2.0
	2024-12-26 16:37:20.804	debug	CURRENT = raspberry true
rpi2.0
	2024-12-26 16:37:20.756	debug	SETSTATE FOR rpi2.0.cpu.scaling_governor VALUE = ondemand
rpi2.0
	2024-12-26 16:37:20.756	debug	---> POST: for scaling_governor in [object Object]
rpi2.0
	2024-12-26 16:37:20.712	debug	SETSTATE FOR rpi2.0.cpu.load15 VALUE = 0.21
rpi2.0
	2024-12-26 16:37:20.712	debug	NAME: load15 VALUE: 0.21
rpi2.0
	2024-12-26 16:37:20.712	debug	MATCHING: 0.21
rpi2.0
	2024-12-26 16:37:20.666	debug	SETSTATE FOR rpi2.0.cpu.load5 VALUE = 0.31
rpi2.0
	2024-12-26 16:37:20.665	debug	NAME: load5 VALUE: 0.31
rpi2.0
	2024-12-26 16:37:20.665	debug	MATCHING: 0.31
rpi2.0
	2024-12-26 16:37:20.620	debug	SETSTATE FOR rpi2.0.cpu.load1 VALUE = 0.48
rpi2.0
	2024-12-26 16:37:20.620	debug	NAME: load1 VALUE: 0.48
rpi2.0
	2024-12-26 16:37:20.620	debug	MATCHING: 0.48
rpi2.0
	2024-12-26 16:37:20.620	debug	---> POST: for load1,load5,load15 in [object Object]
rpi2.0
	2024-12-26 16:37:20.560	debug	SETSTATE FOR rpi2.0.cpu.cpu_frequency VALUE = 1600
rpi2.0
	2024-12-26 16:37:20.560	debug	VALUE: 1600000 POST: $1/1000
rpi2.0
	2024-12-26 16:37:20.560	debug	---> POST: $1/1000 for cpu_frequency in [object Object]
rpi2.0
	2024-12-26 16:37:20.560	debug	-1
rpi2.0
	2024-12-26 16:37:20.560	debug	CURRENT = cpu true
rpi2.0
	2024-12-26 16:37:20.560	debug	PARSING: wlan
rpi2.0
	2024-12-26 16:37:20.560	debug	PARSING: uptime
rpi2.0
	2024-12-26 16:37:20.559	debug	PARSING: temperature
rpi2.0
	2024-12-26 16:37:20.559	debug	PARSING: swap
rpi2.0
	2024-12-26 16:37:20.559	debug	PARSING: sdcard
rpi2.0
	2024-12-26 16:37:20.559	debug	---> POST:
rpi2.0
	2024-12-26 16:37:20.559	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.559	debug	---> REGEXP: /(.*)/
rpi2.0
	2024-12-26 16:37:20.558	debug	------------- 37315299695
rpi2.0
	2024-12-26 16:37:20.556	debug	---> cat /sys/class/net/e*/statistics/tx_bytes
rpi2.0
	2024-12-26 16:37:20.556	debug	PARSING: net_send
rpi2.0
	2024-12-26 16:37:20.556	debug	---> POST: $1*-1
rpi2.0
	2024-12-26 16:37:20.555	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.555	debug	---> REGEXP: /(.*)/
rpi2.0
	2024-12-26 16:37:20.555	debug	------------- 32564790012
rpi2.0
	2024-12-26 16:37:20.552	debug	---> cat /sys/class/net/e*/statistics/rx_bytes
rpi2.0
	2024-12-26 16:37:20.552	debug	PARSING: net_received
rpi2.0
	2024-12-26 16:37:20.552	debug	PARSING: network
rpi2.0
	2024-12-26 16:37:20.552	debug	---> POST: $1/1024
rpi2.0
	2024-12-26 16:37:20.552	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.552	debug	---> REGEXP: /MemAvailable:\s+(\d+)/m
rpi2.0
	2024-12-26 16:37:20.551	debug	------------- MemTotal: 8245584 kB MemFree: 1138400 kB MemAvailable: 5248688 kB Buffers: 216192 kB Cached: 3800864 kB SwapCached: 208 kB Active: 3254944 kB Inactive: 3335408 kB Active(anon): 2575088 kB Inactive(anon): 0 kB Active(file): 679856 kB Inactive(file): 3335408 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 204784 kB SwapFree: 191472 kB Zswap: 0 kB Zswapped: 0 kB Dirty: 544 kB Writeback: 0 kB AnonPages: 2573280 kB Mapped: 240144 kB Shmem: 1792 kB KReclaimable: 259760 kB Slab: 306864 kB SReclaimable: 259760 kB SUnreclaim: 47104 kB KernelStack: 7760 kB PageTables: 145904 kB SecPageTables: 0 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 4327568 kB Committed_AS: 3961776 kB VmallocTotal: 68180246528 kB VmallocUsed: 19824 kB VmallocChunk: 0 kB Percpu: 1280 kB CmaTotal: 327680 kB CmaFree: 259904 kB
rpi2.0
	2024-12-26 16:37:20.549	debug	---> cat /proc/meminfo
rpi2.0
	2024-12-26 16:37:20.548	debug	PARSING: memory_available
rpi2.0
	2024-12-26 16:37:20.548	debug	---> POST: $1/1024
rpi2.0
	2024-12-26 16:37:20.548	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.548	debug	---> REGEXP: /MemFree:\s+(\d+)/
rpi2.0
	2024-12-26 16:37:20.547	debug	------------- MemTotal: 8245584 kB MemFree: 1139120 kB MemAvailable: 5249408 kB Buffers: 216192 kB Cached: 3800864 kB SwapCached: 208 kB Active: 3254352 kB Inactive: 3335408 kB Active(anon): 2574496 kB Inactive(anon): 0 kB Active(file): 679856 kB Inactive(file): 3335408 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 204784 kB SwapFree: 191472 kB Zswap: 0 kB Zswapped: 0 kB Dirty: 544 kB Writeback: 0 kB AnonPages: 2572688 kB Mapped: 240144 kB Shmem: 1792 kB KReclaimable: 259760 kB Slab: 306864 kB SReclaimable: 259760 kB SUnreclaim: 47104 kB KernelStack: 7712 kB PageTables: 145904 kB SecPageTables: 0 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 4327568 kB Committed_AS: 3961776 kB VmallocTotal: 68180246528 kB VmallocUsed: 19792 kB VmallocChunk: 0 kB Percpu: 1280 kB CmaTotal: 327680 kB CmaFree: 259904 kB
rpi2.0
	2024-12-26 16:37:20.545	debug	---> cat /proc/meminfo
rpi2.0
	2024-12-26 16:37:20.545	debug	PARSING: memory_free
rpi2.0
	2024-12-26 16:37:20.545	debug	---> POST: $1/1024
rpi2.0
	2024-12-26 16:37:20.545	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.544	debug	---> REGEXP: /MemTotal:\s+(\d+)/
rpi2.0
	2024-12-26 16:37:20.544	debug	------------- MemTotal: 8245584 kB MemFree: 1139120 kB MemAvailable: 5249408 kB Buffers: 216192 kB Cached: 3800864 kB SwapCached: 208 kB Active: 3254352 kB Inactive: 3335408 kB Active(anon): 2574496 kB Inactive(anon): 0 kB Active(file): 679856 kB Inactive(file): 3335408 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 204784 kB SwapFree: 191472 kB Zswap: 0 kB Zswapped: 0 kB Dirty: 544 kB Writeback: 0 kB AnonPages: 2572688 kB Mapped: 240144 kB Shmem: 1792 kB KReclaimable: 259760 kB Slab: 306864 kB SReclaimable: 259760 kB SUnreclaim: 47104 kB KernelStack: 7712 kB PageTables: 145312 kB SecPageTables: 0 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 4327568 kB Committed_AS: 3961776 kB VmallocTotal: 68180246528 kB VmallocUsed: 19792 kB VmallocChunk: 0 kB Percpu: 1280 kB CmaTotal: 327680 kB CmaFree: 259904 kB
rpi2.0
	2024-12-26 16:37:20.541	debug	---> cat /proc/meminfo
rpi2.0
	2024-12-26 16:37:20.541	debug	PARSING: memory_total
rpi2.0
	2024-12-26 16:37:20.540	debug	PARSING: memory
rpi2.0
	2024-12-26 16:37:20.540	debug	---> POST:
rpi2.0
	2024-12-26 16:37:20.540	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.540	debug	---> REGEXP: /(\d+)/
rpi2.0
	2024-12-26 16:37:20.539	debug	------------- gpu=4M
rpi2.0
	2024-12-26 16:37:20.535	debug	---> vcgencmd get_mem gpu
rpi2.0
	2024-12-26 16:37:20.535	debug	PARSING: mem_gpu
rpi2.0
	2024-12-26 16:37:20.535	debug	---> POST:
rpi2.0
	2024-12-26 16:37:20.535	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.535	debug	---> REGEXP: /(\d+)/
rpi2.0
	2024-12-26 16:37:20.535	debug	------------- arm=1020M
rpi2.0
	2024-12-26 16:37:20.531	debug	---> vcgencmd get_mem arm
rpi2.0
	2024-12-26 16:37:20.531	debug	PARSING: mem_arm
rpi2.0
	2024-12-26 16:37:20.531	debug	---> POST:
rpi2.0
	2024-12-26 16:37:20.531	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.530	debug	---> REGEXP: /(\d+.\d+)V/
rpi2.0
	2024-12-26 16:37:20.530	debug	------------- volt=0.7659V
rpi2.0
	2024-12-26 16:37:20.526	debug	---> vcgencmd measure_volts core
rpi2.0
	2024-12-26 16:37:20.526	debug	PARSING: cpu_voltage
rpi2.0
	2024-12-26 16:37:20.526	debug	PARSING: raspberry
rpi2.0
	2024-12-26 16:37:20.526	debug	---> POST:
rpi2.0
	2024-12-26 16:37:20.526	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.526	debug	---> REGEXP: /(.*)/
rpi2.0
	2024-12-26 16:37:20.525	debug	------------- ondemand
rpi2.0
	2024-12-26 16:37:20.522	debug	---> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
rpi2.0
	2024-12-26 16:37:20.522	debug	PARSING: scaling_governor
rpi2.0
	2024-12-26 16:37:20.522	debug	NAME: load15, VALULE: 0.21
rpi2.0
	2024-12-26 16:37:20.522	debug	MATCHING: 0.21
rpi2.0
	2024-12-26 16:37:20.522	debug	NAME: load5, VALULE: 0.31
rpi2.0
	2024-12-26 16:37:20.522	debug	MATCHING: 0.31
rpi2.0
	2024-12-26 16:37:20.522	debug	NAME: load1, VALULE: 0.48
rpi2.0
	2024-12-26 16:37:20.521	debug	MATCHING: 0.48
rpi2.0
	2024-12-26 16:37:20.521	debug	GROUPS: 4
rpi2.0
	2024-12-26 16:37:20.521	debug	---> REGEXP: /^(\S+)\s(\S+)\s(\S+)/
rpi2.0
	2024-12-26 16:37:20.521	debug	------------- 0.48 0.31 0.21 1/480 1339934
rpi2.0
	2024-12-26 16:37:20.518	debug	---> cat /proc/loadavg
rpi2.0
	2024-12-26 16:37:20.518	debug	PARSING: load1,load5,load15
rpi2.0
	2024-12-26 16:37:20.518	debug	---> POST: $1/1000
rpi2.0
	2024-12-26 16:37:20.518	debug	GROUPS: 2
rpi2.0
	2024-12-26 16:37:20.518	debug	---> REGEXP: /(.*)/
rpi2.0
	2024-12-26 16:37:20.517	debug	------------- 1600000
rpi2.0
	2024-12-26 16:37:20.515	debug	---> test -r /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq && cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq || test -r /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq && cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq || echo -1000
rpi2.0
	2024-12-26 16:37:20.515	debug	PARSING: cpu_frequency
rpi2.0
	2024-12-26 16:37:20.514	debug	PARSING: cpu
rpi2.0
	2024-12-26 16:37:20.514	debug	start parsing
rpi2.0
	2024-12-26 16:36:21.272	debug	GPIO chip undefined initialized
rpi2.0
	2024-12-26 16:36:21.272	debug	Got chip: undefined
rpi2.0
	2024-12-26 16:36:21.271	warn	If the library is installed and npm list | grep opengpio shows the npm library is also installed, please report this issue to the adapter developer with the model of your device and deboug output from an adapter start.
rpi2.0
	2024-12-26 16:36:21.271	warn	Please make sure that libgpiod-dev (on raspian/debian run sudo apt install libgpiod-dev) is installed in the system and then reinstall the adapter.
rpi2.0
	2024-12-26 16:36:21.271	warn	Cannot initialize GPIO: No chip found. GPIO functionality disabled!
rpi2.0
	2024-12-26 16:36:21.271	debug	Using GPIO chip 4 for Raspberry Pi 5 or newer.
rpi2.0
	2024-12-26 16:36:21.271	debug	Got 5 from Raspberry Pi 5 Model B Rev 1.0
                                            Z Garfonso 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            622
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            27
                                            495
                                            60133
                                            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