PH-Messung

skinni

2021-06-09 16:46:32.607 - info: host.iobroker iobroker url https://github.com/Apollon77/ioBroker.ph803w --host iobroker --debug
2021-06-09 16:46:34.842 - info: host.iobroker iobroker install Apollon77/ioBroker.ph803w#4d1f3d628c5ab7266d63559b701b41aabda29129
2021-06-09 16:46:35.502 - info: host.iobroker iobroker NPM version: 6.14.12
2021-06-09 16:46:35.506 - info: host.iobroker iobroker npm install Apollon77/ioBroker.ph803w#4d1f3d628c5ab7266d63559b701b41aabda29129 --loglevel error --prefix "/opt/iobroker" (System call)
2021-06-09 16:47:00.077 - info: host.iobroker iobroker + iobroker.ph803w@0.1.4
2021-06-09 16:47:00.078 - info: host.iobroker iobroker updated 1 package in 23.214s
2021-06-09 16:47:02.206 - info: host.iobroker iobroker
2021-06-09 16:47:02.208 - info: host.iobroker iobroker 55 packages are looking for funding run `npm fund` for details
2021-06-09 16:47:02.280 - info: host.iobroker iobroker upload [5] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/words.js words.js application/javascript
2021-06-09 16:47:02.373 - info: host.iobroker iobroker upload [4] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/style.css style.css text/css
2021-06-09 16:47:02.449 - info: host.iobroker iobroker upload [3] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/ph803w_icon.png ph803w_icon.png image/png
2021-06-09 16:47:02.525 - info: host.iobroker iobroker upload [2] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/ph803w.png ph803w.png image/png
2021-06-09 16:47:02.585 - info: host.iobroker iobroker upload [1] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/index_m.html index_m.html text/html
2021-06-09 16:47:02.643 - info: host.iobroker iobroker upload [0] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/admin.d.ts admin.d.ts video/mp2t
2021-06-09 16:47:02.766 - info: host.iobroker iobroker Update "system.adapter.ph803w.0"
2021-06-09 16:47:02.796 - info: host.iobroker stopInstance system.adapter.ph803w.0 (force=false, process=true)
2021-06-09 16:47:02.803 - info: ph803w.0 (16461) Got terminate signal TERMINATE_YOURSELF
2021-06-09 16:47:02.807 - info: ph803w.0 (16461) terminating
2021-06-09 16:47:02.809 - debug: ph803w.0 (16461) Plugin sentry destroyed
2021-06-09 16:47:02.810 - info: ph803w.0 (16461) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-06-09 16:47:02.810 - info: ph803w.0 (16461) Disconnected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128
2021-06-09 16:47:02.819 - info: host.iobroker stopInstance system.adapter.ph803w.0 send kill signal
2021-06-09 16:47:03.391 - info: host.iobroker instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-06-09 16:47:03.874 - info: host.iobroker iobroker exit 0
2021-06-09 16:47:05.910 - info: host.iobroker instance system.adapter.ph803w.0 started with pid 402
2021-06-09 16:47:07.046 - debug: ph803w.0 (402) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-06-09 16:47:07.096 - debug: ph803w.0 (402) Objects client ready ... initialize now
2021-06-09 16:47:07.099 - debug: ph803w.0 (402) Objects create System PubSub Client
2021-06-09 16:47:07.101 - debug: ph803w.0 (402) Objects create User PubSub Client
2021-06-09 16:47:07.102 - debug: ph803w.0 (402) Objects client initialize lua scripts
2021-06-09 16:47:07.130 - debug: ph803w.0 (402) Objects connected to redis: 127.0.0.1:9001
2021-06-09 16:47:07.139 - debug: ph803w.0 (402) objectDB connected
2021-06-09 16:47:07.142 - debug: ph803w.0 (402) Redis States: Use Redis connection: 127.0.0.1:9000
2021-06-09 16:47:07.151 - debug: ph803w.0 (402) States create System PubSub Client
2021-06-09 16:47:07.152 - debug: ph803w.0 (402) States create User PubSub Client
2021-06-09 16:47:07.162 - debug: ph803w.0 (402) States connected to redis: 127.0.0.1:9000
2021-06-09 16:47:07.164 - debug: ph803w.0 (402) statesDB connected
2021-06-09 16:47:07.460 - debug: ph803w.0 (402) Plugin sentry Initialize Plugin (enabled=true)
2021-06-09 16:47:08.012 - info: ph803w.0 (402) starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.ph803w, node: v12.22.1, js-controller: 3.2.16
2021-06-09 16:47:10.141 - debug: ph803w.0 (402) Init 1 known devices without discovery ...
2021-06-09 16:47:10.810 - info: ph803w.0 (402) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
2021-06-09 16:47:10.932 - debug: ph803w.0 (402) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 16:47:11.037 - debug: ph803w.0 (402) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 16:47:19.293 - info: host.iobroker stopInstance system.adapter.ph803w.0 (force=false, process=true)
2021-06-09 16:47:19.301 - info: host.iobroker stopInstance system.adapter.ph803w.0 send kill signal
2021-06-09 16:47:19.299 - info: ph803w.0 (402) Got terminate signal TERMINATE_YOURSELF
2021-06-09 16:47:19.303 - info: ph803w.0 (402) terminating
2021-06-09 16:47:19.304 - debug: ph803w.0 (402) Plugin sentry destroyed
2021-06-09 16:47:19.305 - info: ph803w.0 (402) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-06-09 16:47:19.306 - info: ph803w.0 (402) Disconnected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128
2021-06-09 16:47:19.891 - info: host.iobroker instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-06-09 16:47:22.407 - info: host.iobroker instance system.adapter.ph803w.0 started with pid 1128
2021-06-09 16:47:23.509 - debug: ph803w.0 (1128) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-06-09 16:47:23.548 - debug: ph803w.0 (1128) Objects client ready ... initialize now
2021-06-09 16:47:23.551 - debug: ph803w.0 (1128) Objects create System PubSub Client
2021-06-09 16:47:23.553 - debug: ph803w.0 (1128) Objects create User PubSub Client
2021-06-09 16:47:23.554 - debug: ph803w.0 (1128) Objects client initialize lua scripts
2021-06-09 16:47:23.577 - debug: ph803w.0 (1128) Objects connected to redis: 127.0.0.1:9001
2021-06-09 16:47:23.587 - debug: ph803w.0 (1128) objectDB connected
2021-06-09 16:47:23.589 - debug: ph803w.0 (1128) Redis States: Use Redis connection: 127.0.0.1:9000
2021-06-09 16:47:23.598 - debug: ph803w.0 (1128) States create System PubSub Client
2021-06-09 16:47:23.600 - debug: ph803w.0 (1128) States create User PubSub Client
2021-06-09 16:47:23.609 - debug: ph803w.0 (1128) States connected to redis: 127.0.0.1:9000
2021-06-09 16:47:23.610 - debug: ph803w.0 (1128) statesDB connected
2021-06-09 16:47:23.891 - debug: ph803w.0 (1128) Plugin sentry Initialize Plugin (enabled=true)
2021-06-09 16:47:24.126 - info: ph803w.0 (1128) starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.ph803w, node: v12.22.1, js-controller: 3.2.16
2021-06-09 16:47:24.222 - debug: ph803w.0 (1128) Init 1 known devices without discovery ...
2021-06-09 16:47:24.520 - info: ph803w.0 (1128) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
2021-06-09 16:47:24.572 - debug: ph803w.0 (1128) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 16:47:24.659 - debug: ph803w.0 (1128) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 16:48:00.002 - error: javascript.0 (12871) Cannot get astro date for "nightEnd"
2021-06-09 16:48:00.004 - error: javascript.0 (12871) Cannot get astro date for "night"
2021-06-09 16:48:21.823 - info: ph803w.0 (1128) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...

schletti

Muss ich für ein Update den Adapter vorher wieder löschen?

apollon77

@schletti Nein, einfach "drüber" Installieren. Falls es eine Installation von GitHub ist dann ggf manuell nach dem Update neu starten

schletti

Blöde Frage, aber was muss ich wo machen um einfach drüber zu installieren?

apollon77

@skinni Ok, dann ganz anders :-) Das log hilft nicht.

Im Admin Adapterinstanz beenden
Log dich mit SSH ein
DEBUG=ph803w* iobroker debug ph803w.0
Dann das log von der Konsole bitte posten, da sollte mehr stehen

schletti

Habs schon selber gefunden wie es geht, einfach wie neuen Adapter installieren.

skinni

@apollon77 said in PH-Messung:

DEBUG=ph803w* iobroker debug ph803w.0

2021-06-09 17:04:43.930  - debug: ph803w.0 (16118) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-06-09 17:04:43.979  - debug: ph803w.0 (16118) Objects client ready ... initialize now
2021-06-09 17:04:43.981  - debug: ph803w.0 (16118) Objects create System PubSub Client
2021-06-09 17:04:43.983  - debug: ph803w.0 (16118) Objects create User PubSub Client
2021-06-09 17:04:43.984  - debug: ph803w.0 (16118) Objects client initialize lua scripts
2021-06-09 17:04:44.012  - debug: ph803w.0 (16118) Objects connected to redis: 127.0.0.1:9001
2021-06-09 17:04:44.023  - debug: ph803w.0 (16118) objectDB connected
2021-06-09 17:04:44.026  - debug: ph803w.0 (16118) Redis States: Use Redis connection: 127.0.0.1:9000
2021-06-09 17:04:44.058  - debug: ph803w.0 (16118) States create System PubSub Client
2021-06-09 17:04:44.059  - debug: ph803w.0 (16118) States create User PubSub Client
2021-06-09 17:04:44.069  - debug: ph803w.0 (16118) States connected to redis: 127.0.0.1:9000
2021-06-09 17:04:44.070  - debug: ph803w.0 (16118) statesDB connected
2021-06-09 17:04:44.358  - debug: ph803w.0 (16118) Plugin sentry Initialize Plugin (enabled=true)
2021-06-09 17:04:44.617  - error: ph803w.0 (16118) adapter disabled
2021-06-09 17:04:44.624  - info: ph803w.0 (16118) starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.ph803w, node: v12.22.1, js-controller: 3.2.16
2021-06-09 17:04:44.715  - debug: ph803w.0 (16118) Init 1 known devices without discovery ...
2021-06-09 17:04:44.774  - info: ph803w.0 (16118) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
2021-06-09 17:04:44.845  - debug: ph803w.0 (16118) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 17:04:44.945  - debug: ph803w.0 (16118) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
2021-06-09 17:05:50.930  - info: ph803w.0 (16118) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...

Wenn ich aus- und einschalte steht da nur

2021-06-09 17:10:42.827  - info: ph803w.0 (27348) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...

Hier nochmal ein reboot des Geräts

2021-06-09 17:10:42.827  - info: ph803w.0 (27348) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
2021-06-09 17:19:33.898  - error: ph803w.0 (27348) PH803W device 2tqRa88FgaUS5AxgARVYug Error: Error: connect EHOSTUNREACH 192.168.88.128:12416
2021-06-09 17:19:33.900  - info: ph803w.0 (27348) Disconnected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128
2021-06-09 17:19:43.913  - info: ph803w.0 (27348) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...

und noch ein Edit..

in iobroker siehts weiterhin so aus:

johnbobjamesson

@skinni said in PH-Messung:

Ich überlege mir gerade ob und wie ich mit blockly ein script baue um auszuwerten ob die die Tendenz eher sinkend, oder steigend ist.

z.B. Durchschnitt der letzten 25 Werte und dann Vergleichen mit dem aktuellen Wert.

Machts Sinn sowas mit in den Adapter einzubauen, oder eher nicht?

Ich habe zuerst gedacht, "Wozu soll man das brauchen, PH geht tendiert immer nach oben, Redox immer nach unten...", aber bei näherem Überlegen wäre das natürlich eine Möglichkeit, die Chlorpumpe erst einzuschalten und ggfs. länger laufen zu lassen, wenn der Trend eindeutig nach unten geht...

apollon77

@skinni Ok, mach mal den manuellen Aufruf per SSH aufruf leicht anders und vorher nochmal Update von GitHub

DEBUG=ph803w* node /opt/iobroker/node_modules/iobroker.ph803w/main.js --debug

Homoran

@johnbobjamesson sagte in PH-Messung:

PH geht tendiert immer nach oben

kann ich nicht bestätigen.

ich habe den Pool jetzt etwa 20 Jahre.
ich habe nur bei der ersteinrichtung eine Gabe von pH-minus benötigt.
Seit dem nur noch pH plus.

Diese Jahr lag der pH bei Inbetriebnahme (vor 10 Tagen) bei etwa 7,7, was mich sehr verwunderte.
Also abgewartet. Heute war es 7,2. Die Temperatur steigt noch (im Moment knapp 23°), da wird der pH noch weiter fallen.

