PH-Messung

apollon77

Allerdings habe ich festgestellt, dass die Verbindung zum Gerät getrennt und wieder neu aufgebaut wird. Im Log erscheint dann "Disconnect to..." und einige Sekunden später wieder "Connecting to..."

Zeig doch mal ein Log bevor ich rumrate ... aber ja der Adater bleibt verbinden es sei denn die Verbindung "WLAN .... und ggf Gerät) bricht ab

Role

@apollon77

Danke für die schnelle Info. Ich werd nachher auf jeden Fall noch schauen ob das WLAN/Powerline-Verbindung zuverlässig läuft.

Hier ein Screenshot vom Log.

coyote

@role
Das sieht für mich auch eher wie ein WLAN Verbindungsabbruch aus

apollon77

@role Jupp ... Adapter tut sein bestes

Role

@apollon77 , @coyote

Ja, ist ein WLAN-Problem, hab grad die Fritzbox geprüft. Danke für den Hinweis. Da stand ich etwas auf dem Schlauch, vor allem weil die Abbrüche erst nach einer Weile kamen. Mit der WLAN-Verbindung kann man ja etwas nachhelfen.

Role

Ich hab jetzt noch eine Ergänzung zum "Problem" an/abmelden des PH803W.
Nach dem Hinweis zum WLAN hab ich das an- und abmelden in der Fritzbox geprüft. Dort wurde das an/abmelden ebenfalls protokolliert. Daraufhin habe ich natürlich das WLAN versuchsweise optimiert, d.h. den Repeater näher hin. Das half auch nichts.

Anschließend wollte ich versuchsweise ein eigenes WLAN für den PH803W zur Verfügung stellen um keine Möglichkeit zum wechseln des Repeaters zu geben. Dazu hatte ich dann die Internetsperre in der Fritzbox deaktiviert. Nach dem deaktivieren der Internetsperre in der Fritzbox erfolgte kein an/abmelden im WLAN mehr.

Frage mich nun was hier nach "draußen" gesendet wird. Oder ob nur die Internetverbindung abgefragt wird. Wie handhabt ihr das? Wisst ihr dazu Näheres?
Könnte der Adapter hier noch etwas abfangen, so das keine Internetverbindung nötig ist?

apollon77

@role ich glaube das das Gerät ggf versucht die Herstellercloud zu erreichen. Grundsätzlich kann das die App von dem Ding.

Ggf wird das Gerät selbst instabil wenn es seine Daten nicht sauber loswird an der Stelle und deine disconnects kommen daher das das Gerät nen reset hinlegt.

Der Adapter kann das er nix tun. Um das zu lösen müsstest du ihm DNS technisch für seine Cloud nen anderen Server lokal bei dir unterjubeln und glaube dann nen MQTT Server aufsetzen der quasi die Daten bekommt.
Das ist aber für die meisten User (und erst recht mit fritzbox) nicht einfach umzusetzen. Daher arbeitet der Adapter auch anders.

Tobi68

Habe eben mal versucht das Teil schon mal ins Netzwerk einzubinden.

Geht das mit IOS Geräten nicht mehr?
Hätte sonst nur noch nen Windows PC zur Verfügung..
Ich bekomme nach 5sec. drücken der Wlan taste am 803W kein Wlan von seinem AP angezeigt.

Edit:
Habs irgendwie hinnbekommen, er ist im Netz.
Hagelt aber Fehlermeldungen vom Adapter, wo hängts da?
Habe keine Elektroden angeschlossen, falls es damit zusammen hängen könnte..


UNCAUGHT_EXCEPTION): Without reason

ph803w.0
2022-04-27 08:55:18.987	info	terminating

ph803w.0
2022-04-27 08:55:18.966	error	The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:55:18.965	error	Error: The id is empty! Please provide a valid id. at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19) at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16 at new Promise (<anonymous>) at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16) at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20) at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24) at PH803WDiscovery.emit (events.js:400:28) at PH803WDiscovery.emit (domain.js:475:12) at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)

