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
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter rpi2 2.x

NEWS

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

Test Adapter rpi2 2.x

Geplant Angeheftet Gesperrt Verschoben Tester
519 Beiträge 29 Kommentatoren 148.7k Aufrufe 20 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.
  • S searcher57

    @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 BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #286

    @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

    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

    S 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @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 Offline
      S Offline
      searcher57
      schrieb am zuletzt editiert von
      #287

      @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 BraunT GarfonsoG 2 Antworten Letzte Antwort
      0
      • S searcher57

        @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 BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #288

        @searcher57

        Hier?

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

        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

        S 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @searcher57

          Hier?

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

          S Offline
          S Offline
          searcher57
          schrieb am zuletzt editiert von
          #289

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

          @searcher57

          Hier?

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

          Nein, mache ich!

          1 Antwort Letzte Antwort
          0
          • MoppedmanM Moppedman

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

            GarfonsoG Offline
            GarfonsoG Offline
            Garfonso
            Developer
            schrieb am zuletzt editiert von
            #290

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

            Ultimativer Lovelace Leitfaden: https://forum.iobroker.net/topic/35937/der-ultimative-iobroker-lovelace-leitfaden-dokumentation

            Lovelace UI Beispiele: https://forum.iobroker.net/topic/35950/zeigt-her-eure-lovelace-visualisierung

            MoppedmanM 1 Antwort Letzte Antwort
            0
            • MoppedmanM Moppedman

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

              GarfonsoG Offline
              GarfonsoG Offline
              Garfonso
              Developer
              schrieb am zuletzt editiert von
              #291

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

              Ultimativer Lovelace Leitfaden: https://forum.iobroker.net/topic/35937/der-ultimative-iobroker-lovelace-leitfaden-dokumentation

              Lovelace UI Beispiele: https://forum.iobroker.net/topic/35950/zeigt-her-eure-lovelace-visualisierung

              1 Antwort Letzte Antwort
              0
              • S searcher57

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

                GarfonsoG Offline
                GarfonsoG Offline
                Garfonso
                Developer
                schrieb am zuletzt editiert von
                #292

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

                Ultimativer Lovelace Leitfaden: https://forum.iobroker.net/topic/35937/der-ultimative-iobroker-lovelace-leitfaden-dokumentation

                Lovelace UI Beispiele: https://forum.iobroker.net/topic/35950/zeigt-her-eure-lovelace-visualisierung

                S 2 Antworten Letzte Antwort
                0
                • GarfonsoG Garfonso

                  @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 Offline
                  S Offline
                  searcher57
                  schrieb am zuletzt editiert von
                  #293

                  @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 Antwort Letzte Antwort
                  0
                  • GarfonsoG Garfonso

                    @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 Offline
                    S Offline
                    searcher57
                    schrieb am zuletzt editiert von
                    #294

                    @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 GarfonsoG 2 Antworten Letzte Antwort
                    0
                    • S searcher57

                      @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 Offline
                      Z Offline
                      Zimbl
                      schrieb am zuletzt editiert von
                      #295

                      Hallo zusammen,

                      ich würde mich gerne auch an diesem Thema anschließen, ich habe genau das gleiche Problem, ich kann
                      diese GPIO nicht ansteuern, wenn ich das Probiere, dann wird der Ausgang bzw. in dem Fall True/False rot.

                      Den Adapter habe ich bereits einmal De-Installiert und dann wieder Installiert.

                      Aber immer noch alles ohne Erfolg.

                      Anbei mein Diag :

                      
========== Start marking the full check here ===========