skinni

@apollon77 said in PH-Messung:

DEBUG=ph803w* node /opt/iobroker/node_modules/iobroker.ph803w/main.js --debug

pi@iobroker:~ $ DEBUG=ph803w* node /opt/iobroker/node_modules/iobroker.ph803w/main.js --debug
2021-06-09 17:36:06.532  - debug: ph803w.0 (3336) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-06-09 17:36:06.586  - debug: ph803w.0 (3336) Objects client ready ... initialize now
2021-06-09 17:36:06.597  - debug: ph803w.0 (3336) Objects create System PubSub Client
2021-06-09 17:36:06.600  - debug: ph803w.0 (3336) Objects create User PubSub Client
2021-06-09 17:36:06.602  - debug: ph803w.0 (3336) Objects client initialize lua scripts
2021-06-09 17:36:06.622  - debug: ph803w.0 (3336) Objects connected to redis: 127.0.0.1:9001
2021-06-09 17:36:06.633  - debug: ph803w.0 (3336) objectDB connected
2021-06-09 17:36:06.636  - debug: ph803w.0 (3336) Redis States: Use Redis connection: 127.0.0.1:9000
2021-06-09 17:36:06.650  - debug: ph803w.0 (3336) States create System PubSub Client
2021-06-09 17:36:06.652  - debug: ph803w.0 (3336) States create User PubSub Client
2021-06-09 17:36:06.671  - debug: ph803w.0 (3336) States connected to redis: 127.0.0.1:9000
2021-06-09 17:36:06.673  - debug: ph803w.0 (3336) statesDB connected
2021-06-09 17:36:06.975  - debug: ph803w.0 (3336) Plugin sentry Initialize Plugin (enabled=true)
2021-06-09 17:36:07.206  - error: ph803w.0 (3336) adapter disabled
2021-06-09 17:36:07.212  - info: ph803w.0 (3336) starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.ph803w, node: v12.22.1, js-controller: 3.2.16
2021-06-09 17:36:07.309  - debug: ph803w.0 (3336) Init 1 known devices without discovery ...
2021-06-09 17:36:07.312  - debug: ph803w.0 (3336) Start PH803W Device initialization for 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128
  ph803w:device Connected to TCP 192.168.88.128:12416 +0ms
2021-06-09 17:36:07.382  - info: ph803w.0 (3336) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
  ph803w:device Write and register for response type 7: 0000000303000006 +3ms
  ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
  ph803w:discovery Send broadcast message 0000000303000003 +0ms
  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]} +0ms
  ph803w:device Write and register for response type 9: 000000030f000008000a49564558425246504d51 +1ms
  ph803w:device login success +8ms
  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.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +50ms
2021-06-09 17:36:07.455  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"11","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +2ms
2021-06-09 17:36:07.456  - debug: ph803w.0 (3336) Initialization for PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 done (1/1)
  ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +101ms
  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
2021-06-09 17:36:07.492  - debug: ph803w.0 (3336) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
  ph803w:discovery Parsing discovered device: 192.168.88.128:12414 - 00000003780000040016327471526138384667615553354178674152565975670006e8db848c4b17000830343032303033410020326433643935346439626237343162346131396261313135333130343933326200000000000000026170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +2ms
  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
2021-06-09 17:36:07.494  - debug: ph803w.0 (3336) Discovered PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 already known, ignore
  ph803w:device Send ping +4s
  ph803w:device received pong +13ms
  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 +5ms
  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 +7ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":621,"phOutlet":false,"redoxOutlet":true} +3s
2021-06-09 17:36:38.938  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":621,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":621,"phOutlet":false,"redoxOutlet":true} +2ms
  ph803w:device Send ping +521ms
  ph803w:device received pong +4ms
  ph803w:device Send ping +4s
  ph803w:device received pong +7ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +1s
2021-06-09 17:36:44.939  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +2ms
  ph803w:device Send ping +3s
  ph803w:device received pong +4ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":624,"phOutlet":false,"redoxOutlet":true} +3s
2021-06-09 17:36:50.945  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":624,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":624,"phOutlet":false,"redoxOutlet":true} +1ms
  ph803w:device Send ping +531ms
  ph803w:device received pong +6ms
  ph803w:device Send ping +4s
  ph803w:device received pong +9ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +1s
