PH-Messung

[Tobi68]

@apollon77

danke hat geklappt, werde ichs doch in den Pool einbauen

ph803w.0 5785	2022-04-28 03:56:28.318	info	Connected PH803W device 192168178134-1651110988215 on IP 192.168.178.134 ... logging in ...

ph803w.0 5785	2022-04-28 03:56:28.215	info	PH803W Device 192168178134-1651110988215 discovered on 192.168.178.134

ph803w.0 5785	2022-04-28 03:56:28.214	info	PH803W Device 192.168.178.134 has no ID, define one by ourself

ph803w.0 5785	2022-04-28 03:56:27.966	info	starting. Version 1.0.2 (non-npm: Apollon77/ioBroker.ph803w) in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

[apollon77]

@tobi68 korrekte Daten kommen auch?

[Tobi68]

@apollon77 sagte in PH-Messung:

@tobi68 korrekte Daten kommen auch?

Soweit bin ich noch nicht, muss noch 100 Seiten im Poolforum lesen..
Ich habe noch keine Kalibrierlösung.. und habe die Elektroden noch gar nicht angeschlossen..
Hast du bedenken? Dann ziehe ich die Bestellung und Einrichtung vor?

[Tobi68]

@apollon77

Es kommt auf jeden Fall schon mal ne veränderung an.
Hab die Sonden mal angeschlossen. Scheint zu klappen.

[apollon77]

@tobi68 Das reicht ja ... am Ende ists ok wenn die Werte im ioBroker zu denen passen die das Display anzeigt

[daniel_iobroker]

@apollon77
Hi Apollon.
Inzwischen habe ich den ph803w auch im Pool system installiert. Dein Adapter funktioniert soweit super. Das einzige Problem was ich habe ist, wenn ich den ph803w ausschalte und wieder einschalte, dann bekommt er eine andere IP Adresse. Danach findet ihn der Adapter nicht mehr. Auch ein Neustart des Adapters hilft da nichts.
Ich muss dann die Objekte unter dem Ph803 löschen, den Adapter neu starten und dann wird er sofort gefunden..

Allerdings sind dann die werte aus der Datenbank verloren, da die ja neu getrackt werden müssen - ebenso muss ich dann in der vis natürlich die neuen Objekte auswählen.

Wäre es nicht besser, wenn der Adapter den ph803w bei Neustart sucht und sich dann verbindet dann über die id herausfindet, dass es eh das gleiche Gerät ist und dann die bestehenden Objekte weiter aktualisiert?

Oder ist bei mir hier was faul?

[apollon77]

@daniel_iobroker Hm ... zeig mal ein Debug log von einem Adapterstart bitte wo das passiert ist. Ansonsten: Pin die IP zur Mac Adresse doch in deinem Router fest?

[daniel_iobroker]

@apollon77 Sorry, bin erst Heute dazu gekommen, das Log mit dem Laptop zu machen. Hier das log:

2022-05-25 18:03:11.648  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-25 18:03:11.761  - info: ph803w.0 (26058) Got terminate signal TERMINATE_YOURSELF
2022-05-25 18:03:11.787  - info: ph803w.0 (26058) terminating
2022-05-25 18:03:11.795  - debug: ph803w.0 (26058) Plugin sentry destroyed
2022-05-25 18:03:11.797  - info: ph803w.0 (26058) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-25 18:03:11.819  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-25 18:03:12.525  - info: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-25 18:03:15.346  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 31494
2022-05-25 18:03:18.105  - debug: ph803w.0 (31494) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-25 18:03:18.246  - debug: ph803w.0 (31494) Objects client ready ... initialize now
2022-05-25 18:03:18.276  - debug: ph803w.0 (31494) Objects create System PubSub Client
2022-05-25 18:03:18.278  - debug: ph803w.0 (31494) Objects create User PubSub Client
2022-05-25 18:03:18.279  - debug: ph803w.0 (31494) Objects client initialize lua scripts
2022-05-25 18:03:18.788  - debug: ph803w.0 (31494) Objects connected to redis: 127.0.0.1:9001
2022-05-25 18:03:18.799  - debug: ph803w.0 (31494) objectDB connected
2022-05-25 18:03:18.803  - debug: ph803w.0 (31494) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-25 18:03:20.802  - warn: ph803w.0 (31494) slow connection to states DB. Still waiting ...
2022-05-25 18:03:21.166  - debug: ph803w.0 (31494) States create System PubSub Client
2022-05-25 18:03:21.171  - debug: ph803w.0 (31494) States create User PubSub Client
2022-05-25 18:03:22.169  - debug: ph803w.0 (31494) States connected to redis: 127.0.0.1:9000
2022-05-25 18:03:22.171  - debug: ph803w.0 (31494) statesDB connected
2022-05-25 18:03:23.423  - debug: ph803w.0 (31494) Plugin sentry Initialize Plugin (enabled=true)
2022-05-25 18:03:23.431  - info: ph803w.0 (31494) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-05-25 18:03:23.453  - info: ph803w.0 (31494) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-05-25 18:03:23.580  - debug: ph803w.0 (31494) Init 1 known devices without discovery ...
2022-05-25 18:03:23.581  - debug: ph803w.0 (31494) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.21
2022-05-25 18:03:26.918  - info: ph803w.0 (31494) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.21:12416
2022-05-25 18:03:40.036  - info: ph803w.0 (31494) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.21:12416

Eigentlich steht da nicht viel, außer dass er sich mit der bei der initialisierung gefundenen IP verbinden will. Da der PH803w jedoch eine neue IP bekommen hat, geht das natürlich nicht.

Da der PH803w über 2 Repeater verbunden ist, sehe ich im Router leider den PH803w leider gar nicht. Daher kann ich die IP Adresse nicht direkt zuweisen. Das geht nur mit Clients, die direkt mit dem Router verbunden sind (Ist leider bei dem Router so). Alternativ wäre es noch möglich, im PH803w direkt eine IP Adresse zu hinterlegen. Leider ist dafür in der PH803w App keine Möglichkeit vorgesehen.

Am einfachsten wäre es, wenn der Adapter hier nach dem Gerät sucht und dieses dann verbindet - unabhängig der IP Adresse.

Nach dem löschen der Objekte unter dem PH803 Ordner und anschließendem Neustart des Adapaters wird der PH803w sofort mit der gleichen ID gefunden (nur halt anderer IP Adresse). Siehe hier das log dazu:

2022-05-25 18:13:50.140  - info: host.raspberrypi "system.adapter.ph803w.0" enabled
2022-05-25 18:13:52.247  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 30431
2022-05-25 18:13:54.716  - debug: ph803w.0 (30431) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-25 18:13:54.784  - debug: ph803w.0 (30431) Objects client ready ... initialize now
2022-05-25 18:13:54.787  - debug: ph803w.0 (30431) Objects create System PubSub Client
2022-05-25 18:13:54.788  - debug: ph803w.0 (30431) Objects create User PubSub Client
2022-05-25 18:13:54.789  - debug: ph803w.0 (30431) Objects client initialize lua scripts
2022-05-25 18:13:54.826  - debug: ph803w.0 (30431) Objects connected to redis: 127.0.0.1:9001
2022-05-25 18:13:54.837  - debug: ph803w.0 (30431) objectDB connected
2022-05-25 18:13:54.840  - debug: ph803w.0 (30431) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-25 18:13:54.861  - debug: ph803w.0 (30431) States create System PubSub Client
2022-05-25 18:13:54.862  - debug: ph803w.0 (30431) States create User PubSub Client
2022-05-25 18:13:54.882  - debug: ph803w.0 (30431) States connected to redis: 127.0.0.1:9000
2022-05-25 18:13:54.884  - debug: ph803w.0 (30431) statesDB connected
2022-05-25 18:13:55.619  - debug: ph803w.0 (30431) Plugin sentry Initialize Plugin (enabled=true)
2022-05-25 18:13:55.629  - info: ph803w.0 (30431) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-05-25 18:13:55.694  - info: ph803w.0 (30431) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-05-25 18:13:56.093  - info: ph803w.0 (30431) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.19
2022-05-25 18:13:56.096  - debug: ph803w.0 (30431) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19
2022-05-25 18:13:56.412  - info: ph803w.0 (30431) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19 ... logging in ...
2022-05-25 18:13:56.484  - debug: ph803w.0 (30431) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"11","binFlags2":"1","ph":7.62,"redox":731,"phOutlet":true,"redoxOutlet":false}
2022-05-25 18:13:56.486  - debug: ph803w.0 (30431) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19 done (1/1)
2022-05-25 18:15:01.925  - info: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-25 18:16:52.008  - info: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-25 18:17:00.285  - debug: ph803w.0 (30431) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.62,"redox":732,"phOutlet":true,"redoxOutlet":false}

