Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. cloud.0 Adapter Fehlermeldung Admin instance not defined

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    cloud.0 Adapter Fehlermeldung Admin instance not defined

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

      @glasfaser Mache ich gerne. Aber da wirst Du mich anleiten müssen, wie das geht.
      DANKE.

      Glasfaser 1 Reply Last reply Reply Quote 0
      • Glasfaser
        Glasfaser @Jochen last edited by

        @jochen

        Code-Tags ... siehe hier :

        https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge

        Jochen 1 Reply Last reply Reply Quote 0
        • Jochen
          Jochen @Glasfaser last edited by

          @glasfaser Danke schonmal. Sollte ich hinkriegen. Allerdings scheinbar (wahrscheinlich WEGEN des geschilderten Problems) nicht von hier aus dem Büro. Wenn ich auf Log herunterladen (current) klicke, dann kommt..:
          caaa5ab2-feda-41d4-87d2-672462a0ee05-image.png
          ...und von da werde ich über sign in wieder auf die iobroker.pro Seite geleitet, wo ich aber auch schon eingeloggt bin.
          Muss ich später von zu Hause probieren.

          Jochen 1 Reply Last reply Reply Quote 0
          • Jochen
            Jochen @Jochen last edited by

            @jochen Ach ja, falls das evtl. auch etwas damit zu tun haben könnte, diesen (eigentlich roten) Eintrag bekomme ich auch nicht weg. Wieder screenshot, sorry, aber sollte hierbei ja auch egal sein.
            iobroker.pro.png
            Die logs dann später..

            FredF 1 Reply Last reply Reply Quote 0
            • FredF
              FredF Most Active Forum Testing @Jochen last edited by

              @jochen sagte in cloud.0 Adapter Fehlermeldung Admin instance not defined:

              diesen (eigentlich roten) Eintrag bekomme ich auch nicht weg

              Bei URL Schlüssel für Dienste?
              Da steht doch dabei was zu tun ist...

              Im iot Adapter die iot Anmeldeinformationen neu erstellen

              Jochen 1 Reply Last reply Reply Quote 0
              • Jochen
                Jochen @FredF last edited by

                @fredf Habe ich mit Sicherheit schon mehrfach versucht.
                Habe - wenn ich mich recht entsinne - auch den .iot Adapter anfangs schonmal runter geschmissen, und neu installiert.
                Mit der Folge, dass ich dann alle Alexa-gesteuerten Geräte auch nochmal anlegen musste.
                Hier im Büro sieht das so aus...:
                7b112fb2-ca51-447d-a071-fd1857e66eeb-image.png
                Und die "Einstellungen"...:
                e553c532-f733-4dee-ba44-b4f5570e6a3c-image.png

                FredF 1 Reply Last reply Reply Quote 0
                • FredF
                  FredF Most Active Forum Testing @Jochen last edited by

                  @jochen
                  Ja, merke gerade auch das über die cloud keine Einstellungen der iot Instanz sicht bar sind.
                  Habe das mal hier gemeldet:
                  https://forum.iobroker.net/topic/58412/pro-cloud-update-mit-admin-6-problem-meldungen

                  haselchen 1 Reply Last reply Reply Quote 0
                  • haselchen
                    haselchen Most Active @FredF last edited by

                    @fredf

                    Das liegt aber seiner Admin Version.
                    Man braucht glaube ich mind. Version 6 um die Einstellungen sehen zu können.
                    Er hat 4.2.2

                    Jochen FredF 2 Replies Last reply Reply Quote 0
                    • Jochen
                      Jochen @haselchen last edited by

                      @haselchen Admin Adapter 6.2.22...

                      1 Reply Last reply Reply Quote 0
                      • FredF
                        FredF Most Active Forum Testing @haselchen last edited by

                        @haselchen Nö, das ist noch ein Bug das über die Cloud die falsche Admin Version angezeigt wird

                        haselchen 1 Reply Last reply Reply Quote 0
                        • haselchen
                          haselchen Most Active @FredF last edited by haselchen

                          @fredf

                          Über die Cloud?
                          Sein Screenshot ist doch vom Admin Hauptbildschirm? 🤔

                          cea92bc9-15bd-42e5-a25b-dfc3c37eb795-grafik.png

                          Ok, wenn es das nicht ist, Irrtum von mir 🙂

                          FredF 1 Reply Last reply Reply Quote 0
                          • FredF
                            FredF Most Active Forum Testing @haselchen last edited by

                            @haselchen Nö, ist die cloud ansicht
                            1d7971b9-3fa2-4bd4-9379-d879afa70bfb-grafik.png

                            Jochen 1 Reply Last reply Reply Quote 1
                            • Jochen
                              Jochen @FredF last edited by

                              Noch eine kleine Zusatzinfo an die Experten..
                              Ich habe jetzt die ganze Zeit online an Scripten gearbeitet, und ab und zu auf die Protokolle geklickt.
                              Dabei ist mir aufgefallen, dass der scheinbar erst wieder anfängt, die Fehlermeldungen (3 pro Sek. !) auszugeben, sobald ich auf Protokolle klicke.
                              Dazwischen sind immer zeitliche Lücken - eben die Lücken, in denen ich an den Scripten gearbeitet habe, und nicht in den Protokollen war.
                              So, jetzt gebe ich Ruhe bis ich gleich die logs habe.
                              Danke nochmal für die rege Beteiligung so far.

                              Jochen 1 Reply Last reply Reply Quote 0
                              • Jochen
                                Jochen @Jochen last edited by

                                2022-09-29 14:08:11.164 - info: cloud.0 (1065) User accessed from cloud: pzvhrnGtaDl-q1oTAUzi
                                2022-09-29 14:10:10.608 - info: cloud.0 (1065) User disconnected from cloud: pzvhrnGtaDl-q1oTAUzi
                                2022-09-29 14:11:09.521 - info: cloud.0 (1065) User accessed from cloud: 571FCjNg4FmuW7hqAU0-
                                2022-09-29 14:12:59.232 - warn: cloud.0 (1065) User disconnected from cloud: 0 571FCjNg4FmuW7hqAU0-
                                2022-09-29 14:12:59.235 - info: cloud.0 (1065) User disconnected from cloud:
                                2022-09-29 14:13:32.389 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:32.390 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:32.404 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:32.420 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:32.692 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:33.002 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:33.310 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:33.604 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:33.914 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:34.215 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:34.517 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:34.816 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:35.142 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:35.447 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:35.759 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:36.054 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:36.351 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:36.652 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:36.952 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:37.258 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:13:37.737 - info: cloud.0 (1065) User accessed from cloud: F45_2QblRpJ4TEvUAU2Q
                                2022-09-29 14:13:42.286 - info: cloud.0 (1065) User accessed from cloud: CzgPPNB_Jt3lVwr_AU2W
                                2022-09-29 14:13:42.322 - error: cloud.0 (1065) Received unknown command 1: name
                                2022-09-29 14:13:45.330 - error: cloud.0 (1065) Cannot request web pages: File i-vis-switch-1.ejs not found: {}
                                2022-09-29 14:13:45.405 - error: cloud.0 (1065) Cannot request web pages: File i-vis-button.ejs not found: {}
                                2022-09-29 14:13:47.567 - error: cloud.0 (1065) Cannot request web pages: File i-vis-switch-1.ejs not found: {}
                                2022-09-29 14:13:47.640 - error: cloud.0 (1065) Cannot request web pages: File i-vis-button.ejs not found: {}
                                2022-09-29 14:13:51.685 - info: cloud.0 (1065) User disconnected from cloud: CzgPPNB_Jt3lVwr_AU2W
                                2022-09-29 14:15:22.728 - info: cloud.0 (1065) User disconnected from cloud: F45_2QblRpJ4TEvUAU2Q
                                2022-09-29 14:15:59.078 - info: cloud.0 (1065) User accessed from cloud: LDN6Rndl4-3sQe76AU3g
                                2022-09-29 14:16:17.217 - info: cloud.0 (1065) received all objects
                                2022-09-29 14:17:46.194 - info: cloud.0 (1065) User disconnected from cloud: LDN6Rndl4-3sQe76AU3g
                                2022-09-29 14:17:46.452 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:17:46.492 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:18:09.950 - warn: cloud.0 (1065) Used invalid characters: 0_userdata.0.Noch_Verbraucher_eingeschaltet_? changed to 0_userdata.0.Noch_Verbraucher_eingeschaltet__
                                2022-09-29 14:18:42.930 - info: cloud.0 (1065) received all objects
                                2022-09-29 14:19:16.102 - warn: cloud.0 (1065) Used invalid characters: 0_userdata.0.Noch_Verbraucher_eingeschaltet__.Noch_Verbraucher_eingeschaltet_? changed to 0_userdata.0.Noch_Verbraucher_eingeschaltet__.Noch_Verbraucher_eingeschaltet__
                                2022-09-29 14:19:23.269 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:23.271 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:23.273 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:23.308 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:23.567 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:23.881 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:24.179 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:24.467 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:24.755 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:25.054 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:25.342 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:25.638 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:25.941 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:26.230 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:26.539 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:26.823 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:27.121 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:27.419 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:27.715 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:28.003 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:28.636 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:28.948 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:29.239 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:29.553 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:29.558 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:19:34.622 - info: cloud.0 (1065) received all objects
                                2022-09-29 14:19:57.312 - info: cloud.0 (1065) User accessed from cloud: 78l_vKjv-nv3okU2AU6K
                                2022-09-29 14:20:55.188 - info: javascript.0 (813) Stop script script.js.common.Energie.Noch_Verbraucher_eingeschaltet__
                                2022-09-29 14:21:01.676 - warn: cloud.0 (1065) User disconnected from cloud: 0 78l_vKjv-nv3okU2AU6K
                                2022-09-29 14:21:01.680 - info: cloud.0 (1065) User disconnected from cloud:
                                2022-09-29 14:21:01.688 - info: cloud.0 (1065) User disconnected from cloud: gXr3IVoOZEduz4DjAURB
                                2022-09-29 14:22:33.850 - info: cloud.0 (1065) User accessed from cloud: PBzg5Cr07YXXvEYYAU7y
                                2022-09-29 14:22:42.303 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:22:42.307 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.087 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.092 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.096 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.129 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.403 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:34.700 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:35.020 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:35.328 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:35.619 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:35.921 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:36.231 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:36.544 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:36.836 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:37.135 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:24:37.454 - info: cloud.0 (1065) User accessed from cloud: 6ewN_arEbvPrGCLpAU8t
                                2022-09-29 14:25:33.791 - warn: cloud.0 (1065) User disconnected from cloud: 0 6ewN_arEbvPrGCLpAU8t
                                2022-09-29 14:25:33.794 - info: cloud.0 (1065) User disconnected from cloud:
                                2022-09-29 14:25:34.091 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:25:34.290 - error: cloud.0 (1065) Admin instance not defined. Please specify the lovelace instance in settings
                                2022-09-29 14:26:43.292 - info: cloud.0 (1065) User accessed from cloud: n34UEuZqv2uz35jNAU91
                                2022-09-29 14:26:54.962 - info: cloud.0 (1065) User disconnected from cloud: n34UEuZqv2uz35jNAU91
                                2022-09-29 14:26:54.975 - info: cloud.0 (1065) User disconnected from cloud: PBzg5Cr07YXXvEYYAU7y
                                2022-09-29 14:46:05.757 - info: cloud.0 (1065) Connection changed: disconnect
                                2022-09-29 14:46:05.758 - info: cloud.0 (1065) Connection lost
                                2022-09-29 14:46:35.830 - info: cloud.0 (1065) Trying to connect as system.user.admin to cloud
                                2022-09-29 14:46:55.515 - info: cloud.0 (1065) Connection changed: connect
                                2022-09-29 15:16:52.456 - info: web.0 (1004) ==> Connected system.user.admin from ::ffff:192.168.123.21
                                2022-09-29 15:18:21.677 - info: web.0 (1004) <== Disconnect system.user.admin from ::ffff:192.168.123.21 vis.0
                                2022-09-29 15:26:12.393 - info: admin.0 (581) failed connection to socket.io from ::ffff:192.168.123.196: Passport was not initialized
                                2022-09-29 15:26:55.411 - info: admin.0 (581) ==> Connected system.user.admin from ::ffff:192.168.123.196
                                
                                Jochen 1 Reply Last reply Reply Quote 0
                                • Jochen
                                  Jochen @Jochen last edited by

                                  Und wegen dem URL-Schlüssel für Dienste...

                                  6f1969d0-a21b-4171-963f-7e1cd5049d21-image.png

                                  Die Anmeldedaten sind ok. Wenn ich die "ändere" - also mit dem Gleichen überschreibe (was soll ich sonst da rein schreiben, wenn es richtig ist), dann lässt der mich ja noch nicht mal speichern.
                                  Oder ist das hier:

                                  ade00c2e-46a0-4587-a468-aeb3f35c73be-image.png

                                  FredF 1 Reply Last reply Reply Quote 0
                                  • FredF
                                    FredF Most Active Forum Testing @Jochen last edited by

                                    @jochen sagte in cloud.0 Adapter Fehlermeldung Admin instance not defined:

                                    Und wegen dem URL-Schlüssel für Dienste...

                                    0555bc60-fd81-42fb-8dc2-b5544dfc141f-grafik.png

                                    Dann muss aber der iot Skill wieder aktiviert werden

                                    Jochen 3 Replies Last reply Reply Quote 0
                                    • Jochen
                                      Jochen @FredF last edited by

                                      @fredf Ich versuche es..

                                      1 Reply Last reply Reply Quote 0
                                      • Jochen
                                        Jochen @FredF last edited by

                                        @fredf Nee, das war es nicht. Habe den Button benutzt.
                                        "Zertifikate werden nach dem Start erneuert"
                                        iot Adapter startet wieder.
                                        skill deaktiviert und wieder aktiviert.
                                        iobroker.pro ausgeloggt und wieder eingeloggt.
                                        Diagnose immer noch gleich.

                                        1 Reply Last reply Reply Quote 0
                                        • Jochen
                                          Jochen @FredF last edited by

                                          @fredf ```
                                          2022-09-29 17:23:10.830 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=true)
                                          2022-09-29 17:23:10.837 - info: iot.0 (26671) Got terminate signal TERMINATE_YOURSELF
                                          2022-09-29 17:23:10.842 - info: iot.0 (26671) terminating
                                          2022-09-29 17:23:10.844 - info: iot.0 (26671) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                          2022-09-29 17:23:10.884 - info: iot.0 (26671) Connection changed: disconnect
                                          2022-09-29 17:23:10.885 - info: iot.0 (26671) Connection lost
                                          2022-09-29 17:23:10.894 - info: host.raspberrypi stopInstance system.adapter.iot.0 send kill signal
                                          2022-09-29 17:23:11.413 - info: host.raspberrypi instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                          2022-09-29 17:23:14.014 - info: host.raspberrypi instance system.adapter.iot.0 started with pid 29802
                                          2022-09-29 17:23:16.320 - info: iot.0 (29802) starting. Version 1.11.9 in /opt/iobroker/node_modules/iobroker.iot, node: v16.17.0, js-controller: 4.0.23
                                          2022-09-29 17:23:16.398 - info: iot.0 (29802) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
                                          2022-09-29 17:23:21.976 - info: iot.0 (29802) Connection changed: connect
                                          2022-09-29 17:23:51.374 - info: iot.0 (29802) Request devices
                                          2022-09-29 17:24:03.056 - info: admin.0 (581) <== Disconnect system.user.admin from ::ffff:192.168.123.196 iot
                                          2022-09-29 17:27:24.021 - info: admin.0 (581) ==> Connected system.user.admin from ::ffff:192.168.123.196
                                          2022-09-29 17:30:08.057 - info: admin.0 (581) <== Disconnect system.user.admin from ::ffff:192.168.123.196 iot

                                          FredF 1 Reply Last reply Reply Quote 0
                                          • FredF
                                            FredF Most Active Forum Testing @Jochen last edited by

                                            @jochen
                                            Das sind normale Meldungen, die ich vorhin auch hatte.
                                            Somit müsste die rote Meldung über die pro cloud weg sein, oder?

                                            Jochen 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            797
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            7
                                            38
                                            2265
                                            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