```bash
Script v.2024-10-19

*** BASE SYSTEM ***
 Static hostname: raspihome
       Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.6.62+rpt-rpi-2712
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 5 Model B Rev 1.0
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 10:47:05 up 7 min,  2 users,  load average: 1.06, 0.49, 0.25
CPU threads: 4


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'bookworm'!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Sat 2024-12-28 10:47:05 CET
           Universal time: Sat 2024-12-28 09:47:05 UTC
                 RTC time: Sat 2024-12-28 09:47:05
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.2G        1.4G        2.0G        5.8M        998M        2.9G
Swap:           202M          0B        202M
Total:          4.4G        1.4G        2.2G

Active iob-Instances:   7

         4045 M total memory
         1300 M used memory
         1327 M active memory
          629 M inactive memory
         1862 M free memory
           69 M buffer memory
          883 M swap cache
          192 M total swap
            0 M used swap
          192 M free swap

*** top - Table Of Processes  ***
top - 10:47:05 up 7 min,  2 users,  load average: 1.06, 0.49, 0.25
Tasks: 175 total,   1 running, 174 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   4045.0 total,   1862.7 free,   1300.6 used,    952.3 buff/cache
MiB Swap:    193.0 total,    193.0 free,      0.0 used.   2744.4 avail Mem

*** FAILED SERVICES ***

  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  2.0G     0  2.0G   0% /dev
tmpfs          tmpfs     405M  5.4M  400M   2% /run
/dev/mmcblk0p2 ext4      6.9G  6.3G  182M  98% /
tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      510M   65M  446M  13% /boot/firmware
tmpfs          tmpfs     405M   16K  405M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sat Dec 28 10:39:15 2024] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave  smsc95xx.macaddr=2C:CF:67:97:18:01 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=918bb801-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB cfg80211.ieee80211_regdom=GB
[Sat Dec 28 10:39:17 2024] EXT4-fs (mmcblk0p2): mounted filesystem 3b445224-0aeb-4897-9108-009ed4211fb4 ro with ordered data mode. Quota mode: none.
[Sat Dec 28 10:39:19 2024] EXT4-fs (mmcblk0p2): re-mounted 3b445224-0aeb-4897-9108-009ed4211fb4 r/w. Quota mode: none.

Show mounted filesystems:
TARGET           SOURCE         FSTYPE OPTIONS
/                /dev/mmcblk0p2 ext4   rw,noatime
`-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
950M    /var/
445M    /var/cache
431M    /var/cache/apt
317M    /var/cache/apt/archives
185M    /var/lib

Archived and active journals take up 120.5M in the file system.

/opt/iobroker/backups:
18M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
856M    /opt/iobroker/iobroker-data/
772M    /opt/iobroker/iobroker-data/files
617M    /opt/iobroker/iobroker-data/files/javascript.admin
560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js

The five largest files in iobroker-data are:
37M     /opt/iobroker/iobroker-data/objects.jsonl
25M     /opt/iobroker/iobroker-data/files/wireless-settings.admin/static/js/main.fe851d24.js.map
24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
12M     /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js
11M     /opt/iobroker/iobroker-data/files/wireless-settings.admin/static/js/main.fe851d24.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ceccc8e6cbc9eb119edf8b4f1d69213e-if00-port0

HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
/dev/ttyUSB0

*** NodeJS-Installation ***

/usr/bin/nodejs         v20.18.1
/usr/bin/node           v20.18.1
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

nodejs:
  Installed: 20.18.1-1nodesource1
  Candidate: 20.18.1-1nodesource1
  Version table:
 *** 20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     18.19.0+dfsg-6~deb12u2 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
     18.19.0+dfsg-6~deb12u1 500
        500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
raspihome        raspihome (version: 6.0.11, hostname: raspihome   , alive, uptime: 31)

Core adapters versions
js-controller:  6.0.11
admin:          7.1.5
javascript:     8.8.3

nodejs modules from github:     0

Adapter State
+ system.adapter.admin.0                  : admin                 : raspihome                              -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.backitup.0               : backitup              : raspihome                              -  enabled
  system.adapter.discovery.0              : discovery             : raspihome                              -  enabled
+ system.adapter.javascript.0             : javascript            : raspihome                              -  enabled
  system.adapter.modbus.0                 : modbus                : raspihome                              -  enabled
  system.adapter.rpi2.0                   : rpi2                  : raspihome                              -  enabled
+ system.adapter.shelly.0                 : shelly                : raspihome                              -  enabled, port: 1882, bind: 0.0.0.0
  system.adapter.terminal.0               : terminal              : raspihome                              -  enabled, port: 8088, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.tuya.0                   : tuya                  : raspihome                              -  enabled
  system.adapter.welcome.0                : welcome               : raspihome                              -  enabled, port: 80, bind: 0.0.0.0, run as: admin
  system.adapter.wireless-settings.0      : wireless-settings     : raspihome                              - disabled
+ system.adapter.zigbee.0                 : zigbee                : raspihome                              -  enabled, port: /dev/ttyUSB0

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : raspihome                              -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.shelly.0                 : shelly                : raspihome                              -  enabled, port: 1882, bind: 0.0.0.0
  system.adapter.terminal.0               : terminal              : raspihome                              -  enabled, port: 8088, bind: 0.0.0.0 (SSL), run as: admin
  system.adapter.welcome.0                : welcome               : raspihome                              -  enabled, port: 80, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : raspihome                              -  enabled, port: /dev/ttyUSB0

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): stable
Upgrade policy: none

Installed ioBroker-Instances
Used repository: stable
Adapter    "admin"        : 7.1.5    , installed 7.1.5
Adapter    "backitup"     : 3.0.25   , installed 3.0.25
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "javascript"   : 8.8.3    , installed 8.8.3
Controller "js-controller": 7.0.6    , installed 6.0.11 [Updatable]
Adapter    "modbus"       : 6.3.2    , installed 6.3.2
Adapter    "rpi2"         : 2.2.1    , installed 2.2.1
Adapter    "shelly"       : 8.2.1    , installed 8.2.1
Adapter    "terminal"     : 1.0.0    , installed 1.0.0
Adapter    "tuya"         : 3.16.0   , installed 3.16.0
Adapter    "welcome"      : 1.0.2    , installed 1.0.2
Adapter    "wireless-settings": 1.0.2, installed 1.0.2
Adapter    "zigbee"       : 1.10.3   , installed 1.10.3

Objects and States
Please stand by - This may take a while
Objects:        815
States:         616

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          6337       760/sshd: /usr/sbin
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       19159      4186/iobroker.js-co
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       19164      4186/iobroker.js-co
tcp6       0      0 :::80                   :::*                    LISTEN      1001       22054      4711/io.welcome.0
tcp6       0      0 :::22                   :::*                    LISTEN      0          6339       760/sshd: /usr/sbin
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       19205      4206/io.admin.0
tcp6       0      0 :::8088                 :::*                    LISTEN      1001       22139      4757/io.terminal.0
udp        0      0 0.0.0.0:6666            0.0.0.0:*                           1001       22600      4366/io.tuya.0
udp        0      0 0.0.0.0:6667            0.0.0.0:*                           1001       22601      4366/io.tuya.0
udp        0      0 0.0.0.0:38105           0.0.0.0:*                           104        656        604/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        654        604/avahi-daemon: r
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       20981      4299/io.shelly.0
udp6       0      0 :::34920                :::*                                104        657        604/avahi-daemon: r
udp6       0      0 fe80::9fc3:98f7:bf5:546 :::*                                0          6430       711/NetworkManager
udp6       0      0 fe80::4bfa:4f8a:169:546 :::*                                0          875        711/NetworkManager
udp6       0      0 :::5353                 :::*                                104        655        604/avahi-daemon: r
                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • Z Zimbl

                        Hallo zusammen,

                        ich würde mich gerne auch an diesem Thema anschließen, ich habe genau das gleiche Problem, ich kann
                        diese GPIO nicht ansteuern, wenn ich das Probiere, dann wird der Ausgang bzw. in dem Fall True/False rot.

                        Den Adapter habe ich bereits einmal De-Installiert und dann wieder Installiert.

                        Aber immer noch alles ohne Erfolg.

                        Anbei mein Diag :

                        
========== Start marking the full check here ===========

```bash
Script v.2024-10-19

*** BASE SYSTEM ***
 Static hostname: raspihome
       Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.6.62+rpt-rpi-2712
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 5 Model B Rev 1.0
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 10:47:05 up 7 min,  2 users,  load average: 1.06, 0.49, 0.25
CPU threads: 4


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'bookworm'!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Sat 2024-12-28 10:47:05 CET
           Universal time: Sat 2024-12-28 09:47:05 UTC
                 RTC time: Sat 2024-12-28 09:47:05
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            4.2G        1.4G        2.0G        5.8M        998M        2.9G
Swap:           202M          0B        202M
Total:          4.4G        1.4G        2.2G

Active iob-Instances:   7

         4045 M total memory
         1300 M used memory
         1327 M active memory
          629 M inactive memory
         1862 M free memory
           69 M buffer memory
          883 M swap cache
          192 M total swap
            0 M used swap
          192 M free swap

*** top - Table Of Processes  ***
top - 10:47:05 up 7 min,  2 users,  load average: 1.06, 0.49, 0.25
Tasks: 175 total,   1 running, 174 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   4045.0 total,   1862.7 free,   1300.6 used,    952.3 buff/cache
MiB Swap:    193.0 total,    193.0 free,      0.0 used.   2744.4 avail Mem

*** FAILED SERVICES ***

  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  2.0G     0  2.0G   0% /dev
tmpfs          tmpfs     405M  5.4M  400M   2% /run
/dev/mmcblk0p2 ext4      6.9G  6.3G  182M  98% /
tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      510M   65M  446M  13% /boot/firmware
tmpfs          tmpfs     405M   16K  405M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sat Dec 28 10:39:15 2024] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave  smsc95xx.macaddr=2C:CF:67:97:18:01 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=918bb801-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB cfg80211.ieee80211_regdom=GB
[Sat Dec 28 10:39:17 2024] EXT4-fs (mmcblk0p2): mounted filesystem 3b445224-0aeb-4897-9108-009ed4211fb4 ro with ordered data mode. Quota mode: none.
[Sat Dec 28 10:39:19 2024] EXT4-fs (mmcblk0p2): re-mounted 3b445224-0aeb-4897-9108-009ed4211fb4 r/w. Quota mode: none.

Show mounted filesystems:
TARGET           SOURCE         FSTYPE OPTIONS
/                /dev/mmcblk0p2 ext4   rw,noatime
`-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
950M    /var/
445M    /var/cache
431M    /var/cache/apt
317M    /var/cache/apt/archives
185M    /var/lib

Archived and active journals take up 120.5M in the file system.

/opt/iobroker/backups:
18M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
856M    /opt/iobroker/iobroker-data/
772M    /opt/iobroker/iobroker-data/files
617M    /opt/iobroker/iobroker-data/files/javascript.admin
560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js

The five largest files in iobroker-data are:
37M     /opt/iobroker/iobroker-data/objects.jsonl
25M     /opt/iobroker/iobroker-data/files/wireless-settings.admin/static/js/main.fe851d24.js.map
24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
12M     /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js
11M     /opt/iobroker/iobroker-data/files/wireless-settings.admin/static/js/main.fe851d24.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ceccc8e6cbc9eb119edf8b4f1d69213e-if00-port0

HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
/dev/ttyUSB0

*** NodeJS-Installation ***

/usr/bin/nodejs         v20.18.1
/usr/bin/node           v20.18.1
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

nodejs:
  Installed: 20.18.1-1nodesource1
  Candidate: 20.18.1-1nodesource1
  Version table:
 *** 20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     18.19.0+dfsg-6~deb12u2 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
     18.19.0+dfsg-6~deb12u1 500
        500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
raspihome        raspihome (version: 6.0.11, hostname: raspihome   , alive, uptime: 31)

Core adapters versions
js-controller:  6.0.11
admin:          7.1.5
javascript:     8.8.3

nodejs modules from github:     0

Adapter State
+ system.adapter.admin.0                  : admin                 : raspihome                              -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.backitup.0               : backitup              : raspihome                              -  enabled
  system.adapter.discovery.0              : discovery             : raspihome                              -  enabled
+ system.adapter.javascript.0             : javascript            : raspihome                              -  enabled
  system.adapter.modbus.0                 : modbus                : raspihome                              -  enabled
  system.adapter.rpi2.0                   : rpi2                  : raspihome                              -  enabled
+ system.adapter.shelly.0                 : shelly                : raspihome                              -  enabled, port: 1882, bind: 0.0.0.0
  system.adapter.terminal.0               : terminal              : raspihome                              -  enabled, port: 8088, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.tuya.0                   : tuya                  : raspihome                              -  enabled
  system.adapter.welcome.0                : welcome               : raspihome                              -  enabled, port: 80, bind: 0.0.0.0, run as: admin
  system.adapter.wireless-settings.0      : wireless-settings     : raspihome                              - disabled
