Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Crash - no connection to states 0.0.0.0:6370[redis]

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    Crash - no connection to states 0.0.0.0:6370[redis]

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators last edited by

      @Thomas-Braun

      bis hierhin sah es noch gut aus
      2021-12-20 20:25:06.270 - info: host.raspberrypi received SIGTERM

      Wo kommt da der SIGTERM auf einmal her

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

        @homoran
        gute Frage
        bekommt er den durch den "iob fix"?

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

          @sirfauntleroy
          Möglich. Vor dem fix stoppt man den iobroker ja. Das wird dann wohl per SIGTERM passieren.

          Homoran 1 Reply Last reply Reply Quote 0
          • F
            fastfoot @Homoran last edited by

            @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

            Wo kommt da der SIGTERM auf einmal her

            später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

            Homoran 1 Reply Last reply Reply Quote 1
            • Homoran
              Homoran Global Moderator Administrators @Thomas Braun last edited by

              @thomas-braun sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

              Möglich. Vor dem fix stoppt man den iobroker ja. Das wird dann wohl per SIGTERM passieren.

              passt, aber dass er dann nach dem Fixer nicht mehr hochkommt ist schon seltsam

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

                @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                Wo kommt da der SIGTERM auf einmal her

                später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                DANKE!!!

                Schon wieder mal nicht gesehen - gestern erst

                F 1 Reply Last reply Reply Quote 0
                • F
                  fastfoot @Homoran last edited by

                  @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  Wo kommt da der SIGTERM auf einmal her

                  später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                  DANKE!!!

                  Schon wieder mal nicht gesehen - gestern erst

                  sieht man auch an list instances, die zeigen noch auf raspberrypi

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

                    @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                    sieht man auch an list instances, die zeigen noch auf raspberrypi

                    ja, die Spalte blende ich immer irgendwie aus 😳 😞

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

                      @homoran
                      21f7498b-b4a0-4882-8454-5033b71f6c02-image.png
                      das Fenster bleibt jetzt so, bis alles wiederhergestellt ist?

                      einfach mal so laufen lassen. ... kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                      Homoran Thomas Braun 2 Replies Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @Sirfauntleroy last edited by Homoran

                        @sirfauntleroy sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                        kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                        iobroker logs --watch zeigt dir die Aktivitäten

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

                          @sirfauntleroy
                          Konsole auf, per

                          iobroker logs --watch
                          

                          den Fortgang beobachten

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

                            will nicht ungeduldig sein, aber ist es normal, dass der Start des Backup-Resores nicht im log steht?

                            iobroker logs --watch
                            2021-12-20 21:04:34.397  - info: host.raspberrypi iobroker.js-controller version 3.3.21 js-controller starting
                            2021-12-20 21:04:34.403  - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                            2021-12-20 21:04:34.404  - info: host.raspberrypi hostname: raspberrypi, node: v14.18.2
                            2021-12-20 21:04:34.404  - info: host.raspberrypi ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                            2021-12-20 21:04:34.601  - info: host.raspberrypi connected to Objects and States
                            2021-12-20 21:04:34.667  - info: host.raspberrypi added notifications configuration of host
                            2021-12-20 21:04:34.987  - info: host.raspberrypi 3 instances found
                            2021-12-20 21:04:34.999  - info: host.raspberrypi starting 3 instances
                            2021-12-20 21:04:35.052  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 7454
                            2021-12-20 21:04:37.005  - info: admin.0 (7454) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:37.054  - info: admin.0 (7454) requesting all states
                            2021-12-20 21:04:37.055  - info: admin.0 (7454) requesting all objects
                            2021-12-20 21:04:37.135  - info: admin.0 (7454) received all objects
                            2021-12-20 21:04:37.231  - info: admin.0 (7454) http server listening on port 8081
                            2021-12-20 21:04:37.231  - info: admin.0 (7454) Use link "http://localhost:8081" to configure.
                            2021-12-20 21:04:37.268  - info: admin.0 (7454) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string"
                            2021-12-20 21:04:37.274  - warn: admin.0 (7454) Repository cannot be read
                            2021-12-20 21:04:39.056  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 7505
                            2021-12-20 21:04:40.515  - info: discovery.0 (7505) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:43.039  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7520
                            2021-12-20 21:04:44.601  - info: backitup.0 (7520) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:44.662  - info: backitup.0 (7520) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:05:13.492  - info: host.raspberrypi Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
                            2021-12-20 21:07:29.728  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:07:29.743  - info: backitup.0 (7520) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:07:29.744  - info: backitup.0 (7520) cleaned everything up...
                            2021-12-20 21:07:29.745  - info: backitup.0 (7520) terminating
                            2021-12-20 21:07:29.746  - info: backitup.0 (7520) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:07:29.752  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:07:30.293  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:07:32.829  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7933
                            2021-12-20 21:07:34.369  - info: backitup.0 (7933) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:07:34.432  - info: backitup.0 (7933) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:08:09.386  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:08:09.398  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:08:09.398  - info: backitup.0 (7933) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:08:09.401  - info: backitup.0 (7933) cleaned everything up...
                            2021-12-20 21:08:09.402  - info: backitup.0 (7933) terminating
                            2021-12-20 21:08:09.405  - info: backitup.0 (7933) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:08:09.993  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:08:12.439  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7984
                            2021-12-20 21:08:14.006  - info: backitup.0 (7984) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:08:14.074  - info: backitup.0 (7984) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:09:05.300  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:09:05.316  - info: backitup.0 (7984) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:09:05.320  - info: backitup.0 (7984) cleaned everything up...
                            2021-12-20 21:09:05.322  - info: backitup.0 (7984) terminating
                            2021-12-20 21:09:05.325  - info: backitup.0 (7984) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:09:05.358  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:09:05.861  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:09:08.399  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 8013
                            2021-12-20 21:09:09.926  - info: backitup.0 (8013) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:09:09.989  - info: backitup.0 (8013) [iobroker] backup was activated at 02:40 every 1 day(s)
                            
                            
                            
                            S 1 Reply Last reply Reply Quote 0
                            • S
                              Sirfauntleroy @Sirfauntleroy last edited by

                              Fand die datei nicht.. nochmal ausgewählt: und es tut sich was

                              2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                              2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                              2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                              2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                              2021-12-20 21:18:40.641  - info: backitup.0 (8013) cleaned everything up...
                              2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                              2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                              2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                              2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                              2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                              2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                              2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                              2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                              2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                              2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                              2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                              2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                              2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                              2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                              2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                              2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                              2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                              2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                              2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                              2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                              
                              
                              Thomas Braun F 2 Replies Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Sirfauntleroy last edited by

                                @sirfauntleroy
                                Du hast die Lokalisierung / lokale Zeitzone nicht angepasst .

                                1 Reply Last reply Reply Quote 0
                                • F
                                  fastfoot @Sirfauntleroy last edited by

                                  @sirfauntleroy da ist immer noch der hostname falschiob stop, iob host this, iob start. Gestern hiess es noch dass backitup das macht 🙂

                                  S Homoran 2 Replies Last reply Reply Quote 1
                                  • S
                                    Sirfauntleroy @fastfoot last edited by

                                    @fastfoot

                                    jetzt rattert im log so einiges durch..
                                    geduldig abwarten...

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

                                      Das Backup ist durchgelaufen.
                                      nun folgendes Problem ...

                                      Error: Cannot find module '../encodings'
                                      Require stack:
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/types/json.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/lib/express.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/lib/web.js
                                      - /opt/iobroker/node_modules/iobroker.admin/main.js
                                          at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                                          at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                                          at Module.require (internal/modules/cjs/loader.js:974:19)
                                          at require (internal/modules/cjs/helpers.js:93:18)
                                          at Object.getCodec (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:65:27)
                                          at Object.getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:127:23)
                                          at getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:45:18)
                                          at readStream (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:180:15)
                                          at getRawBody (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:108:12)
                                          at read (/opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js:77:3)
                                      
                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Sirfauntleroy last edited by

                                        @sirfauntleroy

                                        nodeJS ist sauber, nehme ich an?

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

                                          @thomas-braun

                                          nach einem Reboot gehts es jetzt soweit..

                                          eieiei..

                                          Irgendwie wäre die Idee mit dem schnellen wiederherstellen per .iso ja doch verlockend gewesen...

                                          Herzlichen Dank bisher an euch alle!!!!!!

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

                                            Erstmal danke an alle, die am Backup-Adapter beteiligt sind. Ist ja grundsätzlich schon echt ne super Sache!!!!!!

                                            Nachdem das System nun wieder weitgehend anständig läuft, hätte ich noch ein paar Fragen:

                                            1. Kann ich nun, da das System läuft redis ohne Probleme abstellen? (Wird ja offensichtlich nicht benötigt und macht mehr Probleme als nutzen) und wenn ja, wie, ohne, dass ich wieder einen Crash verursache? 😄

                                            2. Da ich die komplette Anbindung an KNX über Nodered realisiere bin ich darauf besonders angewiesen.
                                              Nach dem Einspielen des Backups waren die Zusatzbausteine wie KNX-Ultimate nicht wieder hergestellt (glaube auch gelesen zu haben, das dies normal ist). Nachdem ich diese installiert hatte, waren alle KNX-Nodes im ersten Flow ?! ohne jegliche Verbindung. Strange....
                                              Gut, dass ich nach jedem größeren Programmierschritt separate Backups aller Flows mache.. so konnte ich diese wiederherstellen. Aber geht das nicht auch einfacher?

                                            Homoran 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

                                            845
                                            Online

                                            32.0k
                                            Users

                                            80.5k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            59
                                            3007
                                            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