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

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    PH-Messung

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

      @skinni genau. Da kommen ja die Boolean Werte schon her ;-)))

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

        @coyote das sind dort zahlen und die Library stellt es als binärstring dar das man es einfacher anschauen kann weil ich denke das es Bits sind.

        Vergiss wireshark, mach neuen Test mit der Library 😉

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

          sonst seh ich keine Werte die sich ändern, abgesehen von PH und redox

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

            @skinni Im Wireshark und zb auch bei deinem einen Post https://forum.iobroker.net/post/635416 hat sich was geändert ... schau mal am anfang ... binFlag1. Die Werte die wir schon gesehen haben stehen auf meiner GitHub seite ... aber die Bedeutung ist noch unklar.

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

              @apollon77 Hatte mir das nicht so genau angeschaut, bin noch am arbeiten. Das erste Paket hat immer die 11 im binFlag1, danach ist es immer 100 und ändert sich auch nie.
              Es ändern sich bei mir nur die Schaltzustände im binFlag2 und die Werte für PH/Redox.

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

                @skinni im wireshark von @coyote hatten sich die binFlag1 auch geändert als er es ins Wasser getan hat und rausgenommen und sowas. Also da ist irgendwas 😉

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

                  @skinni Kannst Du bitte nochmal updaten und nochmal checken? So ein Debig log wäre perfekt dazu

                  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 data.js 192.168.66.56
                      ph803w:device Connected to TCP 192.168.66.56:12416 +0ms
                      ph803w:device Write and register for response type 7: 0000000303000006 +3ms
                      ph803w:device Passcode received: IIXODDIHLL +14ms
                      ph803w:device Resolve for message type 7: IIXODDIHLL +0ms
                      ph803w:device Write and register for response type 9: 000000030f000008000a4949                                                                                                                     584f444449484c4c +2ms
                      ph803w:device login success +7ms
                      ph803w:device Resolve for message type 9: true +0ms
                      ph803w:device Write and register for response type 145: 000000030400009002 +1m                                                                                                                     s
                      ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.49,"re                                                                                                                     dox":-31,"phSwitch":false,"redoxSwitch":true} +44ms
                    Data: {"binFlags1":"11","binFlags2":"10","ph":7.49,"redox":-31,"phSwitch":false,                                                                                                                     "redoxSwitch":true}
                      ph803w:device Resolve for message type 145: [object Object] +3ms
                      ph803w:device Send ping +4s
                      ph803w:device received pong +9ms
                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-29,"phSwitch":false,"redoxSwitch":true} +40ms
                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-29,"phSwitch":false,"redoxSwitch":true}
                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-29,"phSwitch":false,"redoxSwitch":true} +0ms
                      ph803w:device Send ping +4s
                      ph803w:device received pong +3ms
                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.5,"redox":-28,"phSwitch":false,"redoxSwitch":true} +2s
                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.5,"redox":-28,"phSwitch":false,"redoxSwitch":true}
                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.5,"redox":-28,"phSwitch":false,"redoxSwitch":true} +0ms
                      ph803w:device Send ping +2s
                      ph803w:device received pong +11ms
                      ph803w:device Send ping +4s
                      ph803w:device received pong +3ms
                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-25,"phSwitch":false,"redoxSwitch":true} +15ms
                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-25,"phSwitch":false,"redoxSwitch":true}
                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.49,"redox":-25,"phSwitch":false,"redoxSwitch":true} +1ms
                      ph803w:device Send ping +4s
                      ph803w:device received pong +3ms
                      ph803w:device Send ping +4s
                      ph803w:device Ping response overdue, reconnect +8s
                      ph803w:device Destroy socket +0ms
                      ph803w:device Connected to TCP 192.168.66.56:12416 +17s
                      ph803w:device Socket end, Reconnect: true +10s
                    (node:29697) UnhandledPromiseRejectionWarning: Error: Already connected to device
                        at /home/coyote/ph803w/node_modules/node-ph803w/lib/device.js:53:24
                        at new Promise (<anonymous>)
                        at PH803WDevice.connect (/home/coyote/ph803w/node_modules/node-ph803w/lib/device.js:50:16)
                        at Timeout._onTimeout (/home/coyote/ph803w/node_modules/node-ph803w/lib/device.js:91:34)
                        at listOnTimeout (internal/timers.js:554:17)
                        at processTimers (internal/timers.js:497:7)
                    (node:29697) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                    (node:29697) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                    root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# 
                    
                    apollon77 1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @coyote last edited by

                      @coyote sagte in PH-Messung:

                      Please try again 🙂 (update auf GitHub) ...

                      coyote 1 Reply Last reply Reply Quote 0
                      • coyote
                        coyote Most Active @apollon77 last edited by

                        @apollon77

                        Also, das hier kommt wenn ich das Gerät etwas länger aus lasse, keine Ahnung 30s oder so

                        root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w* node data.js 192.168.66.56
                          ph803w:device Connected to TCP 192.168.66.56:12416 +0ms
                          ph803w:device Write and register for response type 7: 0000000303000006 +3ms
                          ph803w:device Passcode received: IIXODDIHLL +10ms
                          ph803w:device Resolve for message type 7: IIXODDIHLL +0ms
                          ph803w:device Write and register for response type 9: 000000030f000008000a4949584f444449484c4c +1ms
                          ph803w:device login success +13ms
                          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":"10","ph":7.33,"redox":-113,"phSwitch":false,"redoxSwitch":true} +45ms
                        Data: {"binFlags1":"11","binFlags2":"10","ph":7.33,"redox":-113,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Resolve for message type 145: [object Object] +2ms
                          ph803w:device Send ping +4s
                          ph803w:device received pong +12ms
                          ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-112,"phSwitch":false,"redoxSwitch":true} +1s
                        Data: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-112,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-112,"phSwitch":false,"redoxSwitch":true} +0ms
                          ph803w:device Send ping +3s
                          ph803w:device received pong +3ms
                          ph803w:device Send ping +4s
                          ph803w:device received pong +5ms
                          ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-111,"phSwitch":false,"redoxSwitch":true} +2s
                        Data: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-111,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.33,"redox":-111,"phSwitch":false,"redoxSwitch":true} +0ms
                          ph803w:device Send ping +2s
                          ph803w:device received pong +5ms
                          ph803w:device Send ping +4s
                          ph803w:device Ping response overdue, reconnect +8s
                          ph803w:device Destroy socket +1ms
                          ph803w:device Socket error: Error: connect EHOSTUNREACH 192.168.66.56:12416 +29s
                        Error: Error: connect EHOSTUNREACH 192.168.66.56:12416
                        (node:32240) UnhandledPromiseRejectionWarning: Error
                            at Socket.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/lib/device.js:78:28)
                            at Socket.emit (events.js:314:20)
                            at emitErrorNT (internal/streams/destroy.js:92:8)
                            at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
                            at processTicksAndRejections (internal/process/task_queues.js:84:21)
                        (node:32240) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                        (node:32240) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                        root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example#
                        
                        

                        Stecke ich es aus und nach paar Sek. wieder ein, siehts so aus

                        root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w* node data.js 192.168.66.56
                          ph803w:device Connected to TCP 192.168.66.56:12416 +0ms
                          ph803w:device Write and register for response type 7: 0000000303000006 +4ms
                          ph803w:device Passcode received: IIXODDIHLL +5ms
                          ph803w:device Resolve for message type 7: IIXODDIHLL +1ms
                          ph803w:device Write and register for response type 9: 000000030f000008000a4949584f444449484c4c +0ms
                          ph803w:device login success +16ms
                          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":"10","ph":7.38,"redox":-87,"phSwitch":false,"redoxSwitch":true} +53ms
                        Data: {"binFlags1":"11","binFlags2":"10","ph":7.38,"redox":-87,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Resolve for message type 145: [object Object] +1ms
                          ph803w:device Send ping +4s
                          ph803w:device received pong +4ms
                          ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-84,"phSwitch":false,"redoxSwitch":true} +849ms
                        Data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-84,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-84,"phSwitch":false,"redoxSwitch":true} +1ms
                          ph803w:device Send ping +3s
                          ph803w:device received pong +3ms
                          ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-83,"phSwitch":false,"redoxSwitch":true} +3s
                        Data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-83,"phSwitch":false,"redoxSwitch":true}
                          ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":-83,"phSwitch":false,"redoxSwitch":true} +7ms
                          ph803w:device Send ping +1s
                          ph803w:device received pong +3ms
                          ph803w:device Send ping +4s
                          ph803w:device Ping response overdue, reconnect +8s
                          ph803w:device Destroy socket +0ms
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                          ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                          ph803w:device Socket end, Reconnect: true +10s
                        
                        

                        Mehr tut sich da leider nicht mehr

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

                          @coyote alles klar. Checke nach dem Film morgen .. :-)) aber hilfreiches log. Danke.

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

                            @coyote sagte in PH-Messung:

                            Ok, war doch schneller alsgedacht ... Please check again.

                            Wenn ich Dich um einen Zusatztest bitten darf: Starte mal neu während das Gerät aus ist ... und schalte es dann ein, verbindet er sich dann korrekt?

                            Marc R S J coyote 4 Replies Last reply Reply Quote 0
                            • Marc R
                              Marc R @apollon77 last edited by

                              @apollon77 würde mich da gerne auch als Tester zur Verfügung stellen... Wie installiere ich das am besten? Ich laufe auf Home Assistant, nicht iobroker leider. Soll ich iobroker auf einem separaten Raspi installieren oder gibt es da einfachere Lösungen, zb Virtual Machine auf Win8 oder sowas? Lieben Dank

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

                                @apollon77 In beiden Fällen negativ. Hab das script laufen lassen, dann den PH-803w aus und gewartet, aber die Pause war wohl zu lange. Dann hab ich ihn wieder eingeschaltet, bin reingelaufen und hab das script gestartet, aber es konnte sich nicht verbinden.

                                Update hab ich gerade eben vorher gemacht.

                                  ph803w:device received pong +9ms
                                  ph803w:device Send ping +4s
                                  ph803w:device Ping response overdue, reconnect +8s
                                  ph803w:device Destroy socket +1ms
                                  ph803w:device Socket error: Error: connect EHOSTUNREACH 192.168.88.128:12416 +29s
                                Error: Error: connect EHOSTUNREACH 192.168.88.128:12416
                                (node:9875) UnhandledPromiseRejectionWarning: Error
                                    at Socket.<anonymous> (/home/pi/node_modules/node-ph803w/lib/device.js:78:28)
                                    at Socket.emit (events.js:314:20)
                                    at emitErrorNT (internal/streams/destroy.js:92:8)
                                    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
                                    at processTicksAndRejections (internal/process/task_queues.js:84:21)
                                (node:9875) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                (node:9875) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                
                                pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node data.js 192.168.88.128
                                  ph803w:device Socket error: Error: connect EHOSTUNREACH 192.168.88.128:12416 +0ms
                                Error: Error: connect EHOSTUNREACH 192.168.88.128:12416
                                (node:15611) UnhandledPromiseRejectionWarning: Error
                                    at Socket.<anonymous> (/home/pi/node_modules/node-ph803w/lib/device.js:78:28)
                                    at Socket.emit (events.js:314:20)
                                    at emitErrorNT (internal/streams/destroy.js:92:8)
                                    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
                                    at processTicksAndRejections (internal/process/task_queues.js:84:21)
                                (node:15611) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                (node:15611) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                
                                1 Reply Last reply Reply Quote 0
                                • J
                                  johnbobjamesson @apollon77 last edited by

                                  @apollon77 Ich hab's hier eingerichtet und kann auf Zuruf testen, aber ihr kommt ja momentan so aus. Nur, falls Du noch jemanden brauchst, melde Dich. Ach, und danke für die ganze Arbeit! Ich freue mich so darauf, hoffentlich irgendwann die Daten im iobroker zu haben 🙂
                                  Grüße, Claudio

                                  1 Reply Last reply Reply Quote 0
                                  • coyote
                                    coyote Most Active @apollon77 last edited by

                                    @apollon77

                                    Log wenn Gerät eingeschaltet, dann ausgeschaltet. Nach ca. 30s bricht er dann komplett ab.

                                    root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w*                                                                                                                      node data.js 192.168.66.56
                                      ph803w:device Connected to TCP 192.168.66.56:12416 +0ms
                                      ph803w:device Write and register for response type 7: 0000000303000006 +2ms
                                      ph803w:device Passcode received: IIXODDIHLL +7ms
                                      ph803w:device Resolve for message type 7: IIXODDIHLL +1ms
                                      ph803w:device Write and register for response type 9: 000000030f000008000a4949                                                                                                                     584f444449484c4c +0ms
                                      ph803w:device login success +16ms
                                      ph803w:device Resolve for message type 9: true +0ms
                                      ph803w:device Write and register for response type 145: 000000030400009002 +1m                                                                                                                     s
                                      ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.35,"re                                                                                                                     dox":96,"phSwitch":false,"redoxSwitch":true} +48ms
                                    Data: {"binFlags1":"11","binFlags2":"10","ph":7.35,"redox":96,"phSwitch":false,"                                                                                                                     redoxSwitch":true}
                                      ph803w:device Resolve for message type 145: [object Object] +2ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"r                                                                                                                     edox":94,"phSwitch":false,"redoxSwitch":true} +3s
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.35,"redox":94,"phSwitch":false,                                                                                                                     "redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {                                                                                                                     "binFlags1":"100","binFlags2":"10","ph":7.35,"redox":94,"phSwitch":false,"redoxS                                                                                                                     witch":true} +0ms
                                      ph803w:device Send ping +1s
                                      ph803w:device received pong +3ms
                                      ph803w:device Send ping +4s
                                      ph803w:device received pong +16ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":93,"phSwitch":false,"redoxSwitch":true} +707ms
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":93,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":93,"phSwitch":false,"redoxSwitch":true} +0ms
                                      ph803w:device Send ping +3s
                                      ph803w:device received pong +3ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":92,"phSwitch":false,"redoxSwitch":true} +3s
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":92,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.36,"redox":92,"phSwitch":false,"redoxSwitch":true} +0ms
                                      ph803w:device Send ping +1s
                                      ph803w:device received pong +2ms
                                      ph803w:device Send ping +4s
                                      ph803w:device received pong +43ms
                                      ph803w:device Send ping +4s
                                      ph803w:device Ping response overdue, reconnect +8s
                                      ph803w:device Destroy socket +0ms
                                      ph803w:device Socket error: Error: connect EHOSTUNREACH 192.168.66.56:12416 +28s
                                    Error: Error: connect EHOSTUNREACH 192.168.66.56:12416
                                    (node:13947) UnhandledPromiseRejectionWarning: Error
                                        at Socket.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/lib/device.js:78:28)
                                        at Socket.emit (events.js:314:20)
                                        at emitErrorNT (internal/streams/destroy.js:92:8)
                                        at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
                                        at processTicksAndRejections (internal/process/task_queues.js:84:21)
                                    (node:13947) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                                    (node:13947) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                                    
                                    

                                    Zweites Log, Gerät nach ca. 10-15s wieder eingesteckt.

                                    root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w* node data.js 192.168.66.56
                                      ph803w:device Connected to TCP 192.168.66.56:12416 +0ms
                                      ph803w:device Write and register for response type 7: 0000000303000006 +12ms
                                      ph803w:device Passcode received: IIXODDIHLL +7ms
                                      ph803w:device Resolve for message type 7: IIXODDIHLL +1ms
                                      ph803w:device Write and register for response type 9: 000000030f000008000a4949584f444449484c4c +1ms
                                      ph803w:device login success +7ms
                                      ph803w:device Resolve for message type 9: true +1ms
                                      ph803w:device Write and register for response type 145: 000000030400009002 +1ms
                                      ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.42,"redox":-59,"phSwitch":false,"redoxSwitch":true} +47ms
                                    Data: {"binFlags1":"11","binFlags2":"10","ph":7.42,"redox":-59,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Resolve for message type 145: [object Object] +2ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-56,"phSwitch":false,"redoxSwitch":true} +3s
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-56,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-56,"phSwitch":false,"redoxSwitch":true} +0ms
                                      ph803w:device Send ping +1s
                                      ph803w:device received pong +5ms
                                      ph803w:device Send ping +4s
                                      ph803w:device received pong +2ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-57,"phSwitch":false,"redoxSwitch":true} +3s
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-57,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.38,"redox":-57,"phSwitch":false,"redoxSwitch":true} +0ms
                                      ph803w:device Send ping +764ms
                                      ph803w:device received pong +2ms
                                      ph803w:device Send ping +4s
                                      ph803w:device received pong +2ms
                                      ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.39,"redox":-56,"phSwitch":false,"redoxSwitch":true} +1s
                                    Data: {"binFlags1":"100","binFlags2":"10","ph":7.39,"redox":-56,"phSwitch":false,"redoxSwitch":true}
                                      ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.39,"redox":-56,"phSwitch":false,"redoxSwitch":true} +0ms
                                      ph803w:device Send ping +3s
                                      ph803w:device Ping response overdue, reconnect +8s
                                      ph803w:device Destroy socket +0ms
                                      ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                                      ph803w:device Socket end, Reconnect: true +10s
                                      ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                                      ph803w:device Socket end, Reconnect: true +10s
                                      ph803w:device Connected to TCP 192.168.66.56:12416 +10s
                                      ph803w:device Socket end, Reconnect: true +10s
                                    
                                    
                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      skinni @coyote last edited by

                                      Reconnect geht bei mir jetzt gar nicht mehr. Zumindest kommen keine Werte mehr. Er bricht aber auch nicht ab

                                        ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":6.95,"redox":690,"phSwitch":false,"redoxSwitch":true} +1s
                                      Data: {"binFlags1":"100","binFlags2":"10","ph":6.95,"redox":690,"phSwitch":false,"redoxSwitch":true}
                                        ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":6.95,"redox":690,"phSwitch":false,"redoxSwitch":true} +0ms
                                        ph803w:device Send ping +3s
                                        ph803w:device received pong +5ms
                                        ph803w:device Send ping +4s
                                        ph803w:device Ping response overdue, reconnect +8s
                                        ph803w:device Destroy socket +1ms
                                        ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                        ph803w:device Socket end, Reconnect: true +10s
                                        ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                        ph803w:device Socket end, Reconnect: true +10s
                                        ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                        ph803w:device Socket end, Reconnect: true +10s
                                        ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                        ph803w:device Socket end, Reconnect: true +10s
                                        ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                        ph803w:device Socket end, Reconnect: true +10s
                                      
                                      1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 last edited by

                                        Grrmpf ... war wohl doch zu spät gestern Abend ... Hab die Änderungen nicht zu GitHub gepusht 🙂 Also bitte "Nochmal" das ganze

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

                                          Alles unter Vorbehalt, weil es gestern bei mir auch schon nicht lief und bei Coyote gings. Kanns an diesen Meldungen liegen, das es nicht funktioniert? Mal sehn was die anderen sagen.

                                          pi@iobroker:~ $ npm install Apollon77/node-ph803w
                                          npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
                                          npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                                          npm WARN pi No description
                                          npm WARN pi No repository field.
                                          npm WARN pi No README data
                                          npm WARN pi No license field.
                                          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
                                          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                          

                                          Hier hab ich das Gerät angemacht, script laufen lassen, Gerät aus, gewartet und wieder an.

                                          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 +8ms
                                            ph803w:device Resolve for message type 7: IVEXBRFPMQ +0ms
                                            ph803w:device Write and register for response type 9: 000000030f000008000a49564558425246504d51 +1ms
                                            ph803w:device login success +7ms
                                            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":"10","ph":7.09,"redox":729,"phSwitch":false,"redoxSwitch":true} +56ms
                                          Data: {"binFlags1":"11","binFlags2":"10","ph":7.09,"redox":729,"phSwitch":false,"redoxSwitch":true}
                                            ph803w:device Resolve for message type 145: [object Object] +2ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +6ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +73ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +6ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +4ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +9ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +4ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +10ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +8ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +8ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +4ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +4ms
                                            ph803w:device Send ping +4s
                                            ph803w:device received pong +7ms
                                            ph803w:device Send ping +4s
                                            ph803w:device Ping response overdue, reconnect +8s
                                            ph803w:device Destroy socket +1ms
                                            ph803w:device Connected to TCP 192.168.88.128:12416 +13s
                                            ph803w:device Socket end, Reconnect: true +10s
                                            ph803w:device Connected to TCP 192.168.88.128:12416 +10s
                                            ph803w:device Socket end, Reconnect: true +10s
                                          

                                          Dann aus, script anund Gerät an:

                                          pi@iobroker:~/node_modules/node-ph803w/example $ DEBUG=ph803w* node data.js 192.168.88.128
                                            ph803w:device Socket error: Error: connect EHOSTUNREACH 192.168.88.128:12416 +0ms
                                          Error: Error: connect EHOSTUNREACH 192.168.88.128:12416
                                          

                                          Hab dann vermutlich erst heute Mittag wieder Zeit zu testen.

                                          coyote 1 Reply Last reply Reply Quote 0
                                          • coyote
                                            coyote Most Active @skinni last edited by

                                            @skinni nein, das passt schon. Die Fehlermeldungen kommen bei mir auch beim Installieren.

                                            Eigentlich sieht es ja so aus wie bei mir, nur das beim zweiten mal das Script das Gerät nicht findet.
                                            Ich habe zwar jetzt die neue Version installiert, kann aber erst heute Mittag/Abend testen mit Gerät aus/ein schalten

                                            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

                                            826
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            47
                                            432
                                            68319
                                            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