Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Gelöst: Systeminfo-Adapter Probleme nach Update

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Gelöst: Systeminfo-Adapter Probleme nach Update

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      SmartHomer 0 last edited by SmartHomer 0

      Ich habe heute meine ioBroker-Installation auf den neusten Stand aktualisiert:

      Node.js auf v14.19.0
      Host auf v4.0.15
      Admin auf 5.3.1

      ioBroker läuft im buanet-Docker auf einer Synology-NAS

      PlatformBetriebssystem:linux
      Architektur:x64
      CPUs:4
      Geschwindigkeit:1501 MHz
      Modell:Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
      RAM:7.6 GB
      System-Betriebszeit:29 T. 10:40:53
      Node.js:v14.19.0
      time:1646040013177
      timeOffset:-60
      Adapter-Anzahl:400
      NPM:v6.14.16
      Datenträgergröße:251.9 GB
      freier Festplattenspeicher:204.2 GB
      Betriebszeit:00:01:37
      Aktive Instanzen:18
      Pfad:/opt/iobroker/

      Seit dem Update funktioniert der Systeminfo-Adapter nicht mehr:

      e8891c97-73a8-440d-8b29-90fa7d53a518-grafik.png

      systeminfo.0
      	2692	2022-02-28 10:35:20.042	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2692	2022-02-28 10:35:20.040	info	terminating
      systeminfo.0
      	2692	2022-02-28 10:35:20.039	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2692	2022-02-28 10:35:20.042	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2692	2022-02-28 10:35:20.040	info	terminating
      systeminfo.0
      	2692	2022-02-28 10:35:20.039	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2692	2022-02-28 10:35:20.020	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2692	2022-02-28 10:35:20.019	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2692	2022-02-28 10:35:20.016	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2692	2022-02-28 10:35:20.015	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2692	2022-02-28 10:35:20.013	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2692	2022-02-28 10:35:20.020	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2692	2022-02-28 10:35:20.019	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2692	2022-02-28 10:35:20.016	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2692	2022-02-28 10:35:20.015	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2692	2022-02-28 10:35:20.013	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2692	2022-02-28 10:35:19.987	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2692	2022-02-28 10:35:19.987	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2692	2022-02-28 10:35:19.754	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2692	2022-02-28 10:35:19.754	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2692	2022-02-28 10:35:19.689	debug	States create User PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.689	debug	States create User PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.688	debug	States create System PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.688	debug	States create System PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.672	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2692	2022-02-28 10:35:19.672	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2692	2022-02-28 10:35:19.643	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2692	2022-02-28 10:35:19.643	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2692	2022-02-28 10:35:19.636	debug	Objects client initialize lua scripts
      systeminfo.0
      	2692	2022-02-28 10:35:19.636	debug	Objects client initialize lua scripts
      systeminfo.0
      	2692	2022-02-28 10:35:19.591	debug	Objects create User PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.589	debug	Objects create System PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.591	debug	Objects create User PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.589	debug	Objects create System PubSub Client
      systeminfo.0
      	2692	2022-02-28 10:35:19.586	debug	Objects client ready ... initialize now
      systeminfo.0
      	2692	2022-02-28 10:35:19.586	debug	Objects client ready ... initialize now
      systeminfo.0
      	2692	2022-02-28 10:35:19.197	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2692	2022-02-28 10:35:19.197	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2620	2022-02-28 10:34:51.743	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      systeminfo.0
      	2620	2022-02-28 10:34:51.743	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      systeminfo.0
      	2620	2022-02-28 10:34:51.693	error	adapter disabled
      systeminfo.0
      	2620	2022-02-28 10:34:51.693	error	adapter disabled
      systeminfo.0
      	2620	2022-02-28 10:34:51.599	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2620	2022-02-28 10:34:51.599	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2620	2022-02-28 10:34:51.534	debug	States create User PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.534	debug	States create User PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.533	debug	States create System PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.533	debug	States create System PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.517	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2620	2022-02-28 10:34:51.517	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2620	2022-02-28 10:34:51.486	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2620	2022-02-28 10:34:51.486	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2620	2022-02-28 10:34:51.480	debug	Objects client initialize lua scripts
      systeminfo.0
      	2620	2022-02-28 10:34:51.480	debug	Objects client initialize lua scripts
      systeminfo.0
      	2620	2022-02-28 10:34:51.434	debug	Objects create User PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.432	debug	Objects create System PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.434	debug	Objects create User PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.432	debug	Objects create System PubSub Client
      systeminfo.0
      	2620	2022-02-28 10:34:51.429	debug	Objects client ready ... initialize now
      systeminfo.0
      	2620	2022-02-28 10:34:51.429	debug	Objects client ready ... initialize now
      systeminfo.0
      	2620	2022-02-28 10:34:51.081	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2620	2022-02-28 10:34:51.081	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2581	2022-02-28 10:34:19.503	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2581	2022-02-28 10:34:19.502	info	terminating
      systeminfo.0
      	2581	2022-02-28 10:34:19.501	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2581	2022-02-28 10:34:19.503	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2581	2022-02-28 10:34:19.502	info	terminating
      systeminfo.0
      	2581	2022-02-28 10:34:19.501	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2581	2022-02-28 10:34:19.485	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2581	2022-02-28 10:34:19.484	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2581	2022-02-28 10:34:19.481	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2581	2022-02-28 10:34:19.480	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2581	2022-02-28 10:34:19.478	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2581	2022-02-28 10:34:19.485	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2581	2022-02-28 10:34:19.484	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2581	2022-02-28 10:34:19.481	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2581	2022-02-28 10:34:19.480	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2581	2022-02-28 10:34:19.478	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2581	2022-02-28 10:34:19.452	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2581	2022-02-28 10:34:19.452	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2581	2022-02-28 10:34:19.204	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2581	2022-02-28 10:34:19.204	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2581	2022-02-28 10:34:19.132	debug	States create User PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.132	debug	States create User PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.131	debug	States create System PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.131	debug	States create System PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.115	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2581	2022-02-28 10:34:19.115	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2581	2022-02-28 10:34:19.086	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2581	2022-02-28 10:34:19.086	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2581	2022-02-28 10:34:19.079	debug	Objects client initialize lua scripts
      systeminfo.0
      	2581	2022-02-28 10:34:19.079	debug	Objects client initialize lua scripts
      systeminfo.0
      	2581	2022-02-28 10:34:19.032	debug	Objects create User PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.031	debug	Objects create System PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.032	debug	Objects create User PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.031	debug	Objects create System PubSub Client
      systeminfo.0
      	2581	2022-02-28 10:34:19.027	debug	Objects client ready ... initialize now
      systeminfo.0
      	2581	2022-02-28 10:34:19.027	debug	Objects client ready ... initialize now
      systeminfo.0
      	2581	2022-02-28 10:34:18.666	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2581	2022-02-28 10:34:18.666	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2534	2022-02-28 10:33:47.106	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2534	2022-02-28 10:33:47.104	info	terminating
      systeminfo.0
      	2534	2022-02-28 10:33:47.103	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2534	2022-02-28 10:33:47.106	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      systeminfo.0
      	2534	2022-02-28 10:33:47.104	info	terminating
      systeminfo.0
      	2534	2022-02-28 10:33:47.103	debug	Adapter disconnected and stopped with dostop(false) and callback(true)
      systeminfo.0
      	2534	2022-02-28 10:33:47.088	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2534	2022-02-28 10:33:47.087	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2534	2022-02-28 10:33:47.084	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2534	2022-02-28 10:33:47.083	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2534	2022-02-28 10:33:47.081	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2534	2022-02-28 10:33:47.088	error	Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2534	2022-02-28 10:33:47.087	error	TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26
      systeminfo.0
      	2534	2022-02-28 10:33:47.084	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
      systeminfo.0
      	2534	2022-02-28 10:33:47.083	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      systeminfo.0
      	2534	2022-02-28 10:33:47.081	debug	Adapter systeminfo.0 starting.
      systeminfo.0
      	2534	2022-02-28 10:33:47.055	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2534	2022-02-28 10:33:47.055	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v14.19.0, js-controller: 4.0.15
      systeminfo.0
      	2534	2022-02-28 10:33:46.815	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2534	2022-02-28 10:33:46.815	debug	States connected to redis: 127.0.0.1:9000
      systeminfo.0
      	2534	2022-02-28 10:33:46.750	debug	States create User PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.750	debug	States create User PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.749	debug	States create System PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.749	debug	States create System PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.733	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2534	2022-02-28 10:33:46.733	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      systeminfo.0
      	2534	2022-02-28 10:33:46.702	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2534	2022-02-28 10:33:46.702	debug	Objects connected to redis: 127.0.0.1:9001
      systeminfo.0
      	2534	2022-02-28 10:33:46.695	debug	Objects client initialize lua scripts
      systeminfo.0
      	2534	2022-02-28 10:33:46.695	debug	Objects client initialize lua scripts
      systeminfo.0
      	2534	2022-02-28 10:33:46.648	debug	Objects create User PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.646	debug	Objects create System PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.648	debug	Objects create User PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.646	debug	Objects create System PubSub Client
      systeminfo.0
      	2534	2022-02-28 10:33:46.643	debug	Objects client ready ... initialize now
      systeminfo.0
      	2534	2022-02-28 10:33:46.643	debug	Objects client ready ... initialize now
      systeminfo.0
      	2534	2022-02-28 10:33:46.294	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      systeminfo.0
      	2534	2022-02-28 10:33:46.294	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      

      Habt ihr eine Idee? - Danke im Voraus.

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

        @smarthomer-0
        Sorry, ich habe grade erst gesehen, dass es bereits einen Hinweis auf das Problem mit dem Systeminfo-Adapter gibt.
        Insofern also für mich hier erledigt, bis es ein Adapter-Update gibt.

        ![0_1646047210958_0fcb9f13-a161-4722-b97e-1bfcbcd5ee61-grafik.png](Lade 100% hoch)
        @apollon77 sagte in js-controller 4.0.x jetzt für alle User im STABLE!:

        Nötige Adapter-Aktualisierungen
        Aktuell sind drei Adapter bekannt, welche aktualisiert werden müssen bzw. sollten:

        Backitup sollte auf 2.3.3+ aktualisiert sein, damit vor allem Restores mit js-controller 4 sauber funktionieren
        Admin sollte auf 5.3.1+ aktualisiert sein, damit alle Settings für den js-controller 4 korrekt editiert werden können
        Node-Red muss auf Verson 2.4.2 aktualisiert sein, da der Adapter sonst nicht funktioniert
        km200 (see https://github.com/frankjoke/ioBroker.km200/issues/69 Fix is described in https://forum.iobroker.net/post/760260
        systeminformation Am Ende der gleiche wie wie direkt oben drüber bei km200

        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @SmartHomer 0 last edited by

          @smarthomer-0 Naja die Lösung steht auch dort ... du musst /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js öffnen und dort in Zeile 44 das "object." vor dem getObjectList entfernen. Danach tut alles

          S Y Z P 4 Replies Last reply Reply Quote 0
          • S
            SmartHomer 0 @apollon77 last edited by

            @apollon77
            Hat wunderbar geklappt, Danke Dir 👍

            1 Reply Last reply Reply Quote 2
            • Y
              Yak55 @apollon77 last edited by

              Sorry, bei mir hat das Löschen von "object." vor dem getObjectList nicht geholfen. Hat ev. jemand ne Idee, woran es bei mir liegen könnte? ioBroker läuft auf einem Pi 3b+


              ioBroker-Pi

              Plattform linux
              Betriebssystem linux
              Architektur arm
              CPUs 4
              Geschwindigkeit 600 MHz
              Modell ARMv7 Processor rev 4 (v7l)
              RAM 926.08 MB
              System-Betriebszeit 00:41:02
              Node.js v14.19.0
              time 1646221338213
              timeOffset -60
              Anzahl der Adapter 400
              NPM 6.14.16
              Datenträgergröße 15.39 GB
              freier Festplattenspeicher 8.13 GB
              Betriebszeit 00:41:16
              Aktive Instanzen 15
              location /opt/iobroker/
              Hostname ioBroker-Pi

              Log sieht so aus:

              km200.0 2022-03-02 12:09:53.314 info Adapter km200 initialization finished with 0 states.
              km200.0 2022-03-02 12:09:53.287 info Slow Interval=6 hours, Slow-List:
              km200.0 2022-03-02 12:09:53.286 info Fast Interval=2 min, Fast-List:
              km200.0 2022-03-02 12:09:53.285 info Interval=15 min, Norm-list:
              km200.0 2022-03-02 12:09:53.282 info KM200 found 0 states, get their values now.
              km200.0 2022-03-02 12:09:53.280 info Services found: 41
              km200.0 2022-03-02 12:09:53.278 warn Did not get any Services from KLM200!: {}
              km200.0 2022-03-02 12:09:53.255 warn Skip service data of /system
              km200.0 2022-03-02 12:09:53.072 warn Skip service data of /solarCircuits
              km200.0 2022-03-02 12:09:52.891 warn Skip service data of /recordings
              km200.0 2022-03-02 12:09:52.701 warn Skip service data of /notifications
              km200.0 2022-03-02 12:09:52.701 warn Skip service data of /notifications
              km200.0 2022-03-02 12:09:52.527 warn Skip service data of /heatSources
              km200.0 2022-03-02 12:09:52.355 warn Skip service data of /heatingCircuits
              km200.0 2022-03-02 12:09:52.181 warn Skip service data of /gateway
              km200.0 2022-03-02 12:09:51.994 warn Skip service data of /dhwCircuits
              km200.0 2022-03-02 12:09:51.690 info km200.0 address: http://BuderusKM200.fritz.box
              km200.0 2022-03-02 12:09:51.686 info km200 initialization started...
              km200.0 2022-03-02 12:09:51.518 info starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.km200, node: v14.19.0, js-controller: 4.0.15
              host.ioBroker-Pi 2022-03-02 12:09:47.854 info instance system.adapter.km200.0 started with pid 1670
              host.ioBroker-Pi 2022-03-02 12:09:47.714 info "system.adapter.km200.0" enabled

              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @Yak55 last edited by

                @yak55 lesen bitte

                warn Did not get any Services from KLM200!: {}
                

                da meldet sich der km200 adapter ..

                Y 1 Reply Last reply Reply Quote 0
                • Y
                  Yak55 @arteck last edited by

                  @arteck - Danke für die Antwort, mich irritiert nur: info Services found: 41.....
                  Aber ich habe das Problem anderweitig gelöst, indem ich nun den ems-esp Adater nutze. Mit dem km200 hatte ich in den letzten Jahren schon häufiger Stress😀

                  K 1 Reply Last reply Reply Quote 0
                  • K
                    Kanumouse @Yak55 last edited by

                    @yak55
                    Auch bei mir läuft systeminfo nicht mehr.
                    Kann mir bitte jemmand noch die genaue Stelle aufzeigen, wo ich in myAdapter.js etwas streichen muss?
                    Ich hab die Stelle noch nicht genau gefunden, da mehrfach „this.getObjectList“ in dieser Datei steht.

                    apollon77 1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @Kanumouse last edited by

                      @kanumouse An sich solltest Du eine Fehlerzeile haben ala

                      2692 2022-02-28 10:35:20.019 error TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:400:28) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8223:26

                      Und da steht es genau ... im Falle von hier:

                      /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55

                      Dateiname:Zeile:Position-in-der-zeile

                      1 Reply Last reply Reply Quote 0
                      • K
                        Kanumouse last edited by

                        @apollon77

                        Ok, vielen Dank!
                        Ich hab's gefunden und jetzt läuft systeminfo wieder.

                        1 Reply Last reply Reply Quote 0
                        • binaryaddict
                          binaryaddict last edited by

                          @kanumouse said in Gelöst: Systeminfo-Adapter Probleme nach Update:

                          Ok, vielen Dank!
                          Ich hab's gefunden und jetzt läuft systeminfo wieder.

                          Was haste denn gemacht? Die referenzierte Datei ist ja scheinbar keine vom Benutzer erstellte Datei, sondern gehört zum Adapter. Die Problem-Zeile einfach auskommentieren?

                          apollon77 1 Reply Last reply Reply Quote 0
                          • apollon77
                            apollon77 @binaryaddict last edited by apollon77

                            @binaryaddict so, jetzt denk mal nach bitte und ließ in diesen thread mal von oben nach unten. Ich denke du wirst schon im zweiten post fündig und weiter unten steht’s noch genauer. Und ja genau das ist zu tun. Man muss eine Datei vom
                            Adapter ändern.

                            1 Reply Last reply Reply Quote 0
                            • Z
                              zizu29 @apollon77 last edited by

                              @apollon77
                              Wo muss ich da genau hin um dieses Objekt zu löschen , ich steh völlig auf dem schlauch

                              Homoran 1 Reply Last reply Reply Quote 0
                              • Homoran
                                Homoran Global Moderator Administrators @zizu29 last edited by

                                @zizu29 sagte in Gelöst: Systeminfo-Adapter Probleme nach Update:

                                Wo muss ich da genau hin um dieses Objekt zu löschen , i

                                @apollon77 sagte in Gelöst: Systeminfo-Adapter Probleme nach Update:

                                ließ in diesen thread mal von oben nach unten. Ich denke du wirst schon im zweiten post fündig und weiter unten steht’s noch genauer.

                                ich denke spätestens im dritten

                                Z 1 Reply Last reply Reply Quote 0
                                • Z
                                  zizu29 @Homoran last edited by

                                  @homoran gehe ich über putty ?

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    padi0-000 @apollon77 last edited by

                                    @apollon77 sagte in Gelöst: Systeminfo-Adapter Probleme nach Update:

                                    @smarthomer-0 Naja die Lösung steht auch dort ... du musst /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js öffnen und dort in Zeile 44 das "object." vor dem getObjectList entfernen. Danach tut alles

                                    Wie und womit öffne ich das ganze ?
                                    über Putty hat es nicht geklappt.

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @padi0-000 last edited by

                                      @padi0-000
                                      puTTY ist auch nur ein Terminal. Du musst die Datei schon editieren, geht z.B. mit
                                      nano

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

                                      Support us

                                      ioBroker
                                      Community Adapters
                                      Donate

                                      740
                                      Online

                                      31.8k
                                      Users

                                      79.9k
                                      Topics

                                      1.3m
                                      Posts

                                      10
                                      17
                                      2166
                                      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