@apollon77 said in PH-Messung:
... musst du (wenn port weitergeleitet) dann nicht die IP des Routers mit dem Port nehmen?
Das war der entscheidende Hinweis. Ist eigentlich logisch, dass dann die IP vom Repeater angegeben werden muss. Hatte darauf nicht gedacht. Hab die Adresse angepasst und schon ging es 
DANKE
@arteck oh Sorry, hab übersehen dass du einem anderen User geantwortet hast
@arteck
Warum eigentlich nicht?
Ich hatte vorher ein yale Türschloss, dass habe ich über ha eingebunden und über den ha Adapter im iobroker angesteuert. Klappte problemlos.
Habe nun auch das u200 über einen thread Stick und matter in ha eingebunden. Von ha aus kann ich es auch ansteuern. Wenn ich in iobroker den state ändere, dann kommt im Log ein Fehler mit "cannot control....." siehe Bild.
Warum ging das beim yale Schloss und hier über das u200 nicht?
Eine andere Möglichkeit wäre ja noch der umgekehrte Weg. Den schließ oder öffnen Befehl an ha in ein anderes entity schicken und in ha dann verknüpfen. Hab ich aber noch nicht probiert.
Edit:
Ok ich habe jetzt den anderen Weg probiert. Man erstellt sich 2 "Helfer" in ha als z.B switch. Diese verknüpft man dann unter automatisierung mit dem Schloss.
Die 2 Helfer können dann direkt im iobroker angesteuert werden. Hat problemlos funktioniert. Kann jetzt also in iobroker über ha das Schloss öffnen und schließen
@peter-v
Wie hast du denn das Schloß mit smartthings verbunden? Braucht man dafür einen eigenen Hub?
@ben1983
In meinem Fall kann ich leider den Maximalwert nicht nehmen. Es geht um den Stromzähler. Der Wert wird also immer höher. Den Stromzähler lese ich aber direkt am Smartmeter aus und manchmal wird mir dort ein falscher Wert übertragen (zu hoch). Diese Werte möchte ich damit rausfiltern. Das wäre also dann der Fall, wenn die Abweichung zu hoch ist. Diese Funktion hat dein Adapter ja bereits integriert. Es geht nur darum, den Standard-Abweichungswert eintragen zu können.
Z.B.
1.) Wenn der neu übertragene Wert um 10 höher ist als der vorherige, dann ignorieren.
2.) Sollten aber mehrere Werte nacheinander hoch sein, dann soll der Wert wieder gültig sein (Z.B. wenn der Smartmeter eine längere Zeit nicht übertragen hat und dann wieder anfängt. Dann wäre der richtige Wert ja logischerweise um einiges höher als der ursprüngliche Wert vor dem "Ausfall")
Den zweiten Fall könnte ich jedoch mit einem zusätzlichen Blockly Script abfangen. In dieser Form: Sollten nach einer Totzeit wieder Werte kommne, deinen Adapter neu starten. Dann hat er den aktuellen Wert wieder als gültig. Wäre natürlich schöner, wenn das direkt in deinem Adapter passiert, aber so war ja dein Adapter nicht gedacht
@Ben1983
Ich habe heute über einen Link zum iobroker Blog von deinem Adapter erfahren.
Habe ihn gleich installiert (Version 1.0.0 aus dem stable) und wollte damit eigentlich nur Werte ignorieren, wenn diese zu hoch sind. Also eigentlich ohne die glätten Funktion. Habe einen Sensor, der manchmal einen viel zu hohen Wert liefert.
Wo kann ich denn den Standard-Abweichungswert eingeben? Pro Datenpunkt kann ich ja "nur" den Abweichungs-Multiplikator angeben oder?
Hab den Multiplikator mal auf 2 gesetzt. Der Adapter ignoriert aber alle folgenden Werte.
Im log werden immer Infos geschrieben, dass der Wert ignoriert wird, da die Abweichung zu hoch ist. Allerdings steht dort auch "The maximal deviation is actual: NaN". Der Adapter (und ich) wissen also nicht, wie hoch die Standard-Abweichung ist.
@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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [32minfo[39m: host.raspberrypi "system.adapter.ph803w.0" disabled
2022-06-03 06:56:54.813 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-06-03 06:56:54.834 - [32minfo[39m: ph803w.0 (5707) Got terminate signal TERMINATE_YOURSELF
2022-06-03 06:56:54.837 - [32minfo[39m: ph803w.0 (5707) terminating
2022-06-03 06:56:54.839 - [34mdebug[39m: ph803w.0 (5707) Plugin sentry destroyed
2022-06-03 06:56:54.840 - [32minfo[39m: ph803w.0 (5707) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-06-03 06:56:54.842 - [32minfo[39m: ph803w.0 (5707) Disconnected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 (0/1)
2022-06-03 06:56:55.026 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-06-03 06:56:55.588 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-06-03 06:57:37.502 - [32minfo[39m: influxdb.0 (3092) Store 101 buffered influxDB history points
2022-06-03 06:58:12.795 - [32minfo[39m: host.raspberrypi "system.adapter.ph803w.0" enabled
2022-06-03 06:58:13.157 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 12291
2022-06-03 06:58:15.153 - [34mdebug[39m: ph803w.0 (12291) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-03 06:58:15.242 - [34mdebug[39m: ph803w.0 (12291) Objects client ready ... initialize now
2022-06-03 06:58:15.245 - [34mdebug[39m: ph803w.0 (12291) Objects create System PubSub Client
2022-06-03 06:58:15.247 - [34mdebug[39m: ph803w.0 (12291) Objects create User PubSub Client
2022-06-03 06:58:15.248 - [34mdebug[39m: ph803w.0 (12291) Objects client initialize lua scripts
2022-06-03 06:58:15.287 - [34mdebug[39m: ph803w.0 (12291) Objects connected to redis: 127.0.0.1:9001
2022-06-03 06:58:15.297 - [34mdebug[39m: ph803w.0 (12291) objectDB connected
2022-06-03 06:58:15.300 - [34mdebug[39m: ph803w.0 (12291) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-03 06:58:15.322 - [34mdebug[39m: ph803w.0 (12291) States create System PubSub Client
2022-06-03 06:58:15.323 - [34mdebug[39m: ph803w.0 (12291) States create User PubSub Client
2022-06-03 06:58:15.363 - [34mdebug[39m: ph803w.0 (12291) States connected to redis: 127.0.0.1:9000
2022-06-03 06:58:15.365 - [34mdebug[39m: ph803w.0 (12291) statesDB connected
2022-06-03 06:58:16.138 - [34mdebug[39m: ph803w.0 (12291) Plugin sentry Initialize Plugin (enabled=true)
2022-06-03 06:58:16.142 - [32minfo[39m: 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 - [32minfo[39m: 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 - [34mdebug[39m: ph803w.0 (12291) Init 1 known devices without discovery ...
2022-06-03 06:58:16.256 - [34mdebug[39m: ph803w.0 (12291) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17
2022-06-03 06:58:16.483 - [32minfo[39m: ph803w.0 (12291) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.17:12416
2022-06-03 06:58:16.570 - [32minfo[39m: ph803w.0 (12291) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.15
2022-06-03 06:58:16.571 - [33mwarn[39m: ph803w.0 (12291) Device 5b4qJ9jHFtEQXmuJEMyHoJ already known on 192.168.8.17 and not connected. Overwrite!
2022-06-03 06:58:16.573 - [34mdebug[39m: ph803w.0 (12291) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15
2022-06-03 06:58:16.801 - [32minfo[39m: ph803w.0 (12291) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 ... logging in ...
2022-06-03 06:58:16.875 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (12291) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 done (1/1)
2022-06-03 06:58:24.207 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (12291) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.17:12416
2022-06-03 06:58:26.502 - [33mwarn[39m: 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 - [31merror[39m: ph803w.0 (12291) uncaught exception: Cannot read property 'destroy' of undefined
2022-06-03 06:58:26.505 - [31merror[39m: 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 - [31merror[39m: ph803w.0 (12291) Cannot read property 'destroy' of undefined
2022-06-03 06:58:26.648 - [32minfo[39m: ph803w.0 (12291) terminating
2022-06-03 06:58:26.650 - [34mdebug[39m: ph803w.0 (12291) Plugin sentry destroyed
2022-06-03 06:58:26.651 - [33mwarn[39m: ph803w.0 (12291) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-06-03 06:58:26.654 - [32minfo[39m: ph803w.0 (12291) Disconnected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 (0/1)
2022-06-03 06:58:27.531 - [31merror[39m: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-06-03 06:58:27.532 - [32minfo[39m: host.raspberrypi Restart adapter system.adapter.ph803w.0 because enabled
2022-06-03 06:58:57.590 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 14415
2022-06-03 06:58:59.415 - [34mdebug[39m: ph803w.0 (14415) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-03 06:58:59.496 - [34mdebug[39m: ph803w.0 (14415) Objects client ready ... initialize now
2022-06-03 06:58:59.499 - [34mdebug[39m: ph803w.0 (14415) Objects create System PubSub Client
2022-06-03 06:58:59.500 - [34mdebug[39m: ph803w.0 (14415) Objects create User PubSub Client
2022-06-03 06:58:59.501 - [34mdebug[39m: ph803w.0 (14415) Objects client initialize lua scripts
2022-06-03 06:58:59.529 - [34mdebug[39m: ph803w.0 (14415) Objects connected to redis: 127.0.0.1:9001
2022-06-03 06:58:59.537 - [34mdebug[39m: ph803w.0 (14415) objectDB connected
2022-06-03 06:58:59.539 - [34mdebug[39m: ph803w.0 (14415) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-03 06:58:59.552 - [34mdebug[39m: ph803w.0 (14415) States create System PubSub Client
2022-06-03 06:58:59.553 - [34mdebug[39m: ph803w.0 (14415) States create User PubSub Client
2022-06-03 06:58:59.575 - [34mdebug[39m: ph803w.0 (14415) States connected to redis: 127.0.0.1:9000
2022-06-03 06:58:59.576 - [34mdebug[39m: ph803w.0 (14415) statesDB connected
2022-06-03 06:59:00.498 - [34mdebug[39m: ph803w.0 (14415) Plugin sentry Initialize Plugin (enabled=true)
2022-06-03 06:59:00.503 - [32minfo[39m: 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 - [32minfo[39m: 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 - [34mdebug[39m: ph803w.0 (14415) Init 1 known devices without discovery ...
2022-06-03 06:59:00.664 - [34mdebug[39m: ph803w.0 (14415) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15
2022-06-03 06:59:00.831 - [32minfo[39m: ph803w.0 (14415) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 ... logging in ...
2022-06-03 06:59:00.890 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (14415) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 done (1/1)
2022-06-03 06:59:00.923 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (14415) Discovered PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.15 already known, ignore
2022-06-03 06:59:06.890 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [32minfo[39m: influxdb.0 (3092) Store 101 buffered influxDB history points
2022-06-03 06:59:20.535 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 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 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-27 08:45:30.873 - [32minfo[39m: ph803w.0 (14758) Got terminate signal TERMINATE_YOURSELF
2022-05-27 08:45:30.877 - [32minfo[39m: ph803w.0 (14758) terminating
2022-05-27 08:45:30.878 - [34mdebug[39m: ph803w.0 (14758) Plugin sentry destroyed
2022-05-27 08:45:30.879 - [32minfo[39m: ph803w.0 (14758) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-27 08:45:31.115 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-27 08:45:31.216 - [32minfo[39m: ph803w.0 (14758) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:45:31.757 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-27 08:45:34.426 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 22393
2022-05-27 08:45:36.641 - [34mdebug[39m: ph803w.0 (22393) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-27 08:45:36.728 - [34mdebug[39m: ph803w.0 (22393) Objects client ready ... initialize now
2022-05-27 08:45:36.731 - [34mdebug[39m: ph803w.0 (22393) Objects create System PubSub Client
2022-05-27 08:45:36.732 - [34mdebug[39m: ph803w.0 (22393) Objects create User PubSub Client
2022-05-27 08:45:36.734 - [34mdebug[39m: ph803w.0 (22393) Objects client initialize lua scripts
2022-05-27 08:45:36.777 - [34mdebug[39m: ph803w.0 (22393) Objects connected to redis: 127.0.0.1:9001
2022-05-27 08:45:36.787 - [34mdebug[39m: ph803w.0 (22393) objectDB connected
2022-05-27 08:45:36.789 - [34mdebug[39m: ph803w.0 (22393) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-27 08:45:36.805 - [34mdebug[39m: ph803w.0 (22393) States create System PubSub Client
2022-05-27 08:45:36.806 - [34mdebug[39m: ph803w.0 (22393) States create User PubSub Client
2022-05-27 08:45:36.845 - [34mdebug[39m: ph803w.0 (22393) States connected to redis: 127.0.0.1:9000
2022-05-27 08:45:36.846 - [34mdebug[39m: ph803w.0 (22393) statesDB connected
2022-05-27 08:45:37.693 - [34mdebug[39m: ph803w.0 (22393) Plugin sentry Initialize Plugin (enabled=true)
2022-05-27 08:45:37.717 - [32minfo[39m: 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 - [32minfo[39m: 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 - [34mdebug[39m: ph803w.0 (22393) Init 1 known devices without discovery ...
2022-05-27 08:45:37.975 - [34mdebug[39m: ph803w.0 (22393) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16
2022-05-27 08:45:38.264 - [32minfo[39m: ph803w.0 (22393) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:45:38.364 - [32minfo[39m: ph803w.0 (22393) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.17
2022-05-27 08:45:38.365 - [33mwarn[39m: ph803w.0 (22393) Device 5b4qJ9jHFtEQXmuJEMyHoJ already known on undefined and not connected. Overwrite!
2022-05-27 08:45:38.366 - [34mdebug[39m: ph803w.0 (22393) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17
2022-05-27 08:45:38.467 - [32minfo[39m: ph803w.0 (22393) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 ... logging in ...
2022-05-27 08:45:38.546 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (22393) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.17 done (1/2)
2022-05-27 08:45:49.416 - [32minfo[39m: ph803w.0 (22393) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.16:12416
2022-05-27 08:50:44.846 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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 - [34mdebug[39m: 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
Hier noch ein logauszug nach ein paar Minuten:
2022-05-26 12:11:17.261 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:25.911 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:37.353 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:42.282 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:11:57.377 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:00.713 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:17.105 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:27.419 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:29.398 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:43.723 - [34mdebug[39m: 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 - [32minfo[39m: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-26 12:12:47.432 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:12:57.443 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:01.137 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:17.466 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:21.622 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:36.984 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:47.489 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:13:50.283 - [34mdebug[39m: 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 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:14:07.733 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect ECONNREFUSED 192.168.8.19:12416
2022-05-26 12:14:09.742 - [34mdebug[39m: 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 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 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: host.raspberrypi iobroker Update "system.adapter.ph803w.0"
2022-05-26 11:00:24.196 - [32minfo[39m: ph803w.0 (30431) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:00:24.268 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-26 11:00:24.466 - [32minfo[39m: ph803w.0 (30431) Got terminate signal TERMINATE_YOURSELF
2022-05-26 11:00:24.500 - [32minfo[39m: ph803w.0 (30431) terminating
2022-05-26 11:00:24.510 - [34mdebug[39m: ph803w.0 (30431) Plugin sentry destroyed
2022-05-26 11:00:24.511 - [32minfo[39m: ph803w.0 (30431) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-26 11:00:24.539 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-26 11:00:25.330 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-26 11:00:25.539 - [32minfo[39m: host.raspberrypi iobroker exit 0
2022-05-26 11:00:27.882 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 25630
2022-05-26 11:00:29.918 - [34mdebug[39m: ph803w.0 (25630) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-26 11:00:30.233 - [34mdebug[39m: ph803w.0 (25630) Objects client ready ... initialize now
2022-05-26 11:00:30.496 - [34mdebug[39m: ph803w.0 (25630) Objects create System PubSub Client
2022-05-26 11:00:30.498 - [34mdebug[39m: ph803w.0 (25630) Objects create User PubSub Client
2022-05-26 11:00:30.499 - [34mdebug[39m: ph803w.0 (25630) Objects client initialize lua scripts
2022-05-26 11:00:30.629 - [34mdebug[39m: ph803w.0 (25630) Objects connected to redis: 127.0.0.1:9001
2022-05-26 11:00:30.650 - [34mdebug[39m: ph803w.0 (25630) objectDB connected
2022-05-26 11:00:30.660 - [34mdebug[39m: ph803w.0 (25630) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-26 11:00:30.777 - [34mdebug[39m: ph803w.0 (25630) States create System PubSub Client
2022-05-26 11:00:30.780 - [34mdebug[39m: ph803w.0 (25630) States create User PubSub Client
2022-05-26 11:00:30.830 - [34mdebug[39m: ph803w.0 (25630) States connected to redis: 127.0.0.1:9000
2022-05-26 11:00:30.832 - [34mdebug[39m: ph803w.0 (25630) statesDB connected
2022-05-26 11:00:32.037 - [34mdebug[39m: ph803w.0 (25630) Plugin sentry Initialize Plugin (enabled=true)
2022-05-26 11:00:32.050 - [32minfo[39m: 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 - [32minfo[39m: 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 - [34mdebug[39m: ph803w.0 (25630) Init 1 known devices without discovery ...
2022-05-26 11:00:32.212 - [34mdebug[39m: ph803w.0 (25630) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19
2022-05-26 11:00:32.544 - [32minfo[39m: ph803w.0 (25630) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.16
2022-05-26 11:00:32.545 - [34mdebug[39m: ph803w.0 (25630) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16
2022-05-26 11:00:33.979 - [32minfo[39m: ph803w.0 (25630) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16 ... logging in ...
2022-05-26 11:00:34.060 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (25630) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.16 done (1/2)
2022-05-26 11:00:35.487 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:00:48.596 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:01.716 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:14.836 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:27.956 - [32minfo[39m: ph803w.0 (25630) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.19:12416
2022-05-26 11:01:33.652 - [32minfo[39m: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-26 11:01:41.086 - [32minfo[39m: 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.
@apollon77 Sorry, bin erst Heute dazu gekommen, das Log mit dem Laptop zu machen. Hier das log:
2022-05-25 18:03:11.648 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 (force=false, process=true)
2022-05-25 18:03:11.761 - [32minfo[39m: ph803w.0 (26058) Got terminate signal TERMINATE_YOURSELF
2022-05-25 18:03:11.787 - [32minfo[39m: ph803w.0 (26058) terminating
2022-05-25 18:03:11.795 - [34mdebug[39m: ph803w.0 (26058) Plugin sentry destroyed
2022-05-25 18:03:11.797 - [32minfo[39m: ph803w.0 (26058) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-05-25 18:03:11.819 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.ph803w.0 send kill signal
2022-05-25 18:03:12.525 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-05-25 18:03:15.346 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 31494
2022-05-25 18:03:18.105 - [34mdebug[39m: ph803w.0 (31494) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-25 18:03:18.246 - [34mdebug[39m: ph803w.0 (31494) Objects client ready ... initialize now
2022-05-25 18:03:18.276 - [34mdebug[39m: ph803w.0 (31494) Objects create System PubSub Client
2022-05-25 18:03:18.278 - [34mdebug[39m: ph803w.0 (31494) Objects create User PubSub Client
2022-05-25 18:03:18.279 - [34mdebug[39m: ph803w.0 (31494) Objects client initialize lua scripts
2022-05-25 18:03:18.788 - [34mdebug[39m: ph803w.0 (31494) Objects connected to redis: 127.0.0.1:9001
2022-05-25 18:03:18.799 - [34mdebug[39m: ph803w.0 (31494) objectDB connected
2022-05-25 18:03:18.803 - [34mdebug[39m: ph803w.0 (31494) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-25 18:03:20.802 - [33mwarn[39m: ph803w.0 (31494) slow connection to states DB. Still waiting ...
2022-05-25 18:03:21.166 - [34mdebug[39m: ph803w.0 (31494) States create System PubSub Client
2022-05-25 18:03:21.171 - [34mdebug[39m: ph803w.0 (31494) States create User PubSub Client
2022-05-25 18:03:22.169 - [34mdebug[39m: ph803w.0 (31494) States connected to redis: 127.0.0.1:9000
2022-05-25 18:03:22.171 - [34mdebug[39m: ph803w.0 (31494) statesDB connected
2022-05-25 18:03:23.423 - [34mdebug[39m: ph803w.0 (31494) Plugin sentry Initialize Plugin (enabled=true)
2022-05-25 18:03:23.431 - [32minfo[39m: 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 - [32minfo[39m: 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 - [34mdebug[39m: ph803w.0 (31494) Init 1 known devices without discovery ...
2022-05-25 18:03:23.581 - [34mdebug[39m: ph803w.0 (31494) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.21
2022-05-25 18:03:26.918 - [32minfo[39m: ph803w.0 (31494) PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ Error: Error: connect EHOSTUNREACH 192.168.8.21:12416
2022-05-25 18:03:40.036 - [32minfo[39m: 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 - [32minfo[39m: host.raspberrypi "system.adapter.ph803w.0" enabled
2022-05-25 18:13:52.247 - [32minfo[39m: host.raspberrypi instance system.adapter.ph803w.0 started with pid 30431
2022-05-25 18:13:54.716 - [34mdebug[39m: ph803w.0 (30431) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-05-25 18:13:54.784 - [34mdebug[39m: ph803w.0 (30431) Objects client ready ... initialize now
2022-05-25 18:13:54.787 - [34mdebug[39m: ph803w.0 (30431) Objects create System PubSub Client
2022-05-25 18:13:54.788 - [34mdebug[39m: ph803w.0 (30431) Objects create User PubSub Client
2022-05-25 18:13:54.789 - [34mdebug[39m: ph803w.0 (30431) Objects client initialize lua scripts
2022-05-25 18:13:54.826 - [34mdebug[39m: ph803w.0 (30431) Objects connected to redis: 127.0.0.1:9001
2022-05-25 18:13:54.837 - [34mdebug[39m: ph803w.0 (30431) objectDB connected
2022-05-25 18:13:54.840 - [34mdebug[39m: ph803w.0 (30431) Redis States: Use Redis connection: 127.0.0.1:9000
2022-05-25 18:13:54.861 - [34mdebug[39m: ph803w.0 (30431) States create System PubSub Client
2022-05-25 18:13:54.862 - [34mdebug[39m: ph803w.0 (30431) States create User PubSub Client
2022-05-25 18:13:54.882 - [34mdebug[39m: ph803w.0 (30431) States connected to redis: 127.0.0.1:9000
2022-05-25 18:13:54.884 - [34mdebug[39m: ph803w.0 (30431) statesDB connected
2022-05-25 18:13:55.619 - [34mdebug[39m: ph803w.0 (30431) Plugin sentry Initialize Plugin (enabled=true)
2022-05-25 18:13:55.629 - [32minfo[39m: 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 - [32minfo[39m: 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 - [32minfo[39m: ph803w.0 (30431) PH803W Device 5b4qJ9jHFtEQXmuJEMyHoJ discovered on 192.168.8.19
2022-05-25 18:13:56.096 - [34mdebug[39m: ph803w.0 (30431) Start PH803W Device initialization for 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19
2022-05-25 18:13:56.412 - [32minfo[39m: ph803w.0 (30431) Connected PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19 ... logging in ...
2022-05-25 18:13:56.484 - [34mdebug[39m: 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 - [34mdebug[39m: ph803w.0 (30431) Initialization for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ on IP 192.168.8.19 done (1/1)
2022-05-25 18:15:01.925 - [32minfo[39m: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-25 18:16:52.008 - [32minfo[39m: influxdb.0 (29706) Store 101 buffered influxDB history points
2022-05-25 18:17:00.285 - [34mdebug[39m: ph803w.0 (30431) Data received for PH803W device 5b4qJ9jHFtEQXmuJEMyHoJ: {"binFlags1":"100","binFlags2":"1","ph":7.62,"redox":732,"phOutlet":true,"redoxOutlet":false}