+ system.adapter.zigbee.0                 : zigbee                : raspihome                              -  enabled, port: /dev/ttyUSB0

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : raspihome                              -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.shelly.0                 : shelly                : raspihome                              -  enabled, port: 1882, bind: 0.0.0.0
  system.adapter.terminal.0               : terminal              : raspihome                              -  enabled, port: 8088, bind: 0.0.0.0 (SSL), run as: admin
  system.adapter.welcome.0                : welcome               : raspihome                              -  enabled, port: 80, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : raspihome                              -  enabled, port: /dev/ttyUSB0

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): stable
Upgrade policy: none

Installed ioBroker-Instances
Used repository: stable
Adapter    "admin"        : 7.1.5    , installed 7.1.5
Adapter    "backitup"     : 3.0.25   , installed 3.0.25
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "javascript"   : 8.8.3    , installed 8.8.3
Controller "js-controller": 7.0.6    , installed 6.0.11 [Updatable]
Adapter    "modbus"       : 6.3.2    , installed 6.3.2
Adapter    "rpi2"         : 2.2.1    , installed 2.2.1
Adapter    "shelly"       : 8.2.1    , installed 8.2.1
Adapter    "terminal"     : 1.0.0    , installed 1.0.0
Adapter    "tuya"         : 3.16.0   , installed 3.16.0
Adapter    "welcome"      : 1.0.2    , installed 1.0.2
Adapter    "wireless-settings": 1.0.2, installed 1.0.2
Adapter    "zigbee"       : 1.10.3   , installed 1.10.3

Objects and States
Please stand by - This may take a while
Objects:        815
States:         616

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          6337       760/sshd: /usr/sbin
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       19159      4186/iobroker.js-co
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       19164      4186/iobroker.js-co
tcp6       0      0 :::80                   :::*                    LISTEN      1001       22054      4711/io.welcome.0
tcp6       0      0 :::22                   :::*                    LISTEN      0          6339       760/sshd: /usr/sbin
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       19205      4206/io.admin.0
tcp6       0      0 :::8088                 :::*                    LISTEN      1001       22139      4757/io.terminal.0
udp        0      0 0.0.0.0:6666            0.0.0.0:*                           1001       22600      4366/io.tuya.0
udp        0      0 0.0.0.0:6667            0.0.0.0:*                           1001       22601      4366/io.tuya.0
udp        0      0 0.0.0.0:38105           0.0.0.0:*                           104        656        604/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        654        604/avahi-daemon: r
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       20981      4299/io.shelly.0
udp6       0      0 :::34920                :::*                                104        657        604/avahi-daemon: r
udp6       0      0 fe80::9fc3:98f7:bf5:546 :::*                                0          6430       711/NetworkManager
udp6       0      0 fe80::4bfa:4f8a:169:546 :::*                                0          875        711/NetworkManager
udp6       0      0 :::5353                 :::*                                104        655        604/avahi-daemon: r
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #296

                        @zimbl sagte in Test Adapter rpi2 2.x:

                        Controller "js-controller": 7.0.6 , installed 6.0.11 [Updatable]

                        Auf Stand bringen.

                        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

                        Z 1 Antwort Letzte Antwort
                        0
                        • Thomas BraunT Thomas Braun

                          @zimbl sagte in Test Adapter rpi2 2.x:

                          Controller "js-controller": 7.0.6 , installed 6.0.11 [Updatable]

                          Auf Stand bringen.

                          Z Offline
                          Z Offline
                          Zimbl
                          schrieb am zuletzt editiert von
                          #297

                          @thomas-braun

                          oh da habe ich schlechte Erfahrung mit gemacht, diese akt. durchzuführen.

                          Kannst du mir genau sagen, wie ich da am besten vorgehe ?

                          Hatte da mal eine Anleitung aus dem Netz gehabt und alles ging irgendwie schief was schief gehen konnte :-)

                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • Z Zimbl

                            @thomas-braun

                            oh da habe ich schlechte Erfahrung mit gemacht, diese akt. durchzuführen.

                            Kannst du mir genau sagen, wie ich da am besten vorgehe ?

                            Hatte da mal eine Anleitung aus dem Netz gehabt und alles ging irgendwie schief was schief gehen konnte :-)

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

                            @zimbl sagte in Test Adapter rpi2 2.x:

                            oh da habe ich schlechte Erfahrung mit gemacht, diese akt. durchzuführen.

                            Und ich habe schlechte Erfahrungen mit ungepflegten Kisten gemacht.

                            iob stop
