Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Einbindung elsner P03/ Modbus Wetterstation

    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

    Einbindung elsner P03/ Modbus Wetterstation

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

      @wendy2702
      Hallo wendy. Der Adapter ist zumindest grün, ich gehe davon aus, dass dies bedeutet die Kommunikation steht?

      Hier meine Einstellungen:

      Modbus Adapter.png Adapter Einstellungen.png

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

        @wendy2702
        Hallo wendy, ich habe noch weitere Versuche unternommen, werde aber nicht schlau aus der Sache. Ich kann ein Objekt anlegen innerhalb der Holding Register aber sobald ich Poll anschalte, wird der Adpater gelb?Screenshot 2022-02-26 162148.png Screenshot 2022-02-26 162053.png

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

          @sebastianiv Dann stelle den Adapter mal auf "Debug" und poste das log hier als Text in Code Tags </>

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

            @wendy2702 ```
            Hallo wendy2702, anbei das Log file. So wie es aussieht, meldet sich die Wetterstation nicht??

            code_text
            2022-03-01 18:12:46.942 - warn: modbus.3 (22629) Error: undefined
            2022-03-01 18:12:46.943 - error: modbus.3 (22629) Request timed out.
            2022-03-01 18:12:46.944 - warn: modbus.3 (22629) Poll error count: 10 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:12:47.944 - info: modbus.3 (22629) Disconnected from slave
            2022-03-01 18:13:47.947 - info: modbus.3 (22629) Connected to slave
            2022-03-01 18:13:52.950 - warn: modbus.3 (22629) Error: undefined
            2022-03-01 18:13:52.951 - error: modbus.3 (22629) Request timed out.
            2022-03-01 18:13:52.952 - warn: modbus.3 (22629) Poll error count: 11 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:13:53.952 - info: modbus.3 (22629) Disconnected from slave
            2022-03-01 18:14:53.956 - info: modbus.3 (22629) Connected to slave
            2022-03-01 18:14:58.960 - warn: modbus.3 (22629) Error: undefined
            2022-03-01 18:14:58.960 - error: modbus.3 (22629) Request timed out.
            2022-03-01 18:14:58.961 - warn: modbus.3 (22629) Poll error count: 12 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:14:59.962 - info: modbus.3 (22629) Disconnected from slave
            2022-03-01 18:15:59.966 - info: modbus.3 (22629) Connected to slave
            2022-03-01 18:16:04.968 - warn: modbus.3 (22629) Error: undefined
            2022-03-01 18:16:04.969 - error: modbus.3 (22629) Request timed out.
            2022-03-01 18:16:04.970 - warn: modbus.3 (22629) Poll error count: 13 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:16:04.971 - error: modbus.3 (22629) Reconnect did not help, restart adapter
            2022-03-01 18:16:04.975 - info: modbus.3 (22629) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
            2022-03-01 18:16:05.600 - info: host.raspberrypi instance system.adapter.modbus.3 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-03-01 18:16:05.605 - info: host.raspberrypi Restart adapter system.adapter.modbus.3 because enabled
            2022-03-01 18:16:06.672 - info: host.raspberrypi instance system.adapter.modbus.3 started with pid 22729
            2022-03-01 18:16:08.297 - info: modbus.3 (22729) starting. Version 3.4.17 in /opt/iobroker/node_modules/iobroker.modbus, node: v14.18.3, js-controller: 3.3.22
            2022-03-01 18:16:08.703 - info: modbus.3 (22729) Connected to slave
            2022-03-01 18:16:13.714 - warn: modbus.3 (22729) Error: undefined
            2022-03-01 18:16:13.715 - error: modbus.3 (22729) Request timed out.
            2022-03-01 18:16:13.716 - warn: modbus.3 (22729) Poll error count: 1 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:16:14.725 - info: modbus.3 (22729) Disconnected from slave
            2022-03-01 18:16:35.365 - info: host.raspberrypi stopInstance system.adapter.modbus.3 (force=false, process=true)
            2022-03-01 18:16:35.383 - info: host.raspberrypi stopInstance system.adapter.modbus.3 send kill signal
            2022-03-01 18:16:35.383 - info: modbus.3 (22729) Got terminate signal TERMINATE_YOURSELF
            2022-03-01 18:16:35.395 - info: modbus.3 (22729) terminating
            2022-03-01 18:16:35.398 - info: modbus.3 (22729) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2022-03-01 18:16:35.969 - info: host.raspberrypi instance system.adapter.modbus.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
            2022-03-01 18:16:38.501 - info: host.raspberrypi instance system.adapter.modbus.3 started with pid 22744
            2022-03-01 18:16:39.655 - debug: modbus.3 (22744) Redis Objects: Use Redis connection: 127.0.0.1:9001
            2022-03-01 18:16:39.704 - debug: modbus.3 (22744) Objects client ready ... initialize now
            2022-03-01 18:16:39.707 - debug: modbus.3 (22744) Objects create System PubSub Client
            2022-03-01 18:16:39.708 - debug: modbus.3 (22744) Objects create User PubSub Client
            2022-03-01 18:16:39.710 - debug: modbus.3 (22744) Objects client initialize lua scripts
            2022-03-01 18:16:39.723 - debug: modbus.3 (22744) Objects connected to redis: 127.0.0.1:9001
            2022-03-01 18:16:39.733 - debug: modbus.3 (22744) objectDB connected
            2022-03-01 18:16:39.735 - debug: modbus.3 (22744) Redis States: Use Redis connection: 127.0.0.1:9000
            2022-03-01 18:16:39.743 - debug: modbus.3 (22744) States create System PubSub Client
            2022-03-01 18:16:39.745 - debug: modbus.3 (22744) States create User PubSub Client
            2022-03-01 18:16:39.752 - debug: modbus.3 (22744) States connected to redis: 127.0.0.1:9000
            2022-03-01 18:16:39.754 - debug: modbus.3 (22744) statesDB connected
            2022-03-01 18:16:39.959 - debug: modbus.3 (22744) Plugin sentry Initialize Plugin (enabled=true)
            2022-03-01 18:16:40.203 - info: modbus.3 (22744) starting. Version 3.4.17 in /opt/iobroker/node_modules/iobroker.modbus, node: v14.18.3, js-controller: 3.3.22
            2022-03-01 18:16:40.507 - debug: modbus.3 (22744) Initialize Objects for disInputs: []
            2022-03-01 18:16:40.508 - debug: modbus.3 (22744) Initialize Objects for coils: []
            2022-03-01 18:16:40.509 - debug: modbus.3 (22744) Initialize Objects for inputRegs: []
            2022-03-01 18:16:40.509 - debug: modbus.3 (22744) Initialize Objects for holdingRegs: [{"_address":"40003","name":"Temp","description":"Außentemperatur","unit":"C","type":"int8le","len":1,"factor":1,"offset":0,"formula":"","role":"level","room":"","poll":true,"wp":"","cw":"","isScale":"","address":2,"deviceId":1,"id":"holdingRegisters.40003_Temp"}]
            2022-03-01 18:16:40.510 - debug: modbus.3 (22744) Add holdingRegisters.40003_Temp: {"_id":"holdingRegisters.40003_Temp","type":"state","common":{"name":"Außentemperatur","role":"level","type":"number","read":true,"write":true,"def":0,"unit":"C"},"native":{"regType":"holdingRegs","address":2,"deviceId":1,"type":"int8le","len":1,"offset":0,"factor":1,"poll":true}}
            2022-03-01 18:16:40.794 - debug: modbus.3 (22744) connect to serial /dev/ttyAMA0 with 19200
            2022-03-01 18:16:40.802 - info: modbus.3 (22744) Connected to slave
            2022-03-01 18:16:40.803 - debug: modbus.3 (22744) [DevID_1] Poll start ---------------------
            2022-03-01 18:16:40.806 - debug: modbus.3 (22744) Initialization of scale factors done!
            2022-03-01 18:16:40.806 - debug: modbus.3 (22744) [DevID_1/holdingRegs] Poll address 2 - 1 registers
            2022-03-01 18:16:45.818 - warn: modbus.3 (22744) Error: undefined
            2022-03-01 18:16:45.819 - error: modbus.3 (22744) Request timed out.
            2022-03-01 18:16:45.820 - warn: modbus.3 (22744) Poll error count: 1 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:16:46.822 - info: modbus.3 (22744) Disconnected from slave
            2022-03-01 18:16:46.827 - debug: modbus.3 (22744) Clearing timeout of the current request.
            2022-03-01 18:16:46.828 - debug: modbus.3 (22744) Cleaning up request fifo.
            2022-03-01 18:17:46.825 - debug: modbus.3 (22744) connect to serial /dev/ttyAMA0 with 19200
            2022-03-01 18:17:46.833 - info: modbus.3 (22744) Connected to slave
            2022-03-01 18:17:46.835 - debug: modbus.3 (22744) [DevID_1] Poll start ---------------------
            2022-03-01 18:17:46.837 - debug: modbus.3 (22744) [DevID_1/holdingRegs] Poll address 2 - 1 registers
            2022-03-01 18:17:51.841 - warn: modbus.3 (22744) Error: undefined
            2022-03-01 18:17:51.843 - error: modbus.3 (22744) Request timed out.
            2022-03-01 18:17:51.845 - warn: modbus.3 (22744) Poll error count: 2 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:17:52.844 - info: modbus.3 (22744) Disconnected from slave
            2022-03-01 18:17:52.847 - debug: modbus.3 (22744) Clearing timeout of the current request.
            2022-03-01 18:17:52.848 - debug: modbus.3 (22744) Cleaning up request fifo.
            2022-03-01 18:18:52.847 - debug: modbus.3 (22744) connect to serial /dev/ttyAMA0 with 19200
            2022-03-01 18:18:52.851 - info: modbus.3 (22744) Connected to slave
            2022-03-01 18:18:52.852 - debug: modbus.3 (22744) [DevID_1] Poll start ---------------------
            2022-03-01 18:18:52.854 - debug: modbus.3 (22744) [DevID_1/holdingRegs] Poll address 2 - 1 registers
            2022-03-01 18:18:57.857 - warn: modbus.3 (22744) Error: undefined
            2022-03-01 18:18:57.858 - error: modbus.3 (22744) Request timed out.
            2022-03-01 18:18:57.860 - warn: modbus.3 (22744) Poll error count: 3 code: {"err":"timeout","timeout":5000}
            2022-03-01 18:18:58.860 - info: modbus.3 (22744) Disconnected from slave
            2022-03-01 18:18:58.864 - debug: modbus.3 (22744) Clearing timeout of the current request.
            2022-03-01 18:18:58.865 - debug: modbus.3 (22744) Cleaning up request fifo.
            
            wendy2702 1 Reply Last reply Reply Quote 0
            • wendy2702
              wendy2702 @SebastianIV last edited by

              @sebastianiv Kannst du das loggen mal auf Debug stellen:

              Debug.gif

              Die Adapter Einstellungen hier posten und auch das Logfile nach Adapter start.

              S 2 Replies Last reply Reply Quote 0
              • S
                SebastianIV @wendy2702 last edited by

                @wendy2702
                Hallo wendy, sorry hat ein wenig länger gedauert. Anebi das log in debug. Ich hatte den Adapter schon das letzte Mal umgestellt aber erst nach deinem Psot gesehen, das es veraltete Daten waren...

                code_text
                2022-03-06 10:39:07.887 - info: host.raspberrypi "system.adapter.modbus.3" enabled
                2022-03-06 10:39:07.994 - info: host.raspberrypi instance system.adapter.modbus.3 started with pid 12198
                2022-03-06 10:39:09.118 - debug: modbus.3 (12198) Redis Objects: Use Redis connection: 127.0.0.1:9001
                2022-03-06 10:39:09.168 - debug: modbus.3 (12198) Objects client ready ... initialize now
                2022-03-06 10:39:09.171 - debug: modbus.3 (12198) Objects create System PubSub Client
                2022-03-06 10:39:09.172 - debug: modbus.3 (12198) Objects create User PubSub Client
                2022-03-06 10:39:09.173 - debug: modbus.3 (12198) Objects client initialize lua scripts
                2022-03-06 10:39:09.193 - debug: modbus.3 (12198) Objects connected to redis: 127.0.0.1:9001
                2022-03-06 10:39:09.202 - debug: modbus.3 (12198) objectDB connected
                2022-03-06 10:39:09.205 - debug: modbus.3 (12198) Redis States: Use Redis connection: 127.0.0.1:9000
                2022-03-06 10:39:09.213 - debug: modbus.3 (12198) States create System PubSub Client
                2022-03-06 10:39:09.215 - debug: modbus.3 (12198) States create User PubSub Client
                2022-03-06 10:39:09.222 - debug: modbus.3 (12198) States connected to redis: 127.0.0.1:9000
                2022-03-06 10:39:09.223 - debug: modbus.3 (12198) statesDB connected
                2022-03-06 10:39:09.386 - debug: modbus.3 (12198) Plugin sentry Initialize Plugin (enabled=true)
                2022-03-06 10:39:09.623 - info: modbus.3 (12198) starting. Version 3.4.17 in /opt/iobroker/node_modules/iobroker.modbus, node: v14.18.3, js-controller: 3.3.22
                2022-03-06 10:39:09.782 - debug: modbus.3 (12198) Initialize Objects for disInputs: []
                2022-03-06 10:39:09.782 - debug: modbus.3 (12198) Initialize Objects for coils: []
                2022-03-06 10:39:09.783 - debug: modbus.3 (12198) Initialize Objects for inputRegs: []
                2022-03-06 10:39:09.783 - debug: modbus.3 (12198) Initialize Objects for holdingRegs: [{"_address":"40003","name":"Temp","description":"Außentemperatur","unit":"C","type":"int8le","len":1,"factor":1,"offset":0,"formula":"","role":"level","room":"","poll":true,"wp":"","cw":"","isScale":"","address":2,"deviceId":1,"id":"holdingRegisters.40003_Temp"}]
                2022-03-06 10:39:09.784 - debug: modbus.3 (12198) Add holdingRegisters.40003_Temp: {"_id":"holdingRegisters.40003_Temp","type":"state","common":{"name":"Außentemperatur","role":"level","type":"number","read":true,"write":true,"def":0,"unit":"C"},"native":{"regType":"holdingRegs","address":2,"deviceId":1,"type":"int8le","len":1,"offset":0,"factor":1,"poll":true}}
                2022-03-06 10:39:10.059 - debug: modbus.3 (12198) connect to serial /dev/ttyAMA0 with 19200
                2022-03-06 10:39:10.067 - info: modbus.3 (12198) Connected to slave
                2022-03-06 10:39:10.068 - debug: modbus.3 (12198) [DevID_1] Poll start ---------------------
                2022-03-06 10:39:10.070 - debug: modbus.3 (12198) Initialization of scale factors done!
                2022-03-06 10:39:10.070 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                2022-03-06 10:39:15.079 - warn: modbus.3 (12198) Error: undefined
                2022-03-06 10:39:15.080 - error: modbus.3 (12198) Request timed out.
                2022-03-06 10:39:15.084 - warn: modbus.3 (12198) Poll error count: 1 code: {"err":"timeout","timeout":5000}
                2022-03-06 10:39:16.082 - info: modbus.3 (12198) Disconnected from slave
                2022-03-06 10:39:16.086 - debug: modbus.3 (12198) Clearing timeout of the current request.
                2022-03-06 10:39:16.088 - debug: modbus.3 (12198) Cleaning up request fifo.
                2022-03-06 10:40:16.084 - debug: modbus.3 (12198) connect to serial /dev/ttyAMA0 with 19200
                2022-03-06 10:40:16.091 - info: modbus.3 (12198) Connected to slave
                2022-03-06 10:40:16.093 - debug: modbus.3 (12198) [DevID_1] Poll start ---------------------
                2022-03-06 10:40:16.094 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                2022-03-06 10:40:21.096 - warn: modbus.3 (12198) Error: undefined
                2022-03-06 10:40:21.097 - error: modbus.3 (12198) Request timed out.
                2022-03-06 10:40:21.099 - warn: modbus.3 (12198) Poll error count: 2 code: {"err":"timeout","timeout":5000}
                2022-03-06 10:40:22.098 - info: modbus.3 (12198) Disconnected from slave
                2022-03-06 10:40:22.101 - debug: modbus.3 (12198) Clearing timeout of the current request.
                2022-03-06 10:40:22.102 - debug: modbus.3 (12198) Cleaning up request fifo.
                2022-03-06 10:41:22.100 - debug: modbus.3 (12198) connect to serial /dev/ttyAMA0 with 19200
                2022-03-06 10:41:22.104 - info: modbus.3 (12198) Connected to slave
                2022-03-06 10:41:22.105 - debug: modbus.3 (12198) [DevID_1] Poll start ---------------------
                2022-03-06 10:41:22.106 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                2022-03-06 10:41:27.108 - warn: modbus.3 (12198) Error: undefined
                2022-03-06 10:41:27.109 - error: modbus.3 (12198) Request timed out.
                2022-03-06 10:41:27.110 - warn: modbus.3 (12198) Poll error count: 3 code: {"err":"timeout","timeout":5000}
                2022-03-06 10:41:28.110 - info: modbus.3 (12198) Disconnected from slave
                2022-03-06 10:41:28.112 - debug: modbus.3 (12198) Clearing timeout of the current request.
                2022-03-06 10:41:28.114 - debug: modbus.3 (12198) Cleaning up request fifo.
                
                1 Reply Last reply Reply Quote 0
                • S
                  SebastianIV @wendy2702 last edited by

                  @wendy2702

                  code_text
                  2022-03-06 10:39:10.070 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                  2022-03-06 10:39:15.079 - warn: modbus.3 (12198) Error: undefined
                  2022-03-06 10:39:15.080 - error: modbus.3 (12198) Request timed out.
                  2022-03-06 10:39:15.084 - warn: modbus.3 (12198) Poll error count: 1 code: {"err":"timeout","timeout":5000}
                  2022-03-06 10:39:16.082 - info: modbus.3 (12198) Disconnected from slave
                  2022-03-06 10:39:16.086 - debug: modbus.3 (12198) Clearing timeout of the current request.
                  2022-03-06 10:39:16.088 - debug: modbus.3 (12198) Cleaning up request fifo.
                  2022-03-06 10:40:16.084 - debug: modbus.3 (12198) connect to serial /dev/ttyAMA0 with 19200
                  2022-03-06 10:40:16.091 - info: modbus.3 (12198) Connected to slave
                  2022-03-06 10:40:16.093 - debug: modbus.3 (12198) [DevID_1] Poll start ---------------------
                  2022-03-06 10:40:16.094 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                  2022-03-06 10:40:21.096 - warn: modbus.3 (12198) Error: undefined
                  2022-03-06 10:40:21.097 - error: modbus.3 (12198) Request timed out.
                  2022-03-06 10:40:21.099 - warn: modbus.3 (12198) Poll error count: 2 code: {"err":"timeout","timeout":5000}
                  2022-03-06 10:40:22.098 - info: modbus.3 (12198) Disconnected from slave
                  2022-03-06 10:40:22.101 - debug: modbus.3 (12198) Clearing timeout of the current request.
                  2022-03-06 10:40:22.102 - debug: modbus.3 (12198) Cleaning up request fifo.
                  2022-03-06 10:41:22.100 - debug: modbus.3 (12198) connect to serial /dev/ttyAMA0 with 19200
                  2022-03-06 10:41:22.104 - info: modbus.3 (12198) Connected to slave
                  2022-03-06 10:41:22.105 - debug: modbus.3 (12198) [DevID_1] Poll start ---------------------
                  2022-03-06 10:41:22.106 - debug: modbus.3 (12198) [DevID_1/holdingRegs] Poll address 2 - 1 registers
                  2022-03-06 10:41:27.108 - warn: modbus.3 (12198) Error: undefined
                  2022-03-06 10:41:27.109 - error: modbus.3 (12198) Request timed out.
                  2022-03-06 10:41:27.110 - warn: modbus.3 (12198) Poll error count: 3 code: {"err":"timeout","timeout":5000}
                  2022-03-06 10:41:28.110 - info: modbus.3 (12198) Disconnected from slave
                  2022-03-06 10:41:28.112 - debug: modbus.3 (12198) Clearing timeout of the current request.
                  2022-03-06 10:41:28.114 - debug: modbus.3 (12198) Cleaning up request fifo
                  
                  wendy2702 1 Reply Last reply Reply Quote 0
                  • wendy2702
                    wendy2702 @SebastianIV last edited by

                    @sebastianiv Poste mal einen Screenshot der Adapter Einstellungen.

                    Ist das RS485 Shield auch wirklich das Device „ttyAMA0“ ?

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

                      @wendy2702
                      Hallo wendy, hier die Einstellungen vom Adapter. Ich hScreenshot 2022-03-07 165903.png abe mir parallel noch ein weiteres Shield bzw. Adapter für RS485 via USB gekauft, vielleicht funktioniert dieser besser....

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

                        Mach mal den Haken bei „Use Aliases“ weg. Kontrolliere danach die Register und poste dann mal das logfile.

                        S 2 Replies Last reply Reply Quote 0
                        • S
                          SebastianIV @wendy2702 last edited by

                          @wendy2702
                          Hallo wendy, ich habe nun Tests mit dem USB Adapter gemacht. Hier stellt sich die Thematik so dar, dass ich keine Antwort von der Wetterstation erhalte. Also die TX LED am Adapter geht an, die COM an der Wetterstation auch aber die RX am Adapter nicht. Um die Funktion der Wetterstation zu prüfen, wurde nun mit einem PC, dem Adapter via Docklight eine Kommunikation aufgebaut. Hier funktioniert alles, also auch die RX LED vom Adapter.

                          Docklight.png

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

                            @wendy2702
                            Hallo wendy, die Wetterstation läuft mittlerweile. Mit Hilfe des USB Adapter, dem richtigenm Einstellungen und Regsitern steht die Kommunikation. Einzig den Parameter des Regens bekomme ich nicht ausgelesen. Hast du hier vielleicht noch einen Tipp? Die Register zuvor funktionieren auch weil der Typ Signed 16bit (Big Endian) aus der Anleitung klar ist. Bei Regen habe ich alles möglich versucht aber nichts funktioniert?? Der WErt bleibt konstant bei 0..

                            Vielen Dank

                            Screenshot 2022-03-08 180505.png Screenshot 2022-03-08 180441.png Screenshot 2022-03-08 180415.png

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

                              @sebastianiv Blöde Frage, regnet es denn?

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

                                @wendy2702
                                🙂 Nein ich habe aber versucht den Regen mit einem feuchten Lappen zu simulieren.

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                924
                                Online

                                31.9k
                                Users

                                80.2k
                                Topics

                                1.3m
                                Posts

                                2
                                18
                                957
                                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