Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter time-switch v2.0.x GitHub/Latest

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter time-switch v2.0.x GitHub/Latest

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

      @SVallant Cool! Falls sich in dieser Version noch was an der Widgetlogik ändert, gebe ich dir bescheid. Wo gibt es den Quellcode dazu?

      SVallant liv-in-sky 2 Replies Last reply Reply Quote 0
      • SVallant
        SVallant @walli545 last edited by

        @walli545 Danke, nightly Build hier zum Download

        TimeSwitch-Widget ist minuvis-webapp.iobroker\src\components\widgets\TimeSwitch.js

        Die Visu ist eine React-App ...

        Werde das noch ein bißchen testen und dann in die nächste Version bei Github einfliessen lassen.
        Sage dir dann auch Bescheid !

        1 Reply Last reply Reply Quote 0
        • frankthegreat
          frankthegreat @walli545 last edited by

          @walli545 Gerade gesehen, das es eine neue Version gibt 😳
          Wird jetzt auch auf iPad und iPhone richtig dargestellt 👍

          Super Job, den du hier machst. Ich freue mich schon auf weitere Features von dir.

          1 Reply Last reply Reply Quote 0
          • W
            Wolfi last edited by

            @walli545
            Komisches verhalten unter Android
            Sobald ich mit Android Tablet oder Handy versuche im Zeit zu ändern oder den Namen zu ändern.
            Kommt kurz die Tastatur hoch die View mit Time-switch schließt sich und ich lande in meiner Hauptview dem Dasbord??
            Via PC funktioniert es.

            walli545 1 Reply Last reply Reply Quote 0
            • liv-in-sky
              liv-in-sky @walli545 last edited by

              @walli545 sorry - ich schon wieder - habe heute auf js-controller 3 upgedatet

              jetzt kommt das im browser:

              Image 4.png

              die widget scheinen aber zu funktionieren und auch zu schalten

              im log vom iobroker kommt das:

              Image 5.png

              1 Reply Last reply Reply Quote 0
              • walli545
                walli545 @Wolfi last edited by

                @Wolfi kann ich bei mir so nicht feststellen, hat sonst jmd das Problem?
                @liv-in-sky Ersters ist normal, zweites sollte nach einem Update auf die neueste Version behoben sein

                liv-in-sky W Iccube 3 Replies Last reply Reply Quote 0
                • liv-in-sky
                  liv-in-sky @walli545 last edited by

                  @walli545 die neue version , die kommt oder die schon da ist? 1.1.0 ?

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

                    @all Ich habe nun noch die vorgeschlagenen Änderung von @berndhome und @SVallant eingebaut. Dadurch hat sich erneut
                    die Struktur der Schedule Daten geändert, also bitte nochmal bereits vorhandene vor dem Update löschen. Ich versuche von jetzt an solche Änderungen zu vermeiden bzw. wenn dann Upgrade Logik einzubauen. Aktuell denke ich aber, das das noch nicht sinnvoll ist, da der Adapter ja noch in der Testphase ist.
                    Zudem habe ich noch einige Unit Tests geschrieben und die Adapterlogik dahingehend geändert, dass nun nicht mehr bei einer Änderung an einem Schaltplan alles komplett jedes mal neu eingelesen/registriert wird, sondern, nur wenn Änderungen von außen kommen. Das sollte besonders auf schwächeren Hosts und vielen Triggern weniger Performance kosten.

                    Bitte die Version von https://github.com/walli545/ioBroker.time-switch/tarball/dev installieren und nochmal ausgiebig testen. Dann kann man über einen neuen Release und über neue Features nachdenken 🙂

                    Außerdem habe ich das README angepasst und es gibt nun auch eine deutsche Anleitung @SMS.

                    liv-in-sky 1 Reply Last reply Reply Quote 0
                    • W
                      Wolfi @walli545 last edited by Wolfi

                      @walli545
                      Das passiert sobald die Tastatur eingeblendet und auf das TS Tool trift.
                      Wenn ich die Tastatur verkleinern dann funktioniert es aber mit so einer kleinen Tastatur kann man nicht arbeiten.

                      Neue Version für alle?
                      Bitte die Version von https://github.com/walli545/ioBroker.time-switch/tarball/dev installieren

                      1 Reply Last reply Reply Quote 0
                      • liv-in-sky
                        liv-in-sky @walli545 last edited by liv-in-sky

                        @walli545

                        • bei mir kann ich den current value von hand schalten
                        • aber das schedule funktioniert nicht - json datenpunkt stimmt - kein schalten

                        fehler habe ich sonst keinen mehr im log
                        habe alles gelöscht, neu installiert , upload gemacht - kein schalten - kein eintrag im log

                        walli545 O 2 Replies Last reply Reply Quote 0
                        • Iccube
                          Iccube @walli545 last edited by Iccube

                          @walli545 ist bei mir genauso wie es @Wolfi beschrieben hat lande auch immer in der Hauptview bei Android geräten Tablet und Handy

                          W 1 Reply Last reply Reply Quote 0
                          • walli545
                            walli545 @liv-in-sky last edited by walli545

                            @liv-in-sky hab noch Logging hinzugefügt, bitte nochmal updaten. Falls es nicht geht, kompletten Log schicken und Inhalt des Schedules (Logging Level von Adapter auf debug stellen). Bei mir schaltet es schon 🤔

                            @Wolfi @Iccube Kann mir einer von euch davon eine Bildschirmaufnahme machen? Ich kann das bei mir nicht reproduzieren.

                            liv-in-sky Iccube 2 Replies Last reply Reply Quote 0
                            • liv-in-sky
                              liv-in-sky @walli545 last edited by

                              @walli545

                              log - hätte um 17:11 schalten sollen

                              time-switch.0	2020-05-03 17:11:58.616	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:58.614	info	(32525) Finished message update-trigger
                              time-switch.0	2020-05-03 17:11:58.613	debug	(32525) Scheduling trigger at 17:14 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:11:58.613	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":14,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
                              time-switch.0	2020-05-03 17:11:58.613	info	(32525) Received update-trigger
                              time-switch.0	2020-05-03 17:11:48.309	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:48.302	info	(32525) Finished message add-trigger
                              time-switch.0	2020-05-03 17:11:48.301	debug	(32525) Scheduling trigger at 0:0 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:11:48.300	debug	(32525) Wants OnOffValueAction
                              time-switch.0	2020-05-03 17:11:48.300	debug	(32525) Wants TimeTrigger
                              time-switch.0	2020-05-03 17:11:48.300	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","triggerType":"TimeTrigger","actionType":"OnOffValueAction","valueType":"boolean","stateIds":["controll-own.0.LEDLampe"]}
                              time-switch.0	2020-05-03 17:11:48.300	info	(32525) Received add-trigger
                              time-switch.0	2020-05-03 17:11:45.926	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:45.923	info	(32525) Finished message update-trigger
                              time-switch.0	2020-05-03 17:11:45.922	debug	(32525) Scheduling trigger at 17:13 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:11:45.921	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":13,"weekdays":[1,2,3,4,5,6,0],"id":"0","action":{"type":"OnOffStateAction","name":"On"}}}
                              time-switch.0	2020-05-03 17:11:45.921	info	(32525) Received update-trigger
                              time-switch.0	2020-05-03 17:11:35.803	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:35.801	info	(32525) Finished message add-trigger
                              time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Scheduling trigger at 0:0 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Wants OnOffValueAction
                              time-switch.0	2020-05-03 17:11:35.799	debug	(32525) Wants TimeTrigger
                              time-switch.0	2020-05-03 17:11:35.799	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","triggerType":"TimeTrigger","actionType":"OnOffValueAction","valueType":"boolean","stateIds":["controll-own.0.LEDLampe"]}
                              time-switch.0	2020-05-03 17:11:35.798	info	(32525) Received add-trigger
                              time-switch.0	2020-05-03 17:11:34.759	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:34.758	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:34.756	info	(32525) Finished message enable-schedule
                              time-switch.0	2020-05-03 17:11:34.756	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:34.756	info	(32525) Received enable-schedule
                              time-switch.0	2020-05-03 17:11:34.739	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:34.737	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:34.736	info	(32525) Finished message enable-schedule
                              time-switch.0	2020-05-03 17:11:34.735	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:34.735	info	(32525) Received enable-schedule
                              time-switch.0	2020-05-03 17:11:26.490	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:26.489	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:26.487	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:26.487	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:26.487	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:26.466	debug	(32525) change from adapter itself for time-switch.0.onoff.0.data
                              time-switch.0	2020-05-03 17:11:26.465	debug	(32525) change from adapter itself for time-switch.0.onoff.0.enabled
                              time-switch.0	2020-05-03 17:11:26.463	info	(32525) Finished message enable-schedule
                              time-switch.0	2020-05-03 17:11:26.462	debug	(32525) {"dataId":"time-switch.0.onoff.0.data"}
                              time-switch.0	2020-05-03 17:11:26.462	info	(32525) Received enable-schedule
                              time-switch.0	2020-05-03 17:11:20.279	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:20.279	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:20.277	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:20.276	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:20.276	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:19.828	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:19.827	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:19.825	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:19.824	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:19.824	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:19.770	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:19.768	info	(32525) Finished message change-switched-values
                              time-switch.0	2020-05-03 17:11:19.767	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","valueType":"boolean","onValue":"true","offValue":"false"}
                              time-switch.0	2020-05-03 17:11:19.767	info	(32525) Received change-switched-values
                              time-switch.0	2020-05-03 17:11:17.897	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:17.896	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:17.894	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:17.893	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:17.893	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:17.408	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:17.407	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:17.405	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:17.404	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:17.404	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:17.390	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:17.388	info	(32525) Finished message change-switched-values
                              time-switch.0	2020-05-03 17:11:17.387	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","valueType":"boolean","offValue":"false"}
                              time-switch.0	2020-05-03 17:11:17.387	info	(32525) Received change-switched-values
                              time-switch.0	2020-05-03 17:11:11.065	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:11:11.065	debug	(32525) change from adapter itself for time-switch.0.onoff.1.enabled
                              time-switch.0	2020-05-03 17:11:11.061	info	(32525) Finished message disable-schedule
                              time-switch.0	2020-05-03 17:11:11.060	debug	(32525) {"dataId":"time-switch.0.onoff.1.data"}
                              time-switch.0	2020-05-03 17:11:11.060	info	(32525) Received disable-schedule
                              time-switch.0	2020-05-03 17:11:00.006	debug	(32525) Executing trigger with id 1
                              time-switch.0	2020-05-03 17:10:15.052	debug	(32525) got state: [object Object]
                              time-switch.0	2020-05-03 17:10:15.051	debug	(32525) Scheduling trigger at 17:11 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:10:15.040	debug	(32525) Scheduling trigger at 17:9 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:10:15.035	debug	(32525) got state: [object Object]
                              time-switch.0	2020-05-03 17:10:15.015	debug	(32525) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                              time-switch.0	2020-05-03 17:10:14.989	debug	(32525) Onoff state 1not found, creating
                              time-switch.0	2020-05-03 17:10:14.988	debug	(32525) Found state time-switch.0.onoff.0.data
                              time-switch.0	2020-05-03 17:10:14.967	debug	(32525) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                              time-switch.0	2020-05-03 17:10:14.948	info	(32525) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.time-switch, node: v10.20.1, js-controller: 3.0.20
                              host.iobroker59	2020-05-03 17:10:13.777	info	instance system.adapter.time-switch.0 started with pid 32525
                              host.iobroker59	2020-05-03 17:10:11.274	info	instance system.adapter.time-switch.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              time-switch.0	2020-05-03 17:10:10.752	info	(27511) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              time-switch.0	2020-05-03 17:10:10.752	info	(27511) terminating
                              time-switch.0	2020-05-03 17:10:10.752	info	(27511) cleaned everything up...
                              time-switch.0	2020-05-03 17:10:10.751	info	(27511) Got terminate signal TERMINATE_YOURSELF
                              host.iobroker59	2020-05-03 17:10:10.749	info	stopInstance system.adapter.time-switch.0 send kill signal
                              host.iobroker59	2020-05-03 17:10:10.748	info	stopInstance system.adapter.time-switch.0 (force=false, process=true)
                              time-switch.0	2020-05-03 17:09:56.648	debug	(27511) change from adapter itself for time-switch.0.onoff.0.data
                              time-switch.0	2020-05-03 17:09:56.647	debug	(27511) change from adapter itself for time-switch.0.onoff.0.enabled
                              time-switch.0	2020-05-03 17:09:56.645	info	(27511) Finished message enable-schedule
                              time-switch.0	2020-05-03 17:09:56.645	debug	(27511) {"dataId":"time-switch.0.onoff.0.data"}
                              time-switch.0	2020-05-03 17:09:56.644	info	(27511) Received enable-schedule
                              host.iobroker59	2020-05-03 17:09:10.059	info	instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                              host.iobroker59	2020-05-03 17:09:00.026	info	instance system.adapter.ical.0 started with pid 29171
                              time-switch.0	2020-05-03 17:09:00.007	debug	(27511) Executing trigger with id 0
                              time-switch.0	2020-05-03 17:08:22.938	debug	(27511) change from adapter itself for time-switch.0.onoff.0.data
                              time-switch.0	2020-05-03 17:08:22.934	info	(27511) Finished message update-trigger
                              time-switch.0	2020-05-03 17:08:22.931	debug	(27511) Scheduling trigger at 17:11 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:08:22.930	debug	(27511) {"dataId":"time-switch.0.onoff.0.data","trigger":{"type":"TimeTrigger","hour":17,"minute":11,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
                              time-switch.0	2020-05-03 17:08:22.930	info	(27511) Received update-trigger
                              

                              log - hätte um 17:16 schalten sollen

                              time-switch.0	2020-05-03 17:16:00.006	debug	(32525) Executing trigger with id 0
                              time-switch.0	2020-05-03 17:14:26.309	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:14:26.306	info	(32525) Finished message update-trigger
                              time-switch.0	2020-05-03 17:14:26.305	debug	(32525) Scheduling trigger at 17:17 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:14:26.304	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":17,"weekdays":[1,2,3,4,5,6,0],"id":"1","action":{"type":"OnOffStateAction","name":"Off"}}}
                              time-switch.0	2020-05-03 17:14:26.304	info	(32525) Received update-trigger
                              time-switch.0	2020-05-03 17:14:21.306	debug	(32525) change from adapter itself for time-switch.0.onoff.1.data
                              time-switch.0	2020-05-03 17:14:21.304	info	(32525) Finished message update-trigger
                              time-switch.0	2020-05-03 17:14:21.303	debug	(32525) Scheduling trigger at 17:16 on 1,2,3,4,5,6,0
                              time-switch.0	2020-05-03 17:14:21.303	debug	(32525) {"dataId":"time-switch.0.onoff.1.data","trigger":{"type":"TimeTrigger","hour":17,"minute":16,"weekdays":[1,2,3,4,5,6,0],"id":"0","action":{"type":"OnOffStateAction","name":"On"}}}
                              time-switch.0	2020-05-03 17:14:21.303	info	(32525) Received update-trigger
                              time-switch.0	2020-05-03 17:14:00.005	debug	(32525) Executing trigger with id 1
                              


                              current value bleibt um 17:16 auf false
                              Image 1.png

                              walli545 1 Reply Last reply Reply Quote 0
                              • walli545
                                walli545 @liv-in-sky last edited by

                                @liv-in-sky bewegt sich nur der Schalter nicht oder ändert sich auch der Wert des States nicht? Nicht, dass ich am Falschen Ende suche

                                liv-in-sky 2 Replies Last reply Reply Quote 0
                                • liv-in-sky
                                  liv-in-sky @walli545 last edited by

                                  @walli545 datenpunkte ändern sich nicht

                                  du kannst auch gerne noch warten, ob es einen anderen user gibt, der das selbe problem hat

                                  1 Reply Last reply Reply Quote 0
                                  • liv-in-sky
                                    liv-in-sky @walli545 last edited by

                                    @walli545 habe es auch mal mit number getestet - selbes verhalten

                                    walli545 1 Reply Last reply Reply Quote 0
                                    • walli545
                                      walli545 @liv-in-sky last edited by walli545

                                      @liv-in-sky kann es sein, dass du das Widget nicht neu angelegt hast? Und dadurch nie den geschaltenen State konfiguriert hast?

                                      liv-in-sky 1 Reply Last reply Reply Quote 0
                                      • liv-in-sky
                                        liv-in-sky @walli545 last edited by liv-in-sky

                                        @walli545

                                        instanz stop, widgets wurden gelöscht , objecte gelöscht - instanz gelöscht - update adapter - instanz neu - im setting neu und danach neues widget

                                        walli545 1 Reply Last reply Reply Quote 0
                                        • W
                                          Wolfi last edited by

                                          @walli545 @Iccube

                                          Wollte zur Bildschirmaufnahme eine Testumgebung benutzen ( Projekt main ) und siehe da dort lande ich nicht mehr in der Hauptview nein da funktioniert es.
                                          Jetzt muss ich rausfinden warum in meinem Projekt das passiert

                                          1 Reply Last reply Reply Quote 0
                                          • W
                                            Wolfi last edited by Wolfi

                                            @walli545 @Iccube
                                            Das hat definitiv nicht mit deinem Adapter/witget zu tun passiert auch mit einem anderen Eingabe Widget aber warum? Das muss ich noch rausfinden.

                                            Was löst die Einblendung der Tastatur in der View aus??

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            593
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter switch test time vis zeitschaltuhr
                                            75
                                            481
                                            87558
                                            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