iob update
iob upgrade self
iob start

                            Fertig.

                            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

                            Z 1 Antwort Letzte Antwort
                            0
                            • Thomas BraunT Thomas Braun

                              @zimbl sagte in Test Adapter rpi2 2.x:

                              oh da habe ich schlechte Erfahrung mit gemacht, diese akt. durchzuführen.

                              Und ich habe schlechte Erfahrungen mit ungepflegten Kisten gemacht.

                              iob stop
iob update
iob upgrade self
iob start

                              Fertig.

                              Z Offline
                              Z Offline
                              Zimbl
                              schrieb am zuletzt editiert von
                              #299

                              @thomas-braun

                              nein ich meine damit irgendwelche Anleitungen im Netz zu nehmen, wusste jetzt nicht, das es auch einfach mit dem Standard möglich ist, weil ich hatte den schon durchgeführt...aber hatte der das wohl nicht gemacht...

                              vielen Dank Thomas...

                              Thomas BraunT 1 Antwort Letzte Antwort
                              0
                              • Z Zimbl

                                @thomas-braun

                                nein ich meine damit irgendwelche Anleitungen im Netz zu nehmen, wusste jetzt nicht, das es auch einfach mit dem Standard möglich ist, weil ich hatte den schon durchgeführt...aber hatte der das wohl nicht gemacht...

                                vielen Dank Thomas...

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

                                @zimbl

                                'Der' macht das aber nicht ohne Meldungen...
                                Die 'der' Admin dann liest.

                                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

                                Z 1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @zimbl

                                  'Der' macht das aber nicht ohne Meldungen...
                                  Die 'der' Admin dann liest.

                                  Z Offline
                                  Z Offline
                                  Zimbl
                                  schrieb am zuletzt editiert von
                                  #301

                                  @thomas-braun

                                  ja aber jetzt habe ich das alles aktualisiert...und es ist aber immer noch so, wenn ich einen GPIO Ansteuern möchte, wird der Befehl TRUE or FALSE ....ROT...nicht Grün...wie sonst...

                                  was kann ich nun noch machen ?

                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • Z Zimbl

                                    @thomas-braun

                                    ja aber jetzt habe ich das alles aktualisiert...und es ist aber immer noch so, wenn ich einen GPIO Ansteuern möchte, wird der Befehl TRUE or FALSE ....ROT...nicht Grün...wie sonst...

                                    was kann ich nun noch machen ?

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

                                    @zimbl sagte in Test Adapter rpi2 2.x:

                                    was kann ich nun noch machen ?

                                    Abwarten.
                                    Und/oder bei GitHub evtl. zum passenden Issue weitere Erkenntnisse beitragen.

                                    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
                                    • Z Offline
                                      Z Offline
                                      Zimbl
                                      schrieb am zuletzt editiert von
                                      #303

                                      @thomas-braun

                                      ist es eigentlich möglich einen alten RPI2 Adapter zu installieren ?

                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • Z Zimbl

                                        @thomas-braun

                                        ist es eigentlich möglich einen alten RPI2 Adapter zu installieren ?

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

                                        @zimbl

                                        Wozu? Der funktioniert ja dann noch weniger als der aktuelle. Der Adapter musste ja genau deswegen angepasst werden, weil der an mehrere Stellen nicht mehr funktionierte.

                                        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

                                        Z 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @zimbl

                                          Wozu? Der funktioniert ja dann noch weniger als der aktuelle. Der Adapter musste ja genau deswegen angepasst werden, weil der an mehrere Stellen nicht mehr funktionierte.

                                          Z Offline
                                          Z Offline
                                          Zimbl
                                          schrieb am zuletzt editiert von
                                          #305

                                          @thomas-braun

                                          achso ok, das wusste ich nicht. Weil mit dem alten PI2 hatte ich keine Probleme.

                                          Ich habe nun jetzt aufgerüstet und siehe da, es geht gerade noch weniger.

                                          Aber gut, dann Abwarten...

                                          HomoranH 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

                                          653

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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