ph803w.0
2022-04-27 08:55:18.696	error	unhandled promise rejection: The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:55:18.695	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ph803w.0
2022-04-27 08:55:18.691	info	PH803W Device discovered on 192.168.178.134

ph803w.0
2022-04-27 08:55:18.553	info	starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

ph803w.0
2022-04-27 08:54:45.813	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

ph803w.0
2022-04-27 08:54:45.810	info	terminating

ph803w.0
2022-04-27 08:54:45.749	error	The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:54:45.748	error	Error: The id is empty! Please provide a valid id. at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19) at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16 at new Promise (<anonymous>) at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16) at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20) at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24) at PH803WDiscovery.emit (events.js:400:28) at PH803WDiscovery.emit (domain.js:475:12) at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)

ph803w.0
2022-04-27 08:54:45.443	error	unhandled promise rejection: The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:54:45.442	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ph803w.0
2022-04-27 08:54:45.433	info	PH803W Device discovered on 192.168.178.134

ph803w.0
2022-04-27 08:54:45.290	info	starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

ph803w.0
2022-04-27 08:54:12.155	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

ph803w.0
2022-04-27 08:54:12.153	info	terminating

ph803w.0
2022-04-27 08:54:12.127	error	The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:54:12.126	error	Error: The id is empty! Please provide a valid id. at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19) at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16 at new Promise (<anonymous>) at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16) at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20) at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24) at PH803WDiscovery.emit (events.js:400:28) at PH803WDiscovery.emit (domain.js:475:12) at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)

ph803w.0
2022-04-27 08:54:11.874	error	unhandled promise rejection: The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:54:11.873	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ph803w.0
2022-04-27 08:54:11.869	info	PH803W Device discovered on 192.168.178.134

ph803w.0
2022-04-27 08:54:11.602	info	starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

ph803w.0
2022-04-27 08:53:51.371	info	Got terminate signal TERMINATE_YOURSELF

ph803w.0
2022-04-27 08:53:51.368	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

ph803w.0
2022-04-27 08:53:51.366	info	terminating

ph803w.0
2022-04-27 08:53:51.340	error	The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:53:51.338	error	Error: The id is empty! Please provide a valid id. at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19) at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16 at new Promise (<anonymous>) at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16) at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20) at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24) at PH803WDiscovery.emit (events.js:400:28) at PH803WDiscovery.emit (domain.js:475:12) at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)

ph803w.0
2022-04-27 08:53:51.012	error	unhandled promise rejection: The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 08:53:51.011	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ph803w.0
2022-04-27 08:53:51.000	info	PH803W Device discovered on 192.168.178.134

ph803w.0
2022-04-27 08:53:50.718	info	starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

ph803w.0
2022-04-27 08:53:47.554	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

ph803w.0
2022-04-27 08:53:47.552	info	terminating

apollon77

@tobi68 ja, seeehr strange ... Er bekommt vom Gerät beim Discovery keine ID. Bitte lösche nochmal die Instanz und leg Sie neu an. geht es dann?

Tobi68

@apollon77

Nein geht nicht, muss noch was anderes installiert sein?


host.raspberrypi
2022-04-27 10:31:48.366	warn	Do not restart adapter system.adapter.ph803w.0 because restart loop detected
host.raspberrypi
2022-04-27 10:31:48.366	info	Restart adapter system.adapter.ph803w.0 because enabled
host.raspberrypi
2022-04-27 10:31:48.366	error	instance system.adapter.ph803w.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at PH803WDiscovery.emit (domain.js:475:12)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at PH803WDiscovery.emit (events.js:400:28)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20)
host.raspberrypi
2022-04-27 10:31:48.365	error	Caught by controller[1]: at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16)
host.raspberrypi
2022-04-27 10:31:48.364	error	Caught by controller[1]: at new Promise (<anonymous>)
host.raspberrypi
2022-04-27 10:31:48.364	error	Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16
host.raspberrypi
2022-04-27 10:31:48.364	error	Caught by controller[1]: at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23)
host.raspberrypi
2022-04-27 10:31:48.364	error	Caught by controller[1]: at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19)
host.raspberrypi
2022-04-27 10:31:48.363	error	Caught by controller[1]: Error: The id is empty! Please provide a valid id.
host.raspberrypi
2022-04-27 10:31:48.363	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

