Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. PH-Messung

    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

    PH-Messung

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

      @apollon77 Das war mit debug 😕

      pi@iobroker:~/node_modules/node-ph803w/example $ debug=ph803w* node discovery
      Discover PH803W devices ... CTRL-C to quit
      PH803W Device discovered on 192.168.88.128
      {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"}
      PH803W Device discovered on 192.168.88.128
      {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"}
      ERROR: Ignore data package because invalid message type 145
      ERROR: Ignore data package because invalid message type 145
      
      

      Und hier das normale

      pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node data.js 192.168.88.128
        ph803w:device Connected to TCP 192.168.88.128:12416 +0ms
        ph803w:device Write and register for response type 7: 0000000303000006 +4ms
        ph803w:device Passcode received: IVEXBRFPMQ +11ms
        ph803w:device Resolve for message type 7: {"type":"Buffer","data":[73,86,69,88,66,82,70,80,77,81]} +1ms
        ph803w:device Write and register for response type 9: 000000030f000008000a49564558425246504d51 +1ms
        ph803w:device login success +77ms
        ph803w:device Resolve for message type 9: true +0ms
        ph803w:device Write and register for response type 145: 000000030400009002 +1ms
        ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false} +130ms
      Data: {"binFlags1":"11","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false}
        ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false} +3ms
        ph803w:device Send ping +4s
        ph803w:device received pong +10ms
        ph803w:device Send ping +4s
        ph803w:device received pong +6ms
        ph803w:device Send ping +4s
        ph803w:device received pong +9ms
        ph803w:device Send ping +4s
        ph803w:device received pong +17ms
        ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false} +2s
      Data: {"binFlags1":"100","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false}
        ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"0","ph":7.09,"redox":715,"phSwitch":false,"redoxSwitch":false} +1ms
      

      ok das DEBUG ist case sensitive 😮

      pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node discovery
      Discover PH803W devices ... CTRL-C to quit
        ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
        ph803w:discovery Send broadcast message 0000000303000003 +2ms
        ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +39ms
        ph803w:discovery Discovered device: {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"} +1ms
      PH803W Device discovered on 192.168.88.128
      {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"}
        ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +100ms
        ph803w:discovery Discovered device: {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"} +1ms
      PH803W Device discovered on 192.168.88.128
      {"ip":"192.168.88.128","id1":"2tqRa88FgaUS5AxgARVYug","id2":"02003A\u0000 2d3d954d9bb741b4a19ba1153104932b\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0002api.","apiServer":"com:80","version":"4.1.2"}
        ph803w:discovery Ignore data package because invalid message type 145 +9s
      ERROR: Ignore data package because invalid message type 145
        ph803w:discovery Ignore data package because invalid message type 145 +35s
      ERROR: Ignore data package because invalid message type 145
      ^C
      
      apollon77 1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @skinni last edited by apollon77

        @skinni sagte in PH-Messung:

        @apollon77 Das war mit debug

        Ja klein geschrieben 🙂

        mach mal DEBUG 🙂

        EDIT: Danke! Checke später

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

          @apollon77 Gerade bemerkt, siehe mein edit. Entschuldige meine Amateurhaftigkeit 😬

          apollon77 1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 @skinni last edited by

            @skinni Alles gut. Erstes finding ist das der String anders sein kann 🙂 Ich passe mal die Parser Logik an. Zweitest FInding ist das die "id2" identisch ist zu dem von @coyote ... also das eher nicht die unique ID 🙂

            1 Reply Last reply Reply Quote 1
            • apollon77
              apollon77 last edited by

              Ok, dann bitte nochmal von GitHub aktualisieren, jetzt sollte auch das Format von @skinni verarbeitet werden ... bitte nochmal Ausgabe posten

              S coyote 2 Replies Last reply Reply Quote 0
              • S
                skinni @apollon77 last edited by

                @apollon77

                pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node discovery
                Discover PH803W devices ... CTRL-C to quit
                  ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                  ph803w:discovery Send broadcast message 0000000303000003 +1ms
                  ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +48ms
                  ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +1ms
                PH803W Device discovered on 192.168.88.128
                {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                  ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +93ms
                  ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +1ms
                PH803W Device discovered on 192.168.88.128
                {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                  ph803w:discovery Ignore data package because invalid message type 145: ��ۄ�K�
                  ph803w:discovery ` +1s
                ERROR: Ignore data package because invalid message type 145
                  ph803w:discovery Ignore data package because invalid message type 145: ��ۄ�K�
                  ph803w:discovery _ +6s
                ERROR: Ignore data package because invalid message type 145
                
                1 Reply Last reply Reply Quote 0
                • coyote
                  coyote Most Active @apollon77 last edited by

                  @apollon77 bei mir schauts dann so aus:

                  
                  root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w*                                                                              node discovery
                  Discover PH803W devices ... CTRL-C to quit
                    ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                    ph803w:discovery Send broadcast message 0000000303000003 +0ms
                    ph803w:discovery Parsing discovered device: 192.168.66.56:12414 - 000000036800                                                                             00040016434671704a5453796d434539504c6c703144706268590006483fda87dc47000000203264                                                                             33643935346439626237343162346131396261313135333130343933326200000000000000026170                                                                             692e67697a776974732e636f6d3a383000342e302e3800 +6ms
                    ph803w:discovery Discovered device: {"ip":"192.168.66.56","id":"CFqpJTSymCE9PL                                                                             lp1DpbhY","data1":"483fda87dc47","data2":"","data3":"2d3d954d9bb741b4a19ba115310                                                                             4932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +1ms
                  PH803W Device discovered on 192.168.66.56
                  {"ip":"192.168.66.56","id":"CFqpJTSymCE9PLlp1DpbhY","data1":"483fda87dc47","data                                                                             2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80                                                                             ","version":"4.0.8"}
                    ph803w:discovery Ignore data package because invalid message type 26: ECFqpJTSymCE9PLlp1DpbhYH?ڇ�G 2d3d954d9bb741b4a19ba1153104932b +29s
                  ERROR: Ignore data package because invalid message type 26
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User last edited by

                    @apollon77 bei mir ist es so

                      ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                      ph803w:discovery Send broadcast message 0000000303000003 +1ms
                      ph803w:discovery Parsing discovered device: 192.168.0.118:12414 - 000000036800000400166b624538384a6772685a7930794e4a6f6e503961624b000640f5202c849300000020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e302e3800 +306ms
                      ph803w:discovery Discovered device: {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +1ms
                    PH803W Device discovered on 192.168.0.118
                    {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"}
                    
                    
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 last edited by

                      Cool, updated Ihr bitte nochmal - vor allem @skinni und @coyote und postet die Ausgabe nochmal ... ich will sehen was bei euch diese "unbekannten Pakete" sind 🙂 habe das Logging angepasst. Danke

                      (und @coyote bei dir wars irgendwie abgeschnitten) ...

                      Aber denke auf der Basis haben wir was

                      ? coyote S 3 Replies Last reply Reply Quote 0
                      • ?
                        A Former User @apollon77 last edited by

                        @apollon77

                        Discover PH803W devices ... CTRL-C to quit
                          ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                          ph803w:discovery Send broadcast message 0000000303000003 +1ms
                          ph803w:discovery Parsing discovered device: 192.168.0.118:12414 - 000000036800000400166b624538384a6772685a7930794e4a6f6e503961624b000640f5202c849300000020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e302e3800 +30ms
                          ph803w:discovery Discovered device: {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +2ms
                        PH803W Device discovered on 192.168.0.118
                        {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"}
                        
                        
                        1 Reply Last reply Reply Quote 0
                        • coyote
                          coyote Most Active @apollon77 last edited by

                          @apollon77

                          
                          root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w*                                                                                                           node discovery
                          Discover PH803W devices ... CTRL-C to quit
                            ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                            ph803w:discovery Send broadcast message 0000000303000003 +0ms
                            ph803w:discovery Parsing discovered device: 192.168.66.56:12414 - 000000036800                                                                                                          00040016434671704a5453796d434539504c6c703144706268590006483fda87dc47000000203264                                                                                                          33643935346439626237343162346131396261313135333130343933326200000000000000026170                                                                                                          692e67697a776974732e636f6d3a383000342e302e3800 +4ms
                            ph803w:discovery Discovered device: {"ip":"192.168.66.56","id":"CFqpJTSymCE9PL                                                                                                          lp1DpbhY","data1":"483fda87dc47","data2":"","data3":"2d3d954d9bb741b4a19ba115310                                                                                                          4932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +0ms
                          PH803W Device discovered on 192.168.66.56
                          {"ip":"192.168.66.56","id":"CFqpJTSymCE9PLlp1DpbhY","data1":"483fda87dc47","data                                                                                                          2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80                                                                                                          ","version":"4.0.8"}
                            ph803w:discovery Ignore data package because invalid message type 26: 000000034500001a0016434671704a5453796d434539504c6c703144706268590006483fda87dc4700203264336439353464396262373431623461313962613131353331303439333262 +29s
                          ERROR: Ignore data package because invalid message type 26
                          ^C
                          root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example#
                          
                          1 Reply Last reply Reply Quote 0
                          • S
                            skinni @apollon77 last edited by

                            @apollon77

                            pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node discovery
                            Discover PH803W devices ... CTRL-C to quit
                              ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                              ph803w:discovery Send broadcast message 0000000303000003 +2ms
                              ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +53ms
                              ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +2ms
                            PH803W Device discovered on 192.168.88.128
                            {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                              ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +91ms
                              ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +0ms
                            PH803W Device discovered on 192.168.88.128
                            {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                              ph803w:discovery Ignore data package because invalid message type 145: 000000031400009106e8db848c4b17040202c60a5400000000 +27s
                            ERROR: Ignore data package because invalid message type 145
                              ph803w:discovery Ignore data package because invalid message type 145: 000000031400009106e8db848c4b17040202c60a5300000000 +6s
                            ERROR: Ignore data package because invalid message type 145
                            
                            1 Reply Last reply Reply Quote 0
                            • apollon77
                              apollon77 last edited by

                              Ok, ich denke die weitere Pakete die da kommen sind soweit egal 🙂

                              Damit geht Discovery auch. Dann kann ich vllt doch ohne mein Gerät mal am Adapter basteln

                              1 Reply Last reply Reply Quote 1
                              • apollon77
                                apollon77 last edited by apollon77

                                Ich hab an Discovery nochmal bissl rumgeschraubt. Könnt Ihr bitte nochmal checken ob es noch tut? Am besten (falls jemand früher gemacht hat): Nach 11:10 🙂

                                S ? 2 Replies Last reply Reply Quote 0
                                • S
                                  skinni @apollon77 last edited by

                                  @apollon77

                                  pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node discovery
                                  Discovering PH803W devices ... CTRL-C to quit
                                    ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                                    ph803w:discovery Send broadcast message 0000000303000003 +2ms
                                    ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +82ms
                                    ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +1ms
                                  PH803W Device discovered on 192.168.88.128
                                  {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                                    ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +3ms
                                    ph803w:discovery Discovered device: {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"} +1ms
                                  PH803W Device discovered on 192.168.88.128
                                  {"ip":"192.168.88.128","id":"2tqRa88FgaUS5AxgARVYug","data1":"e8db848c4b17","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.1.2"}
                                  ^C
                                  
                                  1 Reply Last reply Reply Quote 1
                                  • ?
                                    A Former User @apollon77 last edited by

                                    @apollon77 hier die neue Version

                                     Discovering PH803W devices ... CTRL-C to quit
                                      ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
                                      ph803w:discovery Send broadcast message 0000000303000003 +1ms
                                      ph803w:discovery Parsing discovered device: 192.168.0.118:12414 - 000000036800000400166b624538384a6772685a7930794e4a6f6e503961624b000640f5202c849300000020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e302e3800 +305ms
                                      ph803w:discovery Discovered device: {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +2ms
                                    PH803W Device discovered on 192.168.0.118
                                    {"ip":"192.168.0.118","id":"kbE88JgrhZy0yNJonP9abK","data1":"40f5202c8493","data2":"","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"}
                                      ph803w:discovery Ignore data package because invalid message type 26: 000000034500001a00166b624538384a6772685a7930794e4a6f6e503961624b000640f5202c849300203264336439353464396262373431623461313962613131353331303439333262 +29s
                                    
                                    
                                    
                                    1 Reply Last reply Reply Quote 1
                                    • apollon77
                                      apollon77 last edited by

                                      Hat jemand ne Idee was ich für ein Adapter-Bild/Icon nehmen könnte? Jemand "grafisch begabt"? 😉

                                      I 1 Reply Last reply Reply Quote 0
                                      • S
                                        skinni last edited by skinni

                                        Einfach sowas? Transparenten Hintergrund kann ich bei Bedarf auch noch machen, falls das in die richtige Richtung geht

                                        Egal wie du dich entscheidest, hier mit transparentem Hintergrund

                                        803w.png

                                        1 Reply Last reply Reply Quote 0
                                        • I
                                          I-Punkt @apollon77 last edited by

                                          @apollon77
                                          Gedanklich bin ich bei solchen Messungen immer gleich bei Pipette oder Reagenzglas.
                                          09bcfa1b-5a3c-49fc-a8f2-0f63740dc286-image.png 1fe197ed-15d8-4e41-8123-e19bf3d124e8-image.png

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • opossum
                                            opossum @Chaosbrother last edited by

                                            @chaosbrother ,

                                            werden die beiden Messsonden mitgeliefert oder muss ich die extra bei Ali bestellen oder reicht Dein Link zum Bestellen aus?

                                            coyote 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

                                            522
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            48
                                            432
                                            71135
                                            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