[apollon77]

@daniel_iobroker Und du unterschlägst beim ersten Log nicht vllt was? Weil an sich läuft das Discovery auch wenn er versucht eine andere IP zu verbinden und die internen Datenstrukturen merken sichgerade die IP ... also hätte ich trotzdem eine " ... discovered on ..." Zeile erwartet ....

EDIT 1... aaahhhh ... i seeeeee the issue

[apollon77]

@daniel_iobroker Ok, dann versuch mal die GitHub version ... Und poste bitte mal Debug Log.

Achtung: Mit npm6 können GitHub Installs aktuell 10+Minuten dauern ... einfach Geduld haben.

[daniel_iobroker]

@apollon77 Hab ich gemacht.
Sieht gut aus. Die neue IP Adresse wird erkannt und auch die Objekte werden aktualisiert. Im Debug steht halt weiterhin, dass die "alte" Adresse nicht erreichbar ist.

Hier das log dazu:

2022-05-26 11:00:23.434  - info: host.raspberrypi iobroker upload [5] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/words.js words.js application/javascript
2022-05-26 11:00:23.621  - info: host.raspberrypi iobroker upload [4] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/style.css style.css text/css
2022-05-26 11:00:23.690  - info: host.raspberrypi iobroker upload [3] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/ph803w_icon.png ph803w_icon.png image/png
2022-05-26 11:00:23.756  - info: host.raspberrypi iobroker upload [2] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/ph803w.png ph803w.png image/png
2022-05-26 11:00:23.848  - info: host.raspberrypi iobroker upload [1] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/index_m.html index_m.html text/html
2022-05-26 11:00:23.928  - info: host.raspberrypi iobroker upload [0] ph803w.admin /opt/iobroker/node_modules/iobroker.ph803w/admin/admin.d.ts admin.d.ts video/mp2t
2022-05-26 11:00:24.158  - info: host.raspberrypi iobroker Update "system.adapter.ph803w.0"
2022-05-26 11:00:24.196  - info: ph803w.0 (30431) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:00:24.268  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-26 11:00:24.466  - info: ph803w.0 (30431) Got terminate signal TERMINATE_YOURSELF
2022-05-26 11:00:24.500  - info: ph803w.0 (30431) terminating
2022-05-26 11:00:24.510  - debug: ph803w.0 (30431) Plugin sentry destroyed
2022-05-26 11:00:24.511  - info: ph803w.0 (30431) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-26 11:00:24.539  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-26 11:00:25.330  - info: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-26 11:00:25.539  - info: host.raspberrypi iobroker exit 0
2022-05-26 11:00:27.882  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 25630
2022-05-26 11:00:29.918  - debug: ph803w.0 (25630) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-26 11:00:30.233  - debug: ph803w.0 (25630) Objects client ready ... initialize now
2022-05-26 11:00:30.496  - debug: ph803w.0 (25630) Objects create System PubSub Client
2022-05-26 11:00:30.498  - debug: ph803w.0 (25630) Objects create User PubSub Client
2022-05-26 11:00:30.499  - debug: ph803w.0 (25630) Objects client initialize lua scripts
2022-05-26 11:00:30.629  - debug: ph803w.0 (25630) Objects connected to redis: 127.0.0.1:9001
2022-05-26 11:00:30.650  - debug: ph803w.0 (25630) objectDB connected
2022-05-26 11:00:30.660  - debug: ph803w.0 (25630) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-26 11:00:30.777  - debug: ph803w.0 (25630) States create System PubSub Client
2022-05-26 11:00:30.780  - debug: ph803w.0 (25630) States create User PubSub Client
2022-05-26 11:00:30.830  - debug: ph803w.0 (25630) States connected to redis: 127.0.0.1:9000
2022-05-26 11:00:30.832  - debug: ph803w.0 (25630) statesDB connected
2022-05-26 11:00:32.037  - debug: ph803w.0 (25630) Plugin sentry Initialize Plugin (enabled=true)
2022-05-26 11:00:32.050  - info: ph803w.0 (25630) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-05-26 11:00:32.074  - info: ph803w.0 (25630) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-05-26 11:00:32.209  - debug: ph803w.0 (25630) Init 1 known devices without discovery ...
2022-05-26 11:00:32.212  - debug: ph803w.0 (25630) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19
2022-05-26 11:00:32.544  - info: ph803w.0 (25630) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.16
2022-05-26 11:00:32.545  - debug: ph803w.0 (25630) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16
2022-05-26 11:00:33.979  - info: ph803w.0 (25630) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16 ... logging in ...
2022-05-26 11:00:34.060  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"11","binFlags2":"1","ph":7.7,"redox":701,"phOutlet":true,"redoxOutlet":false}
2022-05-26 11:00:34.061  - debug: ph803w.0 (25630) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16 done (1/2)
2022-05-26 11:00:35.487  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:00:48.596  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:01.716  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:14.836  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:27.956  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:33.652  - info: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-26 11:01:41.086  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416