ph803w.0
2022-04-27 10:31:47.725	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

ph803w.0
2022-04-27 10:31:47.723	info	terminating

ph803w.0
2022-04-27 10:31:47.679	error	The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 10:31:47.677	error	Error: The id is empty! Please provide a valid id. at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19) at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16 at new Promise (<anonymous>) at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16) at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20) at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24) at PH803WDiscovery.emit (events.js:400:28) at PH803WDiscovery.emit (domain.js:475:12) at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)

ph803w.0
2022-04-27 10:31:47.426	error	unhandled promise rejection: The id is empty! Please provide a valid id.

ph803w.0
2022-04-27 10:31:47.425	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

ph803w.0
2022-04-27 10:31:47.421	info	PH803W Device discovered on 192.168.178.134

ph803w.0
2022-04-27 10:31:47.285	info	starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21

apollon77

@tobi68 Ok, dann brauche ich bitte mehr Infos weil das ist komisch das es ohne ID ankommt.

Bitte lösch nochmal die Objekte falls welche da sind. (sollte aber ja nicht).

Dann bitte Adapter stoppen.
Dann eine Shell auf den iobroker host auf machen
Dort DEBUG=ph803* node /opt/iobroker/node_modules/iobroker.ph803w/main.js --debug --logs

Und dann Bitte log posten

apollon77

Bzw eine Frage: Du hast das Gerät jetzt aber schon per App einmalig ins WLAN gebracht und so verbunden? Darf es zu dem Cloud Host reden oder hast du es dem nie erlaubt mit seinem Cloud Host zu reden oder sowas?

Tobi68

@apollon77

Ich habe es mit IOS irgendwie mit der App geschafft das er bei mir im Wlan aufgetaucht ist.
Ich konnte die Installation mit der app aber nicht kl. fertig abschliessen. Er hat von mir die Wlan zugangsdaten bekommen das wars.
Danach hatte ich in der Fritz ein neues Esp Gerät entdeckt.

apollon77

@tobi68 Ok, dann bvllt ein setup was bisher noch nicht so vorkam. Daher mach mal das oben geschriebene Log dann schaue ich

Tobi68

@apollon77

Shell auf den Iobroher host
Hoffe mal mit putty ist das gleiche..:
Noch ne Info, DHCP macht bei mir ne 7590 der 803 ist im Garten-Accespoint per TPLink CPE210 eingebunden.

pi@raspberrypi:~ $ DEBUG=ph803* node /opt/iobroker/node_modules/iobroker.ph803w/main.js --debug --logs
2022-04-27 15:07:10.720  - debug: ph803w.0 (27168) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-04-27 15:07:10.787  - debug: ph803w.0 (27168) Objects client ready ... initialize now
2022-04-27 15:07:10.790  - debug: ph803w.0 (27168) Objects create System PubSub Client
2022-04-27 15:07:10.792  - debug: ph803w.0 (27168) Objects create User PubSub Client
2022-04-27 15:07:10.852  - debug: ph803w.0 (27168) Objects client initialize lua scripts
2022-04-27 15:07:10.860  - debug: ph803w.0 (27168) Objects connected to redis: 127.0.0.1:9001
2022-04-27 15:07:10.899  - debug: ph803w.0 (27168) Redis States: Use Redis connection: 127.0.0.1:9000
2022-04-27 15:07:10.919  - debug: ph803w.0 (27168) States create System PubSub Client
2022-04-27 15:07:10.921  - debug: ph803w.0 (27168) States create User PubSub Client
2022-04-27 15:07:10.955  - debug: ph803w.0 (27168) States connected to redis: 127.0.0.1:9000
2022-04-27 15:07:11.069  - debug: ph803w.0 (27168) Plugin sentry Initialize Plugin (enabled=true)
2022-04-27 15:07:11.486  - info: ph803w.0 (27168) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21
  ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
  ph803w:discovery Send broadcast message 0000000303000003 +2ms
  ph803w:discovery Parsing discovered device: 192.168.178.134:12414 - 000000036400000400000006c45bbed045690008303430323030334100203264336439353464396262373431623461313962613131353331303439333262000000000000000265756170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +94ms
  ph803w:discovery Discovered device: {"ip":"192.168.178.134","id":"","data1":"c45bbed04569","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"euapi.gizwits.com:80","version":"4.1.2"} +1ms
2022-04-27 15:07:11.710  - info: ph803w.0 (27168) PH803W Device  discovered on 192.168.178.134
2022-04-27 15:07:11.712  - debug: ph803w.0 (27168) Start PH803W Device initialization for  on IP 192.168.178.134
2022-04-27 15:07:11.715  - error: ph803w.0 (27168) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-04-27 15:07:11.716  - error: ph803w.0 (27168) unhandled promise rejection: The id is empty! Please provide a valid id.
2022-04-27 15:07:11.986  - error: ph803w.0 (27168) Error: The id is empty! Please provide a valid id.
    at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19)
    at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23)
    at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16
    at new Promise (<anonymous>)
    at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16)
    at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20)
    at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24)
    at PH803WDiscovery.emit (events.js:400:28)
    at PH803WDiscovery.emit (domain.js:475:12)
    at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)
2022-04-27 15:07:11.989  - error: ph803w.0 (27168) The id is empty! Please provide a valid id.
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: The id is empty! Please provide a valid id.
    at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19)
    at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23)
    at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16
    at new Promise (<anonymous>)
    at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16)
    at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20)
    at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24)
    at PH803WDiscovery.emit (events.js:400:28)
    at PH803WDiscovery.emit (domain.js:475:12)
    at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)
2022-04-27 15:07:12.013  - info: ph803w.0 (27168) terminating
2022-04-27 15:07:12.014  - debug: ph803w.0 (27168) Plugin sentry destroyed
2022-04-27 15:07:12.016  - warn: ph803w.0 (27168) Terminated (UNCAUGHT_EXCEPTION): Without reason

Tobi68

@apollon77 sagte in PH-Messung:

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

Und noch einmal genau in der Reihenfolge die die beschrieben hast:

pi@raspberrypi:~ $ DEBUG=ph803* node /opt/iobroker/node_modules/iobroker.ph803w/                                                                                                                                                             main.js --debug --logs
2022-04-27 15:11:19.463  - debug: ph803w.0 (27608) Redis Objects: Use Redis conn                                                                                                                                                             ection: 127.0.0.1:9001
2022-04-27 15:11:19.532  - debug: ph803w.0 (27608) Objects client ready ... init                                                                                                                                                             ialize now
2022-04-27 15:11:19.534  - debug: ph803w.0 (27608) Objects create System PubSub                                                                                                                                                              Client
2022-04-27 15:11:19.536  - debug: ph803w.0 (27608) Objects create User PubSub Cl                                                                                                                                                             ient
2022-04-27 15:11:19.612  - debug: ph803w.0 (27608) Objects client initialize lua                                                                                                                                                              scripts
2022-04-27 15:11:19.619  - debug: ph803w.0 (27608) Objects connected to redis: 1                                                                                                                                                             27.0.0.1:9001
2022-04-27 15:11:19.654  - debug: ph803w.0 (27608) Redis States: Use Redis conne                                                                                                                                                             ction: 127.0.0.1:9000
2022-04-27 15:11:19.674  - debug: ph803w.0 (27608) States create System PubSub C                                                                                                                                                             lient
2022-04-27 15:11:19.676  - debug: ph803w.0 (27608) States create User PubSub Cli                                                                                                                                                             ent
2022-04-27 15:11:19.708  - debug: ph803w.0 (27608) States connected to redis: 12                                                                                                                                                             7.0.0.1:9000
2022-04-27 15:11:19.821  - debug: ph803w.0 (27608) Plugin sentry Initialize Plug                                                                                                                                                             in (enabled=true)
2022-04-27 15:11:20.032  - error: ph803w.0 (27608) adapter disabled
2022-04-27 15:11:20.241  - info: ph803w.0 (27608) starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.ph803w, node: v14.18.3, js-controller: 4.0.21
  ph803w:discovery Listen for local PH803W devices on port 12414 +0ms
  ph803w:discovery Send broadcast message 0000000303000003 +1ms
  ph803w:discovery Parsing discovered device: 192.168.178.134:12414 - 000000036400000400000006c45bbed045690008303430323030334100203264336439353464396262373431623461313962613131353331303439333262000000000000000265756170692e67697a776974732e636f6d3a383000342e312e32003033303330303030 +60ms
  ph803w:discovery Discovered device: {"ip":"192.168.178.134","id":"","data1":"c45bbed04569","data2":"3034303230303341","data3":"2d3d954d9bb741b4a19ba1153104932b","apiServer":"euapi.gizwits.com:80","version":"4.1.2"} +1ms
2022-04-27 15:11:20.399  - info: ph803w.0 (27608) PH803W Device  discovered on 192.168.178.134
2022-04-27 15:11:20.400  - debug: ph803w.0 (27608) Start PH803W Device initialization for  on IP 192.168.178.134
2022-04-27 15:11:20.405  - error: ph803w.0 (27608) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-04-27 15:11:20.406  - error: ph803w.0 (27608) unhandled promise rejection: The id is empty! Please provide a valid id.
2022-04-27 15:11:20.690  - error: ph803w.0 (27608) Error: The id is empty! Please provide a valid id.
    at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19)
    at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23)
    at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16
    at new Promise (<anonymous>)
    at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16)
    at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20)
    at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24)
    at PH803WDiscovery.emit (events.js:400:28)
    at PH803WDiscovery.emit (domain.js:475:12)
    at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)
2022-04-27 15:11:20.692  - error: ph803w.0 (27608) The id is empty! Please provide a valid id.
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: The id is empty! Please provide a valid id.
    at Utils.validateId (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:161:19)
    at Ph803w.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:2142:23)
    at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2116:16
    at new Promise (<anonymous>)
    at Ph803w.extendObjectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2115:16)
    at Ph803w.initDevice (/opt/iobroker/node_modules/iobroker.ph803w/main.js:134:20)
    at PH803WDiscovery.<anonymous> (/opt/iobroker/node_modules/iobroker.ph803w/main.js:113:24)
    at PH803WDiscovery.emit (events.js:400:28)
    at PH803WDiscovery.emit (domain.js:475:12)
    at PH803WDiscovery._parseResponse (/opt/iobroker/node_modules/node-ph803w/lib/discovery.js:149:14)
2022-04-27 15:11:20.713  - info: ph803w.0 (27608) terminating
2022-04-27 15:11:20.714  - debug: ph803w.0 (27608) Plugin sentry destroyed
2022-04-27 15:11:20.715  - warn: ph803w.0 (27608) Terminated (UNCAUGHT_EXCEPTION): Without reason

apollon77

Najaok dann gibts als den Fall das das Gerät keine ID hat Versuch mal die GitHub version vom Adapter bitte.

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?

NEWS

PH-Messung

Support us

1.4k
Online

30.4k
Users

76.7k
Topics

1.2m
Posts

NEWS

PH-Messung

Support us

1.4kOnline

30.4kUsers

76.7kTopics

1.2mPosts

1.4k
Online

30.4k
Users

76.7k
Topics

1.2m
Posts