Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Seltsame Abstürze RPI4

    NEWS

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    Seltsame Abstürze RPI4

    This topic has been deleted. Only users with topic management privileges can see it.
    • wendy2702
      wendy2702 @Uwe Waizmann last edited by

      @uwe-waizmann Was man so entziffern kann könnte es ein USB Problem sein.

      Die SSD würde ich mal an einen aktiven Hub anschließen wenn möglich und die Distanz zwischen SSD und PI vergrößern.

      Uwe Waizmann 1 Reply Last reply Reply Quote 0
      • Uwe Waizmann
        Uwe Waizmann @wendy2702 last edited by

        @wendy2702
        ich hab jetzt mal mit sd card kopier die ssd gewechselt

        Uwe Waizmann 1 Reply Last reply Reply Quote 0
        • Uwe Waizmann
          Uwe Waizmann @Uwe Waizmann last edited by

          @uwe-waizmann
          kurzer Zwischenbericht
          ssd wechsel hat auch nichts gebracht, 1 -3 Abstürze am Tag.
          Hab jetzt eine SD Card drin und läuft bis jetzt problemlos.

          Thomas Braun UncleSam 2 Replies Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Uwe Waizmann last edited by Thomas Braun

            @uwe-waizmann
            Mal beobachten. Aber ich denke der Controller ist für die SSD ist nicht geeignet.

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

              Ich hatte mal so ein lustiges Problem mit einer SSD als ich einen meiner Server aufgesetzt habe.

              Am Ende lag es am SATA Kabel in Kombi mit dieser Speziellen SSD.

              Neues Kabel und bei mir war es gut.

              1 Reply Last reply Reply Quote 0
              • UncleSam
                UncleSam Developer @Uwe Waizmann last edited by

                @uwe-waizmann sagte in Seltsame Abstürze RPI4:

                ssd wechsel hat auch nichts gebracht, 1 -3 Abstürze am Tag.
                Hab jetzt eine SD Card drin und läuft bis jetzt problemlos.

                Wie @Thomas-Braun wohl meinte: besser nicht SD verwenden, die wird dir auf einem Master relativ schnell flöten gehen.

                Was übrigens auch noch sein kann: vielleicht ist es auch einfach der Raspi. Auch dort kann ein Fehler sein, eine faule Komponente im USB Interface oder sonstwas...

                Uwe Waizmann 1 Reply Last reply Reply Quote 0
                • Uwe Waizmann
                  Uwe Waizmann @UncleSam last edited by

                  @unclesam
                  lief ohne Probleme mit der sd trotz extesiver nutzung.
                  Hab jetzt die SSD über einen Hub mit eigener Stromversorgung wieder dran, bin gespannt was passiert.

                  Uwe Waizmann 1 Reply Last reply Reply Quote 0
                  • Uwe Waizmann
                    Uwe Waizmann @Uwe Waizmann last edited by

                    @thomas-braun
                    Kurzer Zwischenbericht:
                    hatte zwei unterschiedliche SSD mit jeweils anderem Controler Kabel benutzt, war bei beiden das selbe.
                    Komisch war nur, dass die Abstürze immer morgens als ich an den PC ging kamen.
                    Jetzt SSD mit eigener Stromversorgung über HUB läuft alles noch im grünen Bereich.

                    Uwe Waizmann 1 Reply Last reply Reply Quote 0
                    • Uwe Waizmann
                      Uwe Waizmann @Uwe Waizmann last edited by

                      @thomas-braun
                      Ist gelaufen bis gestern.
                      Ich hab den Backitup aktualisiert, dann ging nichts mehr. Am angeschlossenen Monitor konnte ich htop beobachten wie der Average Load langsam anstiegt bis auf über 33.
                      Tastatur angesteckt ging auch nicht mehr.
                      Dann Stecker ziehen 😞

                      L 1 Reply Last reply Reply Quote 0
                      • wendy2702
                        wendy2702 last edited by

                        Wann ging nichts mehr?

                        Während des Upgrades oder als ein Backup erstellt wurde?

                        Warum dem System nicht einfach mal etwas Zeit gelassen anstelle gleich den Stecker zu ziehen?

                        Wenn der Windows PC mal nicht reagiert reißt Ihr den Stecker doch auch nicht sofort aus der Steckdose.

                        1 Reply Last reply Reply Quote 0
                        • Uwe Waizmann
                          Uwe Waizmann last edited by

                          @wendy2702
                          adapter aktualisieren, dann gewartet aber nichts mehr passiert, ausser Sanduhr

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

                            @uwe-waizmann

                            Einträge im log file?

                            1 Reply Last reply Reply Quote 0
                            • L
                              lobito @Uwe Waizmann last edited by

                              @uwe-waizmann

                              Und ich sage es nochmals, das 8GB Modell hat Probleme mit der Stromversorgung über das Original-NT besonders wenn der Lüfter und USB-Geräte angeschlossen sind. Das kann sich auch in fehlendem Strom für die CPU äussern (Undervolting... Last steigt).

                              jolic 1 Reply Last reply Reply Quote 0
                              • K
                                klassisch Most Active last edited by

                                Falls die Versorgung rocksolid ist:
                                Was für ein Filesystem ist auf den SSD? Sind die gecloned oder neu aufgesetzt?

                                1 Reply Last reply Reply Quote 0
                                • jolic
                                  jolic @lobito last edited by jolic

                                  @lobito said in Seltsame Abstürze RPI4:

                                  ... das 8GB Modell hat Probleme mit der Stromversorgung über das Original-NT ...

                                  Mhh, wo hast du denn diese Info her (Link?), meiner rennt mit dem Original-NT und externer SSD Platte (T5 von Samsung) ohne extra Stromversorgung problemlos. Dieses NT hat 5.1 Volt und liefert bis zu 3A. Im Prinzip könnte natürlich jedes Netzteil ein Produktionsfehler haben, daher würde ich einfach mal ein anderes USB-C Netzteil zum testen anschließen.

                                  1 Reply Last reply Reply Quote 0
                                  • L
                                    lobito last edited by

                                    Das Ihr immer nicht fähig seit selber etwas zu suchen. Nein von mir gibt es keinen Link und sei glücklich das es bei Dir funktioniert. Ich habe ingesamt 10 Raspis von 3 über 3+, 4 mit 2GB, 4 GB und 8 GB im Einsatz. Aber ok, Du hast vollkommen Recht alle meine Orginalnetzteile haben Produktionsfehler, so das es ausgerechnet beim 8 GB Modell zu Problemen mit der Stromversorgung kommt. Der Raspi zeigt es übrigens, ein blinken der roten LED heisst nicht das er arbeitet, sondern das er Probleme mit der Spannung hat. Und komischerweise konnte ich die mit einer 10 Euro Investition in ein Industrie-NT mit 20A Leistung beheben. Noch ein kleiner Lesetipp einige Artikel in c't Ausgaben des Jahres 2020 behandeln genau diesen Fall. Oder gehe doch mal in Homematic-Forum und schau was dort geschrieben wird. Ich bin nicht alleine.

                                    jolic 1 Reply Last reply Reply Quote 0
                                    • jolic
                                      jolic @lobito last edited by

                                      @lobito OK, dann ist es eben PAL und ich bin glücklich.

                                      Würde mich dennoch interessieren welches NT Uwe nutzt und ob ein anderes bei seinem Problem hilft.

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

                                        ich habe es eben schon in einem anderen Thread geschrieben:
                                        Neben dem Netzteil ist auch das USB-Kabel eine mögliche Schwachstelle!

                                        bei schlechten Kontakten und/oder unterdimensionierten Querschnitten kann es auch dort zu Spannungsabfällen aufgrund zu hoher Widerstände kommen.

                                        Uwe Waizmann 1 Reply Last reply Reply Quote 0
                                        • Uwe Waizmann
                                          Uwe Waizmann @Homoran last edited by

                                          Hallo Zusammen,
                                          sorry für die späte Meldung.
                                          Er lief jetzt eine Woche ohne Probleme und heute Morgen war es wieder soweit.
                                          Netzteil ist das Originale mit 3A.
                                          SSD hängt an einem Hub mit eigenem Netzteil.
                                          Sonst ist nichts angeschlossen.
                                          Das System ist ein Image von Raspberry. Zusätzlich habe ich ein emoncms installiert weil da gleich der mosquitto und die DB mit dabei waren.
                                          Um 7:38 habe ich kurz mit der App drauf geschaut, als ich dann an den PC ging und das Browserfenster mit der VIS aktualisierte war Ende.
                                          Habe bis jetzt noch kein alternatives Netzteil gefunden, da fehlt mir vermutlich das notwendige Wissen. Vielleicht kann mir jemand einen Link zu einem Industrienetzteil geben um auch diese mögliche Fehlerquelle auszuschließen.
                                          Ich habe den Monitor kurz angesteckt und folgendes gesehen20210413_080522[1].jpg

                                          Hier noch der Log nach dem Neustart

                                          web.0	2021-04-13 08:18:33.917	info	(9617) <==Disconnect system.user.admin from ::ffff:192.168.1.30
                                          web.0	2021-04-13 08:16:13.247	info	(9617) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0
                                          web.0	2021-04-13 08:16:09.205	info	(9617) ==>Connected system.user.admin from ::ffff:192.168.1.30
                                          web.0	2021-04-13 08:16:04.070	info	(9617) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0
                                          web.0	2021-04-13 08:16:03.936	info	(9617) ==>Connected system.user.admin from ::ffff:192.168.1.30
                                          web.0	2021-04-13 08:16:03.920	info	(9617) ==>Connected system.user.admin from ::ffff:192.168.1.30
                                          web.0	2021-04-13 08:15:02.506	info	(9617) <==Disconnect system.user.admin from ::ffff:192.168.1.26 vis.0
                                          sonoff.0	2021-04-13 08:12:57.494	info	(8244) Client [wama] connected with secret 1618294377493_3335
                                          sonoff.0	2021-04-13 08:12:52.883	info	(8244) Client [Steckdose12] connected with secret 1618294372882_624
                                          sonoff.0	2021-04-13 08:12:42.897	info	(8244) Client [WekstattTemp] connected with secret 1618294362896_1744
                                          sonoff.0	2021-04-13 08:12:38.788	info	(8244) Client [Terrasse_lux_led] connected with secret 1618294358787_4888
                                          sonoff.0	2021-04-13 08:12:38.713	info	(8244) Client [Schalter-TV] connected with secret 1618294358711_1656
                                          sonoff.0	2021-04-13 08:12:38.103	info	(8244) Client [Temp2-DS18B20] connected with secret 1618294358100_1086
                                          sonoff.0	2021-04-13 08:12:34.267	info	(8244) Client [Buero_Temp] connected with secret 1618294354259_2159
                                          web.0	2021-04-13 08:12:34.031	info	(9617) ==>Connected system.user.admin from ::ffff:192.168.1.26
                                          web.0	2021-04-13 08:12:32.426	info	(9617) ==>Connected system.user.admin from ::ffff:192.168.1.26
                                          cloud.0	2021-04-13 08:12:29.841	info	(4454) Connection changed: connect
                                          cloud.0	2021-04-13 08:12:29.684	info	(4454) Trying to connect as system.user.admin
                                          web.0	2021-04-13 08:12:26.736	info	(9617) http server listening on port 8082
                                          web.0	2021-04-13 08:12:26.728	info	(9617) Allow states only when user is owner: false
                                          web.0	2021-04-13 08:12:26.727	info	(9617) simpleAPI server listening on port 8082
                                          web.0	2021-04-13 08:12:26.717	info	(9617) socket.io server listening on port 8082
                                          web.0	2021-04-13 08:12:26.440	info	(9617) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:12:24.423	info	instance system.adapter.web.0 started with pid 9617
                                          shelly.0	2021-04-13 08:12:21.049	info	(7972) Shelly device 192.168.1.127 (shelly1 / shelly1-F4CFA2E46301 / SHSW-1#F4CFA2E46301#1) with CoAP connected! Polltime set to 5 sec.
                                          shelly.0	2021-04-13 08:12:19.447	info	(7972) Shelly device 192.168.1.123 (shellyswitch25 / shellyswitch25-84CCA8B0CC8F / SHSW-25#84CCA8B0CC8F#1) with CoAP connected! Polltime set to 5 sec.
                                          telegram.1	2021-04-13 08:12:17.962	info	(8962) starting. Version 1.8.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:12:15.786	info	instance system.adapter.telegram.1 started with pid 8962
                                          shelly.0	2021-04-13 08:12:15.117	info	(7972) Shelly device 192.168.1.131 (shellydimmer2 / shellydimmer2-40F520015E03 / SHDM-2#40F520015E03#1) with CoAP connected! Polltime set to 5 sec.
                                          telegram.0	2021-04-13 08:12:14.777	info	(8645) starting. Version 1.8.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v12.22.0, js-controller: 3.2.16
                                          shelly.0	2021-04-13 08:12:14.190	info	(7972) Shelly device 192.168.1.128 (shelly1 / shelly1-8CAAB5614D9F / SHSW-1#8CAAB5614D9F#1) with CoAP connected! Polltime set to 5 sec.
                                          shelly.0	2021-04-13 08:12:13.171	info	(7972) Shelly device 192.168.1.126 (shelly1 / shelly1-483FDA91AF1A / SHSW-1#483FDA91AF1A#1) with CoAP connected! Polltime set to 5 sec.
                                          host.whome	2021-04-13 08:12:12.258	info	instance system.adapter.telegram.0 started with pid 8645
                                          sonoff.0	2021-04-13 08:12:09.432	info	(8244) Starting MQTT server on port 1884
                                          sonoff.0	2021-04-13 08:12:09.313	info	(8244) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.sonoff, node: v12.22.0, js-controller: 3.2.16
                                          shelly.0	2021-04-13 08:12:08.889	info	(7972) Shelly device 192.168.1.125 (shelly1 / shelly1-483FDA6F6EBC / SHSW-1#483FDA6F6EBC#1) with CoAP connected! Polltime set to 5 sec.
                                          shelly.0	2021-04-13 08:12:07.865	info	(7972) Shelly device 192.168.1.122 (shellyswitch25 / shellyswitch25-483FDA8DDD51 / SHSW-25#483FDA8DDD51#1) with CoAP connected! Polltime set to 5 sec.
                                          shelly.0	2021-04-13 08:12:07.745	info	(7972) Shelly device 192.168.1.121 (shellyswitch25 / shellyswitch25-84CCA8B09E95 / SHSW-25#84CCA8B09E95#1) with CoAP connected! Polltime set to 5 sec.
                                          shelly.0	2021-04-13 08:12:07.451	info	(7972) Shelly device 192.168.1.120 (shellyswitch25 / shellyswitch25-483FDA8DCC8E / SHSW-25#483FDA8DCC8E#1) with CoAP connected! Polltime set to 5 sec.
                                          host.whome	2021-04-13 08:12:07.196	info	instance system.adapter.sonoff.0 started with pid 8244
                                          shelly.0	2021-04-13 08:12:06.390	info	(7972) Listening for Shelly packets in the network
                                          shelly.0	2021-04-13 08:12:06.311	info	(7972) Starting Shelly adapter in CoAP modus.
                                          shelly.0	2021-04-13 08:12:06.272	info	(7972) Starting Adapter shelly.0 in version 4.0.7
                                          shelly.0	2021-04-13 08:12:06.239	info	(7972) starting. Version 4.0.7 in /opt/iobroker/node_modules/iobroker.shelly, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:12:03.910	info	instance system.adapter.shelly.0 started with pid 7972
                                          node-red.0	2021-04-13 08:12:03.878	warn	(7231) 13 Apr 08:12:03 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
                                          ping.0	2021-04-13 08:12:00.907	info	(7572) starting. Version 1.4.12 in /opt/iobroker/node_modules/iobroker.ping, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:59.113	info	instance system.adapter.ping.0 started with pid 7572
                                          node-red.0	2021-04-13 08:11:57.262	info	(7231) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
                                          node-red.0	2021-04-13 08:11:56.836	info	(7231) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v12.22.0, js-controller: 3.2.16
                                          javascript.0	2021-04-13 08:11:55.569	info	(6679) script.js.common.Temperaturen.aussen: registered 2 subscriptions and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.563	info	(6679) Start javascript script.js.common.Temperaturen.aussen
                                          javascript.0	2021-04-13 08:11:55.562	info	(6679) script.js.common.Temperaturen.temp2: registered 3 subscriptions and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.555	info	(6679) Start javascript script.js.common.Temperaturen.temp2
                                          javascript.0	2021-04-13 08:11:55.555	info	(6679) script.js.common.Buero.heizung_buero_boden: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.549	info	(6679) Start javascript script.js.common.Buero.heizung_buero_boden
                                          javascript.0	2021-04-13 08:11:55.548	info	(6679) script.js.rebootPi: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.542	info	(6679) Start javascript script.js.rebootPi
                                          javascript.0	2021-04-13 08:11:55.542	info	(6679) script.js.common.Wohnzimmer.Wohnzimmer: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.536	info	(6679) Start javascript script.js.common.Wohnzimmer.Wohnzimmer
                                          javascript.0	2021-04-13 08:11:55.438	info	(6679) script.js.common.Scripte.wama2: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.432	info	(6679) Start javascript script.js.common.Scripte.wama2
                                          javascript.0	2021-04-13 08:11:55.431	info	(6679) script.js.common.Scripte.Terasse_LED_stripe: registered 1 subscription and 1 schedule
                                          javascript.0	2021-04-13 08:11:55.425	info	(6679) Start javascript script.js.common.Scripte.Terasse_LED_stripe
                                          javascript.0	2021-04-13 08:11:55.424	info	(6679) script.js.common.Scripte.Tag: registered 0 subscriptions and 2 schedules
                                          javascript.0	2021-04-13 08:11:55.417	info	(6679) Start javascript script.js.common.Scripte.Tag
                                          javascript.0	2021-04-13 08:11:55.417	info	(6679) script.js.common.Scripte.Gute-Nacht: registered 2 subscriptions and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.411	info	(6679) Start javascript script.js.common.Scripte.Gute-Nacht
                                          javascript.0	2021-04-13 08:11:55.411	info	(6679) script.js.common.Scripte.Flur: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.406	info	(6679) Start javascript script.js.common.Scripte.Flur
                                          javascript.0	2021-04-13 08:11:55.405	info	(6679) script.js.common.Scripte.Anwesenheit: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.400	info	(6679) Start javascript script.js.common.Scripte.Anwesenheit
                                          javascript.0	2021-04-13 08:11:55.399	info	(6679) script.js.common.Rolladen.RolladenAutomatik: registered 4 subscriptions and 2 schedules
                                          javascript.0	2021-04-13 08:11:55.388	info	(6679) Start javascript script.js.common.Rolladen.RolladenAutomatik
                                          javascript.0	2021-04-13 08:11:55.387	info	(6679) script.js.common.Rolladen.Rolladen: registered 1 subscription and 0 schedules
                                          javascript.0	2021-04-13 08:11:55.381	info	(6679) Start javascript script.js.common.Rolladen.Rolladen
                                          javascript.0	2021-04-13 08:11:55.380	info	(6679) script.js.common.Heizung.Heizstab: registered 1 subscription and 1 schedule
                                          javascript.0	2021-04-13 08:11:55.370	info	(6679) Start javascript script.js.common.Heizung.Heizstab
                                          javascript.0	2021-04-13 08:11:55.369	info	(6679) script.js.common.Heizung.Auftau: registered 1 subscription and 1 schedule
                                          javascript.0	2021-04-13 08:11:55.282	info	(6679) Start javascript script.js.common.Heizung.Auftau
                                          host.whome	2021-04-13 08:11:55.465	info	instance system.adapter.node-red.0 started with pid 7231
                                          javascript.0	2021-04-13 08:11:55.193	info	(6679) received all states
                                          javascript.0	2021-04-13 08:11:55.183	info	(6679) received all objects
                                          javascript.0	2021-04-13 08:11:54.539	info	(6679) requesting all objects
                                          javascript.0	2021-04-13 08:11:54.537	info	(6679) requesting all states
                                          javascript.0	2021-04-13 08:11:54.292	info	(6679) starting. Version 5.0.14 in /opt/iobroker/node_modules/iobroker.javascript, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:54.396	info	Restart adapter system.adapter.web.0 because enabled
                                          host.whome	2021-04-13 08:11:54.396	error	instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          host.whome	2021-04-13 08:11:52.436	info	instance system.adapter.vis.0 terminated while should be started once
                                          vis.0	2021-04-13 08:11:51.760	info	(6258) Terminated (NO_ERROR): Without reason
                                          host.whome	2021-04-13 08:11:51.555	info	instance system.adapter.web.0 started with pid 6922
                                          host.whome	2021-04-13 08:11:50.953	info	instance system.adapter.mqtt.0 started with pid 6883
                                          vis.0	2021-04-13 08:11:50.244	info	(6258) vis license is OK.
                                          vis.0	2021-04-13 08:11:49.813	info	(6258) starting. Version 1.3.4 in /opt/iobroker/node_modules/iobroker.vis, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:49.450	info	instance system.adapter.javascript.0 started with pid 6679
                                          info.0	2021-04-13 08:11:46.634	info	(5887) starting. Version 1.7.14 in /opt/iobroker/node_modules/iobroker.info, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:45.768	info	Restart adapter system.adapter.telegram.1 because enabled
                                          host.whome	2021-04-13 08:11:45.767	error	instance system.adapter.telegram.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          host.whome	2021-04-13 08:11:43.955	info	instance system.adapter.info.0 started with pid 5887
                                          host.whome	2021-04-13 08:11:43.227	info	instance system.adapter.telegram.1 started with pid 5820
                                          host.whome	2021-04-13 08:11:42.217	info	Restart adapter system.adapter.telegram.0 because enabled
                                          host.whome	2021-04-13 08:11:42.217	error	instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          followthesun.0	2021-04-13 08:11:40.834	info	(5468) Daily sun parameter calculation scheduled for 00:00:31
                                          followthesun.0	2021-04-13 08:11:40.831	info	(5468) Sun position calculation will be done every 120 seconds
                                          followthesun.0	2021-04-13 08:11:40.795	info	(5468) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.followthesun, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:39.210	info	instance system.adapter.telegram.0 started with pid 5499
                                          host.whome	2021-04-13 08:11:38.956	info	instance system.adapter.followthesun.0 started with pid 5468
                                          fb-checkpresence.0	2021-04-13 08:11:37.513	info	(5128) createMemberObjects finished successfully
                                          fb-checkpresence.0	2021-04-13 08:11:37.513	info	(5128) History function for Elke J3 disabled. Please select a history adapter in the configuration dialog!
                                          fb-checkpresence.0	2021-04-13 08:11:37.479	info	(5128) History function for Elke disabled. Please select a history adapter in the configuration dialog!
                                          fb-checkpresence.0	2021-04-13 08:11:37.237	info	(5128) History function for Uwe disabled. Please select a history adapter in the configuration dialog!
                                          fb-checkpresence.0	2021-04-13 08:11:37.162	info	(5128) createGlobalObjects finished successfully
                                          host.whome	2021-04-13 08:11:37.160	info	Restart adapter system.adapter.sonoff.0 because enabled
                                          host.whome	2021-04-13 08:11:37.159	error	instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          fb-checkpresence.0	2021-04-13 08:11:36.987	info	(5128) service DeviceConfig1-Reboot is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.974	info	(5128) service X_AVM-DE_HostFilter-GetWANAccessByIP is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.961	info	(5128) service X_AVM-DE_HostFilter-DisallowWANAccessByIP is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.949	info	(5128) service DeviceInfo1-GetInfo is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.936	info	(5128) service WLANConfiguration3-GetInfo is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.921	info	(5128) service WLANConfiguration3-SetEnable is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.906	info	(5128) service WANPPPConnection1-GetInfo is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.891	info	(5128) service DeviceInfo1-GetSecurityPort is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.879	info	(5128) service Hosts1-X_AVM-DE_GetSpecificHostEntryByIP is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.864	info	(5128) service Hosts1-GetSpecificHostEntry is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.851	info	(5128) service Hosts1-X_AVM-DE_GetMeshListPath is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.835	info	(5128) service Hosts1-X_AVM-DE_GetHostListPath is supported
                                          fb-checkpresence.0	2021-04-13 08:11:36.647	info	(5128) start fb-checkpresence: ip-address: "192.168.1.10" - interval devices: 1 Min. - interval members: 60 s
                                          fb-checkpresence.0	2021-04-13 08:11:36.614	info	(5128) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.fb-checkpresence, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:35.222	info	instance system.adapter.sonoff.0 started with pid 5147
                                          host.whome	2021-04-13 08:11:35.091	info	instance system.adapter.fb-checkpresence.0 started with pid 5128
                                          host.whome	2021-04-13 08:11:33.867	info	Restart adapter system.adapter.shelly.0 because enabled
                                          host.whome	2021-04-13 08:11:33.866	error	instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          discovery.0	2021-04-13 08:11:32.735	info	(4754) starting. Version 2.6.1 in /opt/iobroker/node_modules/iobroker.discovery, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:31.239	info	instance system.adapter.shelly.0 started with pid 4783
                                          host.whome	2021-04-13 08:11:30.960	info	instance system.adapter.discovery.0 started with pid 4754
                                          cloud.0	2021-04-13 08:11:29.670	info	(4454) Adapter redirected temporally to "https://iobroker.net:10556" in one minute. Reason: command from server
                                          cloud.0	2021-04-13 08:11:29.527	info	(4454) Trying to connect as system.user.admin
                                          cloud.0	2021-04-13 08:11:29.276	info	(4454) Connecting with https://iobroker.net:10555 with "uwaizmann@gmail.com_c9f2a840-75ac-11eb-a278-59b6a78c6ee1"
                                          cloud.0	2021-04-13 08:11:29.205	info	(4454) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.cloud, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:29.089	info	Restart adapter system.adapter.ping.0 because enabled
                                          host.whome	2021-04-13 08:11:29.088	error	instance system.adapter.ping.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          host.whome	2021-04-13 08:11:27.258	info	instance system.adapter.cloud.0 started with pid 4454
                                          host.whome	2021-04-13 08:11:27.223	info	instance system.adapter.ping.0 started with pid 4448
                                          backitup.0	2021-04-13 08:11:26.159	info	(4021) [iobroker] backup was activated at 03:00 every 1 day(s)
                                          backitup.0	2021-04-13 08:11:26.081	info	(4021) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:25.429	info	Restart adapter system.adapter.node-red.0 because enabled
                                          host.whome	2021-04-13 08:11:25.428	error	instance system.adapter.node-red.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          chromecast.0	2021-04-13 08:11:25.372	info	(4101) Wohnzimmer - Connected client
                                          chromecast.0	2021-04-13 08:11:25.362	info	(4101) - Connected client
                                          chromecast.0	2021-04-13 08:11:24.952	error	(4101) The id is empty! Please provide a valid id. at Adapter.setObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1846:40) at ChromecastDevice._createObjects (/opt/iobr
                                          chromecast.0	2021-04-13 08:11:24.506	info	(4101) starting. Version 2.3.1 in /opt/iobroker/node_modules/iobroker.chromecast, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:23.212	info	instance system.adapter.node-red.0 started with pid 4132
                                          host.whome	2021-04-13 08:11:22.892	info	instance system.adapter.chromecast.0 started with pid 4101
                                          host.whome	2021-04-13 08:11:21.935	info	instance system.adapter.backitup.0 started with pid 4021
                                          host.whome	2021-04-13 08:11:20.916	info	Restart adapter system.adapter.mqtt.0 because enabled
                                          host.whome	2021-04-13 08:11:20.915	error	instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          mqtt.0	2021-04-13 08:11:20.343	error	(3805) mqtt.0 already running
                                          admin.0	2021-04-13 08:11:19.283	info	(3508) Use link "http://localhost:8081" to configure.
                                          host.whome	2021-04-13 08:11:19.416	info	Restart adapter system.adapter.javascript.0 because enabled
                                          host.whome	2021-04-13 08:11:19.415	error	instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          admin.0	2021-04-13 08:11:19.282	info	(3508) http server listening on port 8081
                                          host.whome	2021-04-13 08:11:19.201	info	instance system.adapter.mqtt.0 started with pid 3805
                                          admin.0	2021-04-13 08:11:19.026	info	(3508) received all objects
                                          javascript.0	2021-04-13 08:11:18.807	warn	(3453) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          javascript.0	2021-04-13 08:11:18.804	error	(3453) javascript.0 already running
                                          admin.0	2021-04-13 08:11:18.076	info	(3508) requesting all objects
                                          admin.0	2021-04-13 08:11:18.075	info	(3508) requesting all states
                                          admin.0	2021-04-13 08:11:18.017	info	(3508) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v12.22.0, js-controller: 3.2.16
                                          host.whome	2021-04-13 08:11:15.819	info	instance system.adapter.admin.0 started with pid 3508
                                          host.whome	2021-04-13 08:11:15.221	info	instance system.adapter.javascript.0 started with pid 3453
                                          host.whome	2021-04-13 08:11:13.933	info	Restart adapter system.adapter.info.0 because enabled
                                          host.whome	2021-04-13 08:11:13.932	error	instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          info.0	2021-04-13 08:11:13.350	warn	(3118) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          info.0	2021-04-13 08:11:13.346	error	(3118) info.0 already running
                                          host.whome	2021-04-13 08:11:11.235	info	instance system.adapter.info.0 started with pid 3118
                                          host.whome	2021-04-13 08:11:08.936	info	Restart adapter system.adapter.followthesun.0 because enabled
                                          host.whome	2021-04-13 08:11:08.936	error	instance system.adapter.followthesun.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          followthesun.0	2021-04-13 08:11:08.365	warn	(2770) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          followthesun.0	2021-04-13 08:11:08.362	error	(2770) followthesun.0 already running
                                          host.whome	2021-04-13 08:11:07.203	info	instance system.adapter.followthesun.0 started with pid 2770
                                          host.whome	2021-04-13 07:38:24.000	info	Restart adapter system.adapter.fb-checkpresence.0 because enabled
                                          host.whome	2021-04-13 07:38:24.000	error	instance system.adapter.fb-checkpresence.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          fb-checkpresence.0	2021-04-13 07:38:23.427	warn	(2397) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          fb-checkpresence.0	2021-04-13 07:38:23.425	error	(2397) fb-checkpresence.0 already running
                                          host.whome	2021-04-13 07:38:22.137	info	instance system.adapter.fb-checkpresence.0 started with pid 2397
                                          host.whome	2021-04-13 07:38:19.864	info	Restart adapter system.adapter.discovery.0 because enabled
                                          host.whome	2021-04-13 07:38:19.864	error	instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          discovery.0	2021-04-13 07:38:19.287	warn	(2048) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          discovery.0	2021-04-13 07:38:19.285	error	(2048) discovery.0 already running
                                          host.whome	2021-04-13 07:38:18.182	info	instance system.adapter.discovery.0 started with pid 2048
                                          host.whome	2021-04-13 07:38:16.153	info	Restart adapter system.adapter.cloud.0 because enabled
                                          host.whome	2021-04-13 07:38:16.152	error	instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          cloud.0	2021-04-13 07:38:15.581	warn	(1688) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          cloud.0	2021-04-13 07:38:15.578	error	(1688) cloud.0 already running
                                          host.whome	2021-04-13 07:38:14.181	info	instance system.adapter.cloud.0 started with pid 1688
                                          host.whome	2021-04-13 07:38:11.810	info	Restart adapter system.adapter.chromecast.0 because enabled
                                          host.whome	2021-04-13 07:38:11.809	error	instance system.adapter.chromecast.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          host.whome	2021-04-13 07:38:11.809	error	Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:97:5)
                                          host.whome	2021-04-13 07:38:11.809	error	Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25)
                                          host.whome	2021-04-13 07:38:11.808	error	Caught by controller[0]: at process.exit (internal/process/per_thread.js:168:15)
                                          host.whome	2021-04-13 07:38:11.808	error	Caught by controller[0]: at process.emit (events.js:314:20)
                                          host.whome	2021-04-13 07:38:11.808	error	Caught by controller[0]: at Object.onceWrapper (events.js:421:26)
                                          host.whome	2021-04-13 07:38:11.807	error	Caught by controller[0]: at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8620:22)
                                          host.whome	2021-04-13 07:38:11.807	error	Caught by controller[0]: at Adapter.emit (events.js:314:20)
                                          host.whome	2021-04-13 07:38:11.806	error	Caught by controller[0]: at Adapter.unload (/opt/iobroker/node_modules/iobroker.chromecast/main.js:79:19)
                                          host.whome	2021-04-13 07:38:11.805	error	Caught by controller[0]: TypeError: Cannot read property 'info' of undefined
                                          chromecast.0	2021-04-13 07:38:11.225	warn	(1374) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          chromecast.0	2021-04-13 07:38:11.223	error	(1374) chromecast.0 already running
                                          host.whome	2021-04-13 07:38:10.842	info	Restart adapter system.adapter.backitup.0 because enabled
                                          host.whome	2021-04-13 07:38:10.841	error	instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          backitup.0	2021-04-13 07:38:10.235	warn	(1019) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          backitup.0	2021-04-13 07:38:10.232	error	(1019) backitup.0 already running
                                          host.whome	2021-04-13 07:38:10.106	info	instance system.adapter.chromecast.0 started with pid 1374
                                          host.whome	2021-04-13 07:38:06.122	info	instance system.adapter.backitup.0 started with pid 1019
                                          host.whome	2021-04-13 07:38:04.741	info	Restart adapter system.adapter.admin.0 because enabled
                                          host.whome	2021-04-13 07:38:04.740	error	instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                                          admin.0	2021-04-13 07:38:04.144	warn	(832) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                                          admin.0	2021-04-13 07:38:04.140	error	(832) admin.0 already running
                                          host.whome	2021-04-13 07:38:02.205	info	instance system.adapter.admin.0 started with pid 832
                                          host.whome	2021-04-13 07:38:02.075	info	starting 18 instances
                                          host.whome	2021-04-13 07:38:02.026	info	25 instances found
                                          host.whome	2021-04-13 07:38:01.395	info	added notifications configuration of host
                                          host.whome	2021-04-13 07:38:01.331	info	connected to Objects and States
                                          host.whome-Server	2021-04-13 07:38:01.179	error	Cannot load /opt/iobroker/iobroker-data/states.json: /opt/iobroker/iobroker-data/states.json: Unexpected end of JSON input. Try last Backup!
                                          host.whome	2021-04-13 07:38:00.706	info	ip addresses: fe80::dea6:32ff:feee:ba65
                                          host.whome	2021-04-13 07:38:00.705	info	hostname: whome, node: v12.22.0
                                          host.whome	2021-04-13 07:38:00.705	info	Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                          host.whome	2021-04-13 07:38:00.699	info	iobroker.js-controller version 3.2.16 js-controller starting
                                          web.0	2021-04-13 07:54:20.852	info	(5925) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0
                                          web.0	2021-04-13 07:53:32.305	info	(5925) <==Disconnect system.user.admin from ::ffff:192.168.1.30 vis.0
                                          web.0	2021-04-13 07:51:40.244	info	(5925) ==>Connected system.user.admin from ::ffff:192.168.1.30
                                          web.0	2021-04-13 07:51:02.247	info	(5925) ==>Connected system.user.admin from ::ffff:192.168.1.30
                                          javascript.0	2021-04-13 06:07:48.692	info	(22433) script.js.common.Heizung.Heizstab: HeizStab AUS
                                          javascript.0	2021-04-13 06:07:48.690	info	(22433) script.js.common.Heizung.Auftau: Auftau Aus
                                          javascript.0	2021-04-13 05:35:38.279	info	(22433) script.js.common.Heizung.Heizstab: HeizStab AUS
                                          javascript.0	2021-04-13 05:35:38.278	info	(22433) script.js.common.Heizung.Auftau: Auftau Aus
                                          chromecast.0	2021-04-13 04:48:42.703	info	(24407) - Connected client
                                          chromecast.0	2021-04-13 04:48:41.679	info	(24407) Wohnzimmer - Connected client
                                          chromecast.0	2021-04-13 04:48:40.767	info	(24407) Reconnecting Wohnzimmer to 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:40.766	info	(24407) Received keep alive for disconnected device Wohnzimmer
                                          chromecast.0	2021-04-13 04:48:37.666	warn	at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
                                          chromecast.0	2021-04-13 04:48:37.666	warn	(24407) Wohnzimmer - Client error: Error: read ECONNRESET
                                          chromecast.0	2021-04-13 04:48:37.665	warn	at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
                                          chromecast.0	2021-04-13 04:48:37.665	warn	(24407) - Client error: Error: read ECONNRESET
                                          chromecast.0	2021-04-13 04:48:33.653	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:33.653	warn	(24407) Wohnzimmer - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:33.651	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:33.651	warn	(24407) - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:30.626	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:30.626	warn	(24407) Wohnzimmer - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:30.625	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:30.625	warn	(24407) - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:28.601	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:28.601	warn	(24407) Wohnzimmer - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:28.599	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:28.599	warn	(24407) - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:27.551	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:27.551	warn	(24407) Wohnzimmer - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:27.550	warn	at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
                                          chromecast.0	2021-04-13 04:48:27.550	warn	(24407) - Client error: Error: connect ECONNREFUSED 192.168.1.25:8009
                                          chromecast.0	2021-04-13 04:48:24.428	info	(24407) Wohnzimmer - client disconnected
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at processTimers (internal/timers.js:497:7)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at listOnTimeout (internal/timers.js:554:17)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at fn.emit (events.js:314:20)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at Object.onceWrapper (events.js:420:28)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26)
                                          chromecast.0	2021-04-13 04:48:24.427	warn	(24407) Wohnzimmer - Client error: Error: Device timeout
                                          chromecast.0	2021-04-13 04:48:24.425	info	(24407) - client disconnected
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at processTimers (internal/timers.js:497:7)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at listOnTimeout (internal/timers.js:554:17)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at fn.emit (events.js:314:20)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at Object.onceWrapper (events.js:420:28)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26)
                                          chromecast.0	2021-04-13 04:48:24.417	warn	(24407) - Client error: Error: Device timeout
                                          javascript.0	2021-04-13 04:39:57.468	info	(22433) script.js.common.Heizung.Heizstab: HeizStab AUS
                                          javascript.0	2021-04-13 04:39:57.468	info	(22433) script.js.common.Heizung.Auftau: Auftau Aus
                                          
                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @Uwe Waizmann last edited by Thomas Braun

                                            @uwe-waizmann sagte in Seltsame Abstürze RPI4:

                                            Kernel Panic.
                                            Warum auch immer.
                                            Schau in das kernel.log / sys.log und in

                                            dmesg -T
                                            

                                            rein.

                                            Wer sagt eigentlich, dass nicht emoncms der Verursacher ist?
                                            Aus deren ReadMe:

                                            It is strongly recommended that you dedicate a single device (NUC/VM/Pi) to emoncms. Using it alongside other software can prove problematic.

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

                                            Support us

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

                                            498
                                            Online

                                            32.0k
                                            Users

                                            80.5k
                                            Topics

                                            1.3m
                                            Posts

                                            10
                                            69
                                            4073
                                            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