2021-06-09 17:36:56.948  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.12,"redox":623,"phOutlet":false,"redoxOutlet":true} +1ms
  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 +0ms
  ph803w:device Socket close +1ms
  ph803w:device Connected to TCP 192.168.88.128:12416 +25s
2021-06-09 17:37:36.864  - info: ph803w.0 (3336) Connected PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 ... logging in ...
  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 +0ms
  ph803w:device Retrieved data: {"binFlags1":"11","binFlags2":"10","ph":7.15,"redox":601,"phOutlet":false,"redoxOutlet":true} +52ms
2021-06-09 17:37:36.924  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"11","binFlags2":"10","ph":7.15,"redox":601,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Resolve for message type 145: {"binFlags1":"11","binFlags2":"10","ph":7.15,"redox":601,"phOutlet":false,"redoxOutlet":true} +1ms
2021-06-09 17:37:36.926  - debug: ph803w.0 (3336) Initialization for PH803W device 2tqRa88FgaUS5AxgARVYug on IP 192.168.88.128 done (2/1)
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.15,"redox":602,"phOutlet":false,"redoxOutlet":true} +4s
2021-06-09 17:37:40.430  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.15,"redox":602,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.15,"redox":602,"phOutlet":false,"redoxOutlet":true} +1ms
  ph803w:device Send ping +442ms
  ph803w:device received pong +4ms
  ph803w:device Send ping +4s
  ph803w:device received pong +4ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":608,"phOutlet":false,"redoxOutlet":true} +2s
2021-06-09 17:37:46.437  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":608,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":608,"phOutlet":false,"redoxOutlet":true} +1ms
  ph803w:device Send ping +2s
  ph803w:device received pong +4ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":612,"phOutlet":false,"redoxOutlet":true} +4s
2021-06-09 17:37:52.438  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":612,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.14,"redox":612,"phOutlet":false,"redoxOutlet":true} +2ms
  ph803w:device Send ping +448ms
  ph803w:device received pong +4ms
  ph803w:device Send ping +4s
  ph803w:device received pong +4ms
  ph803w:device Retrieved data: {"binFlags1":"100","binFlags2":"10","ph":7.13,"redox":614,"phOutlet":false,"redoxOutlet":true} +2s
2021-06-09 17:37:58.500  - debug: ph803w.0 (3336) Data received for PH803W device 2tqRa88FgaUS5AxgARVYug: {"binFlags1":"100","binFlags2":"10","ph":7.13,"redox":614,"phOutlet":false,"redoxOutlet":true}
  ph803w:device Ignore resolve for message type 145 because no promise stored: {"binFlags1":"100","binFlags2":"10","ph":7.13,"redox":614,"phOutlet":false,"redoxOutlet":true} +1ms
  ph803w:device Send ping +2s
  ph803w:device received pong +5ms

apollon77

@skinni sagte in PH-Messung:

Ok, generell tut alles ... hab den Grund gefunden warum der connected Status falsch ist,. Aber generell tut alles.

Also nochmal GitHub bitte ... besser jetzt?

skinni

@apollon77 jetzt klappts!

apollon77

@skinni Dann kommt die 0.1.5 offiziell

apollon77

Wnn möglich bitte alle mal auf die 0.1.5 gehen damit ich weiss das es bei allen noch tut :-)

skinni

Bei mir ist alles gut :blush: :+1:

ioUser 0

Auch hier alles in Ordnung :+1:

johnbobjamesson

Yeah!

@apollon77 : Vielen Dank für Deine Arbeit! Ich freue mich richtig, könnte mir das stundenlang ansehen, wie der ph Wert stetig steigt :)

apollon77

@johnbobjamesson Ja Ja Ja macht mich nur alle neidisch ... Die zwei Sonden vom Ali sind heute angekommen ... das PH803W (was eigentlich garantierte 10 Tage Lieferung hatte) nicht :-) Aber naja vllt ja morgen. Gemke hat auch heute endlich die Messzelle versendet, die soll morgen kommen. Also noch hab ich ne Chance aufs Wochenende :-)

skinni

Meine Sendung bei Gemke ging auch heute raus, war wohl Versandtag :)

Community Forum

NEWS

PH-Messung

Support us

760

32.4k

81.5k

1.3m