PS. Das Update hat wirklich ewig gedauert. Danke für den Hinweis.

[daniel_iobroker]

@apollon77

Hier noch ein logauszug nach ein paar Minuten:

2022-05-26 12:11:17.261  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:25.911  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":713,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:11:27.330  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:37.353  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:42.282  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":714,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:11:47.362  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:57.377  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:00.713  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":715,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:12:07.383  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:17.105  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":716,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:12:17.395  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:27.419  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:29.398  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":717,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:12:37.426  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:43.723  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":718,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:12:45.095  - info: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-26 12:12:47.432  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:57.443  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:01.137  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":719,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:13:07.455  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:17.466  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:21.622  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":720,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:13:27.474  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:36.984  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":721,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:13:37.481  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:47.489  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:50.283  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":722,"phOutlet":true,"redoxOutlet":false}
2022-05-26 12:13:57.570  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:14:07.733  - info: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:14:09.742  - debug: ph803w.0 (25630) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.71,"redox":723,"phOutlet":true,"redoxOutlet":false}

Der Adapter wird übrigens als gelb angezeigt. Die Werte werden jedoch aktualisiert

[apollon77]

Alles klar, dann bitte nochmal GitHub und Log bitte wieder posten. War sehr hilfreich

[daniel_iobroker]

@apollon77 Danke für das Anpassen. Freut mich, dass ich dir helfen konnte.
Hier der neue Log nach dem Update aus github:

2022-05-27 08:45:30.547  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-27 08:45:30.873  - info: ph803w.0 (14758) Got terminate signal TERMINATE_YOURSELF
2022-05-27 08:45:30.877  - info: ph803w.0 (14758) terminating
2022-05-27 08:45:30.878  - debug: ph803w.0 (14758) Plugin sentry destroyed
2022-05-27 08:45:30.879  - info: ph803w.0 (14758) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-27 08:45:31.115  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-27 08:45:31.216  - info: ph803w.0 (14758) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:45:31.757  - info: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-27 08:45:34.426  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 22393
2022-05-27 08:45:36.641  - debug: ph803w.0 (22393) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-27 08:45:36.728  - debug: ph803w.0 (22393) Objects client ready ... initialize now
2022-05-27 08:45:36.731  - debug: ph803w.0 (22393) Objects create System PubSub Client
2022-05-27 08:45:36.732  - debug: ph803w.0 (22393) Objects create User PubSub Client
2022-05-27 08:45:36.734  - debug: ph803w.0 (22393) Objects client initialize lua scripts
2022-05-27 08:45:36.777  - debug: ph803w.0 (22393) Objects connected to redis: 127.0.0.1:9001
2022-05-27 08:45:36.787  - debug: ph803w.0 (22393) objectDB connected
2022-05-27 08:45:36.789  - debug: ph803w.0 (22393) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-27 08:45:36.805  - debug: ph803w.0 (22393) States create System PubSub Client
2022-05-27 08:45:36.806  - debug: ph803w.0 (22393) States create User PubSub Client
2022-05-27 08:45:36.845  - debug: ph803w.0 (22393) States connected to redis: 127.0.0.1:9000
2022-05-27 08:45:36.846  - debug: ph803w.0 (22393) statesDB connected
2022-05-27 08:45:37.693  - debug: ph803w.0 (22393) Plugin sentry Initialize Plugin (enabled=true)
2022-05-27 08:45:37.717  - info: ph803w.0 (22393) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-05-27 08:45:37.820  - info: ph803w.0 (22393) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-05-27 08:45:37.972  - debug: ph803w.0 (22393) Init 1 known devices without discovery ...
2022-05-27 08:45:37.975  - debug: ph803w.0 (22393) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16
2022-05-27 08:45:38.264  - info: ph803w.0 (22393) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:45:38.364  - info: ph803w.0 (22393) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.17
2022-05-27 08:45:38.365  - warn: ph803w.0 (22393) Device 5b4qJ9jHFtEQXmuJEMyHoJ already known on undefined and not connected. Overwrite!
2022-05-27 08:45:38.366  - debug: ph803w.0 (22393) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17
2022-05-27 08:45:38.467  - info: ph803w.0 (22393) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 ... logging in ...
2022-05-27 08:45:38.546  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"11","binFlags2":"1","ph":7.8,"redox":735,"phOutlet":true,"redoxOutlet":false}
2022-05-27 08:45:38.547  - debug: ph803w.0 (22393) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 done (1/2)
2022-05-27 08:45:49.416  - info: ph803w.0 (22393) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:50:44.846  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.8,"redox":736,"phOutlet":true,"redoxOutlet":false}
2022-05-27 08:50:50.991  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.8,"redox":735,"phOutlet":true,"redoxOutlet":false}
2022-05-27 08:50:57.003  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.8,"redox":736,"phOutlet":true,"redoxOutlet":false}
2022-05-27 08:51:05.331  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.8,"redox":735,"phOutlet":true,"redoxOutlet":false}
2022-05-27 08:51:12.493  - debug: ph803w.0 (22393) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.8,"redox":736,"phOutlet":true,"redoxOutlet":false}

Es gab einmal die Meldung, dass der ph803w nicht mit der alten ip gefunden wurde. Danach keine Meldung mehr. Sieht sehr gut aus. Danke

[apollon77]

@daniel_iobroker Hi,

im Log gefällt mir noch was nicht ... könntest Du noch ein letztes mal die GitHub version checken bitte?

[dala]

Hi @apollon77 !
I took a lot of inspiration from your java implementation of the client and created a python version to integrate directly in Home Assistant as a custom integration. Still a lot of testing to do and se how it performs over time but have at least come as far as it now shows 5 sensors (ph, orp, in_water?, ph_on and orp_on). https://github.com/dala318/python_ph803w
(Please let me know if you want any more/different credit to your solution shown in my project page)

I selected the approach to keep the connection open and poll the device constantly, could be that it brings to much strain on the HA manager and a better approach would be to only update every 60s or so and then reconnect every time.

For some reason the device discovery will not work in the Home Assistant environment (mine is running on PC in Hyper-V with a virtual switch that gives every VM it's own IP in my home network), probably has something to do with UDS broadcast ing and receiving response within HA. With the stand-alone lib/main it works...

[apollon77]

@dala Hi, great to hear and great that my lib was a help.Credits are completely fine that way.

[daniel_iobroker]

@apollon77 Hi, sorry bin erst heute wieder dazu gekommen.
Hier der log nach dem update aus github von heute:

2022-06-03 06:56:43.854  - debug: ph803w.0 (5707) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:56:49.844  - debug: ph803w.0 (5707) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:56:54.812  - info: host.raspberrypi "system.adapter.ph803w.0" disabled
2022-06-03 06:56:54.813  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-06-03 06:56:54.834  - info: ph803w.0 (5707) Got terminate signal TERMINATE_YOURSELF
2022-06-03 06:56:54.837  - info: ph803w.0 (5707) terminating
2022-06-03 06:56:54.839  - debug: ph803w.0 (5707) Plugin sentry destroyed
2022-06-03 06:56:54.840  - info: ph803w.0 (5707) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-06-03 06:56:54.842  - info: ph803w.0 (5707) Disconnected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 (0/1)
2022-06-03 06:56:55.026  - info: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-06-03 06:56:55.588  - info: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-06-03 06:57:37.502  - info: influxdb.0 (3092) Store 101 buffered influxDB history points
2022-06-03 06:58:12.795  - info: host.raspberrypi "system.adapter.ph803w.0" enabled
2022-06-03 06:58:13.157  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 12291
2022-06-03 06:58:15.153  - debug: ph803w.0 (12291) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-03 06:58:15.242  - debug: ph803w.0 (12291) Objects client ready ... initialize now
2022-06-03 06:58:15.245  - debug: ph803w.0 (12291) Objects create System PubSub Client
2022-06-03 06:58:15.247  - debug: ph803w.0 (12291) Objects create User PubSub Client
2022-06-03 06:58:15.248  - debug: ph803w.0 (12291) Objects client initialize lua scripts
2022-06-03 06:58:15.287  - debug: ph803w.0 (12291) Objects connected to redis: 127.0.0.1:9001
2022-06-03 06:58:15.297  - debug: ph803w.0 (12291) objectDB connected
2022-06-03 06:58:15.300  - debug: ph803w.0 (12291) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-03 06:58:15.322  - debug: ph803w.0 (12291) States create System PubSub Client
2022-06-03 06:58:15.323  - debug: ph803w.0 (12291) States create User PubSub Client
2022-06-03 06:58:15.363  - debug: ph803w.0 (12291) States connected to redis: 127.0.0.1:9000
2022-06-03 06:58:15.365  - debug: ph803w.0 (12291) statesDB connected
2022-06-03 06:58:16.138  - debug: ph803w.0 (12291) Plugin sentry Initialize Plugin (enabled=true)
2022-06-03 06:58:16.142  - info: ph803w.0 (12291) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-06-03 06:58:16.162  - info: ph803w.0 (12291) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-06-03 06:58:16.253  - debug: ph803w.0 (12291) Init 1 known devices without discovery ...
2022-06-03 06:58:16.256  - debug: ph803w.0 (12291) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17
2022-06-03 06:58:16.483  - info: ph803w.0 (12291) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.17:12416
2022-06-03 06:58:16.570  - info: ph803w.0 (12291) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.15
2022-06-03 06:58:16.571  - warn: ph803w.0 (12291) Device 5b4qJ9jHFtEQXmuJEMyHoJ already known on 192.168.8.17 and not connected. Overwrite!
2022-06-03 06:58:16.573  - debug: ph803w.0 (12291) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15
2022-06-03 06:58:16.801  - info: ph803w.0 (12291) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 ... logging in ...
2022-06-03 06:58:16.875  - debug: ph803w.0 (12291) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"11","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:58:16.876  - debug: ph803w.0 (12291) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 done (1/1)
2022-06-03 06:58:24.207  - debug: ph803w.0 (12291) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:58:26.501  - info: ph803w.0 (12291) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.17:12416
2022-06-03 06:58:26.502  - warn: ph803w.0 (12291) Device 5b4qJ9jHFtEQXmuJEMyHoJ already known on 192.168.8.15 and connected. Ignore this old IP 192.168.8.17!
2022-06-03 06:58:26.504  - error: ph803w.0 (12291) uncaught exception: Cannot read property 'destroy' of undefined
2022-06-03 06:58:26.505  - error: ph803w.0 (12291) TypeError: Cannot read property 'destroy' of undefined
    at PH803WDevice.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:218:45)
    at PH803WDevice.emit (events.js:400:28)
    at Socket.<anonymous> (/opt/iobroker/node_modules/node-ph803w/lib/device.js:118:22)
    at Socket.emit (events.js:400:28)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
2022-06-03 06:58:26.506  - error: ph803w.0 (12291) Cannot read property 'destroy' of undefined
2022-06-03 06:58:26.648  - info: ph803w.0 (12291) terminating
2022-06-03 06:58:26.650  - debug: ph803w.0 (12291) Plugin sentry destroyed
2022-06-03 06:58:26.651  - warn: ph803w.0 (12291) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-06-03 06:58:26.654  - info: ph803w.0 (12291) Disconnected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 (0/1)
2022-06-03 06:58:27.531  - error: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-06-03 06:58:27.532  - info: host.raspberrypi Restart adapter system.adapter.ph803w.0 because enabled
2022-06-03 06:58:57.590  - info: host.raspberrypi instance system.adapter.ph803w.0 started with pid 14415
2022-06-03 06:58:59.415  - debug: ph803w.0 (14415) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-03 06:58:59.496  - debug: ph803w.0 (14415) Objects client ready ... initialize now
2022-06-03 06:58:59.499  - debug: ph803w.0 (14415) Objects create System PubSub Client
2022-06-03 06:58:59.500  - debug: ph803w.0 (14415) Objects create User PubSub Client
2022-06-03 06:58:59.501  - debug: ph803w.0 (14415) Objects client initialize lua scripts
2022-06-03 06:58:59.529  - debug: ph803w.0 (14415) Objects connected to redis: 127.0.0.1:9001
2022-06-03 06:58:59.537  - debug: ph803w.0 (14415) objectDB connected
2022-06-03 06:58:59.539  - debug: ph803w.0 (14415) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-03 06:58:59.552  - debug: ph803w.0 (14415) States create System PubSub Client
2022-06-03 06:58:59.553  - debug: ph803w.0 (14415) States create User PubSub Client
2022-06-03 06:58:59.575  - debug: ph803w.0 (14415) States connected to redis: 127.0.0.1:9000
2022-06-03 06:58:59.576  - debug: ph803w.0 (14415) statesDB connected
2022-06-03 06:59:00.498  - debug: ph803w.0 (14415) Plugin sentry Initialize Plugin (enabled=true)
2022-06-03 06:59:00.503  - info: ph803w.0 (14415) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-06-03 06:59:00.529  - info: ph803w.0 (14415) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.17.4, js-controller: 3.3.22
2022-06-03 06:59:00.662  - debug: ph803w.0 (14415) Init 1 known devices without discovery ...
2022-06-03 06:59:00.664  - debug: ph803w.0 (14415) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15
2022-06-03 06:59:00.831  - info: ph803w.0 (14415) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 ... logging in ...
2022-06-03 06:59:00.890  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:00.893  - debug: ph803w.0 (14415) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 done (1/1)
2022-06-03 06:59:00.923  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"11","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:00.956  - debug: ph803w.0 (14415) Discovered PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 already known, ignore
2022-06-03 06:59:06.890  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:13.328  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:14.340  - info: influxdb.0 (3092) Store 101 buffered influxDB history points
2022-06-03 06:59:20.535  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:26.510  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:32.511  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:40.985  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":760,"phOutlet":true,"redoxOutlet":false}
2022-06-03 06:59:58.383  - debug: ph803w.0 (14415) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.64,"redox":761,"phOutlet":true,"redoxOutlet":false}

Bis auf den Fehler nach dem ersten Start des Adapters und anschließendem automatischem Neustart des Adapters, ist mir nichts negatives aufgefallen.

Danke nochmals für das anpassen

[apollon77]

@daniel_iobroker Ok, fix kommt

[punker]

@apollon77

Hi, ich lese hier seit einiger Zeit mit und hab mir auch einen 803w gekauft.
Leider nutze ich FHEM als Hausautomation.
Dein Programm unter SSH funzt einwandfrei.
Aber wie kann ich die Werte an einen MQTT-Server senden bzw. wenigstens in eine Logdatei schreiben?
Diese könnte ich dann in FHEM weiternutzen.

Update: Umleiten in eine Datei hab ich hinbekommen!

LG
Dieter