PH-Messung
-
@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
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
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
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
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
-
Ok, dann bitte nochmal von GitHub aktualisieren, jetzt sollte auch das Format von @skinni verarbeitet werden ... bitte nochmal Ausgabe posten
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
-
Ok, dann bitte nochmal von GitHub aktualisieren, jetzt sollte auch das Format von @skinni verarbeitet werden ... bitte nochmal Ausgabe posten
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 -
Ok, dann bitte nochmal von GitHub aktualisieren, jetzt sollte auch das Format von @skinni verarbeitet werden ... bitte nochmal Ausgabe posten
@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 -
@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"} -
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
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
-
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"} -
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# -
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 -
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 :-)
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 -
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 :-)
@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
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden550
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge