NEWS
PH-Messung
ioBroker Allgemein
432
Beiträge
48
Kommentatoren
107.7k
Aufrufe
50
Watching
-
nee sorry, ich weiß du hättest da gerne was :) Ist bei mir immer 100 bis auf das erste Paket mit 11.
Mir ist gerade aufgefallen, dass es manchmal selten Daten gibt. Gefühlt ist es so, wenn sich die Werte stabilisiert haben, aber das ist nur eine Vermutung. Evtl. wenn keine Änderung war, gibts kein Update.
Wenn ich das script neu starte verbindet es sich, aber bekommt weiterhin nichts. Scheint also am Gerät selbst zu liegen. Die Abstände bis Daten kommen können also variieren.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 +9ms ph803w:device Resolve for message type 9: true +1ms ph803w:device Write and register for response type 145: 000000030400009002 +2ms ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +48ms Data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +3ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +8ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +9ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +7ms 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 Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1ms ph803w:device Send ping +3s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +0ms -
nee sorry, ich weiß du hättest da gerne was :) Ist bei mir immer 100 bis auf das erste Paket mit 11.
Mir ist gerade aufgefallen, dass es manchmal selten Daten gibt. Gefühlt ist es so, wenn sich die Werte stabilisiert haben, aber das ist nur eine Vermutung. Evtl. wenn keine Änderung war, gibts kein Update.
Wenn ich das script neu starte verbindet es sich, aber bekommt weiterhin nichts. Scheint also am Gerät selbst zu liegen. Die Abstände bis Daten kommen können also variieren.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 +9ms ph803w:device Resolve for message type 9: true +1ms ph803w:device Write and register for response type 145: 000000030400009002 +2ms ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +48ms Data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +3ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +8ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +9ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +7ms 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 Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1ms ph803w:device Send ping +3s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +0ms -
nee sorry, ich weiß du hättest da gerne was :) Ist bei mir immer 100 bis auf das erste Paket mit 11.
Mir ist gerade aufgefallen, dass es manchmal selten Daten gibt. Gefühlt ist es so, wenn sich die Werte stabilisiert haben, aber das ist nur eine Vermutung. Evtl. wenn keine Änderung war, gibts kein Update.
Wenn ich das script neu starte verbindet es sich, aber bekommt weiterhin nichts. Scheint also am Gerät selbst zu liegen. Die Abstände bis Daten kommen können also variieren.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 +9ms ph803w:device Resolve for message type 9: true +1ms ph803w:device Write and register for response type 145: 000000030400009002 +2ms ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +48ms Data: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +3ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +8ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +9ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +7ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +7ms 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 Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":689,"phSwitch":false,"redoxSwitch":true} +1ms ph803w:device Send ping +3s ph803w:device received pong +5ms ph803w:device Send ping +4s ph803w:device received pong +6ms ph803w:device Send ping +4s ph803w:device received pong +5ms ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +1s Data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":690,"phSwitch":false,"redoxSwitch":true} +0ms -
ist es schon möglich den Adapter zu testen?
Muss man für die Installation anders vorgehen als mit normalen Adapter, die man von github installiert? -
ist es schon möglich den Adapter zu testen?
Muss man für die Installation anders vorgehen als mit normalen Adapter, die man von github installiert?@sven-n gibt noch kein Adapter, Apollon hat ein node Script gebastelt. Weiter oben im Thread hat er geschrieben, wie man es installiert
-
@sven-n gibt noch kein Adapter, Apollon hat ein node Script gebastelt. Weiter oben im Thread hat er geschrieben, wie man es installiert
-
@coyote auf seinem github gibt es doch schon was oder sehe ich das falsch?
@sven-n ja da ist ein leeres repository. Finger weg ;-)
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@apollon77 ok danke dir
-
@apollon77 hier die Ausgabe:
root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w* node discovery ph803w:discovery Send broadcast message 0000000303000003 +0ms ph803w:discovery Listen for local PH803W devices on port 12414 +4ms ph803w:discovery Parsing discovered device: 192.168.66.56:12414 - hCFqpJTSymCE9PLlp1DpbhYH?ڇ�G 2d3d954d9bb741b4a19ba1153104932bapi.gizwits.com:804.0.8 +5ms ph803w:discovery Discovered device: {"ip":"192.168.66.56","id1":"CFqpJTSymCE9PLlp1DpbhY","id2":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +1ms /home/coyote/ph803w/node_modules/node-ph803w/example/discovery.js:10 console.log(`PH803W Device discovered on ${remote.address}`); ^ TypeError: Cannot read property 'address' of undefined at PH803WDiscovery.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/example/discovery.js:10:55) at PH803WDiscovery.emit (events.js:314:20) at PH803WDiscovery.parseResponse (/home/coyote/ph803w/node_modules/node-ph803w/lib/discovery.js:103:14) at Socket.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/lib/discovery.js:25:18) at Socket.emit (events.js:314:20) at UDP.onMessage [as onmessage] (dgram.js:921:8) -
@apollon77 hier die Ausgabe:
root@debian:/home/coyote/ph803w/node_modules/node-ph803w/example# DEBUG=ph803w* node discovery ph803w:discovery Send broadcast message 0000000303000003 +0ms ph803w:discovery Listen for local PH803W devices on port 12414 +4ms ph803w:discovery Parsing discovered device: 192.168.66.56:12414 - hCFqpJTSymCE9PLlp1DpbhYH?ڇ�G 2d3d954d9bb741b4a19ba1153104932bapi.gizwits.com:804.0.8 +5ms ph803w:discovery Discovered device: {"ip":"192.168.66.56","id1":"CFqpJTSymCE9PLlp1DpbhY","id2":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"api.gizwits.com:80","version":"4.0.8"} +1ms /home/coyote/ph803w/node_modules/node-ph803w/example/discovery.js:10 console.log(`PH803W Device discovered on ${remote.address}`); ^ TypeError: Cannot read property 'address' of undefined at PH803WDiscovery.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/example/discovery.js:10:55) at PH803WDiscovery.emit (events.js:314:20) at PH803WDiscovery.parseResponse (/home/coyote/ph803w/node_modules/node-ph803w/lib/discovery.js:103:14) at Socket.<anonymous> (/home/coyote/ph803w/node_modules/node-ph803w/lib/discovery.js:25:18) at Socket.emit (events.js:314:20) at UDP.onMessage [as onmessage] (dgram.js:921:8)@coyote Danke! Bitte nochmal versuchen. War nur ein Mini Fehler im Discovery Example Skript :-)
Für die anderen: Bitte auch mal ib updaten von GitHub und das obige Kommando ausführen. Log hier posten. Das ist das Netzwerk-DIscovery per UDP (also gerät wo es gestartet wird und das PH803W muss im gleichen netzwerk sein.
Danke!
id 1 scheint die mqtt ID zu sien, id2 unbekannt. Ich will mal schauen was am besten für eine Adapter Device-ID taugt :-)
Ingo
-
@coyote Danke! Bitte nochmal versuchen. War nur ein Mini Fehler im Discovery Example Skript :-)
Für die anderen: Bitte auch mal ib updaten von GitHub und das obige Kommando ausführen. Log hier posten. Das ist das Netzwerk-DIscovery per UDP (also gerät wo es gestartet wird und das PH803W muss im gleichen netzwerk sein.
Danke!
id 1 scheint die mqtt ID zu sien, id2 unbekannt. Ich will mal schauen was am besten für eine Adapter Device-ID taugt :-)
Ingo
@apollon77 Es kommen keine Werte, so gehts ewig weiter
/€ nochmal etwas produktiver:
Discovery funktioniert, aber danach kommen keine Werte, nur noch invalid message type 145
Das script mit IP aufgerufen funktioniert und liefert Werte.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 ERROR: Ignore data package because invalid message type 145 ERROR: Ignore data package because invalid message type 145 -
@apollon77 Es kommen keine Werte, so gehts ewig weiter
/€ nochmal etwas produktiver:
Discovery funktioniert, aber danach kommen keine Werte, nur noch invalid message type 145
Das script mit IP aufgerufen funktioniert und liefert Werte.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 ERROR: Ignore data package because invalid message type 145 ERROR: Ignore data package because invalid message type 145@skinni sagte in PH-Messung:
Es kommen keine Werte, so gehts ewig weiter
Naja das Discovery Skript macht auch NUR discovery ... das ist korrekt das es nur sagt "Hab was gefunden" :-)
Aber bei Dir starte bitte mal wie oben gesagt mit dem "DEBUG=..." davor! scheinbar ist deine Message anders ... da muss ich nochmal im Parser ran.
-
@skinni sagte in PH-Messung:
Es kommen keine Werte, so gehts ewig weiter
Naja das Discovery Skript macht auch NUR discovery ... das ist korrekt das es nur sagt "Hab was gefunden" :-)
Aber bei Dir starte bitte mal wie oben gesagt mit dem "DEBUG=..." davor! scheinbar ist deine Message anders ... da muss ich nochmal im Parser ran.
@apollon77 Das war mit debug :confused:
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 145Und 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} +1msok das DEBUG ist case sensitive :open_mouth:
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 Das war mit debug :confused:
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 145Und 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} +1msok das DEBUG ist case sensitive :open_mouth:
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@skinni sagte in PH-Messung:
@apollon77 Das war mit debug
Ja klein geschrieben :-)
mach mal DEBUG :-)
EDIT: Danke! Checke später
-
@skinni sagte in PH-Messung:
@apollon77 Das war mit debug
Ja klein geschrieben :-)
mach mal DEBUG :-)
EDIT: Danke! Checke später
-
@apollon77 Gerade bemerkt, siehe mein edit. Entschuldige meine Amateurhaftigkeit :grimacing:
718
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge