MQTT-Fehler

[AndyUM61]

Hallo, ich habe seid dem vorletzen Update des MQTT-Adapters immer folgende Fehlermeldungen:

mqtt.0	2016-11-10 18:44:36.952	error	true
mqtt.0	2016-11-10 18:44:36.950	warn	[TuerSensor01] Error: read ECONNRESET
mqtt.0	2016-11-10 18:44:23.637	error	true
mqtt.0	2016-11-10 18:44:23.636	warn	[TuerSensor02] Error: read ECONNRESET
hm-rpc.1	2016-11-10 18:44:20.800	info	setValue ["JEQ0148892:18","STATE",false] BOOL
mqtt.0	2016-11-10 18:44:18.840	error	true
mqtt.0	2016-11-10 18:44:18.838	warn	[TuerSensor02] Error: read ECONNRESET

Auch ein Neustart des Adapters hat bisher nicht geholfen:(

[AndyUM61]

Hat denn keiner diesen Fehler???

[Bluefox]

Kannst du updaten? Ganz normal.

Habe ein paar debug Ausgaben hinzugefügt.

[AndyUM61]

Hallo,

ich habe soeben geupdatet,.

Folgende Fehler treten auf:

host.ARGO-SERVER	2016-11-13 13:24:54.795	info	Restart adapter system.adapter.mqtt.0 because enabled
host.ARGO-SERVER	2016-11-13 13:24:54.795	error	instance system.adapter.mqtt.0 terminated with code 0 (OK)
mqtt.0	2016-11-13 13:24:54.264	error	close: true
ReferenceError:	2016-11-13 13:24:54.264	error	at process._tickCallback (node.js:356:17)
ReferenceError:	2016-11-13 13:24:54.264	error	at nextTickCallbackWith2Args (node.js:442:9)
ReferenceError:	2016-11-13 13:24:54.264	error	at emitErrorNT (net.js:1269:8)
ReferenceError:	2016-11-13 13:24:54.264	error	at Socket.emit (events.js:169:7)
ReferenceError:	2016-11-13 13:24:54.264	error	at emitOne (events.js:82:20)
ReferenceError:	2016-11-13 13:24:54.264	error	at Connection.emit (events.js:169:7)
ReferenceError:	2016-11-13 13:24:54.264	error	at emitOne (events.js:77:13)
ReferenceError:	2016-11-13 13:24:54.264	error	at Connection. (C:\Program Files\ioBroker\node_modules\iobroker.mqtt\lib\server.js:526:63)
ReferenceError:	2016-11-13 13:24:54.264	error	error is not defined
uncaught	2016-11-13 13:24:54.232	error	exception: error is not defined
hm-rpc.1	2016-11-13 13:24:53.732	info	setValue ["JEQ0148892:18","STATE",false] BOOL
host.ARGO-SERVER	2016-11-13 13:22:59.716	info	instance system.adapter.mqtt.0 started with pid 7488

[Bluefox]

Kannst du noch mal vom git updaten?

Aber:
> "ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors.
Da hilft nur Wireshark. Kannst du machen?

[AndyUM61]

Bei zwei meiner Sensoren könnte ich diesen Abbruch ja verstehen, da meine MQTT-Temperatursensoren immer für einige Zeit in den "Tiefschlaf" gehen.

Aber die MQTT-Tür-Sensoren(PIR), sollten eigentlich immer "online" sein.

Das mit Wireshark - muss ich mal schauen, ob ich da zurecht komme.

Nach Update aus Github leider gleiche Fehlermeldung:

host.ARGO-SERVER	2016-11-13 13:46:07.108	info	Restart adapter system.adapter.mqtt.0 because enabled
host.ARGO-SERVER	2016-11-13 13:46:07.108	error	instance system.adapter.mqtt.0 terminated with code 0 (OK)
mqtt.0	2016-11-13 13:46:06.561	error	close: true
ReferenceError:	2016-11-13 13:46:06.561	error	at process._tickCallback (node.js:356:17)
ReferenceError:	2016-11-13 13:46:06.561	error	at nextTickCallbackWith2Args (node.js:442:9)
ReferenceError:	2016-11-13 13:46:06.561	error	at emitErrorNT (net.js:1269:8)
ReferenceError:	2016-11-13 13:46:06.561	error	at Socket.emit (events.js:169:7)
ReferenceError:	2016-11-13 13:46:06.561	error	at emitOne (events.js:82:20)
ReferenceError:	2016-11-13 13:46:06.561	error	at Connection.emit (events.js:169:7)
ReferenceError:	2016-11-13 13:46:06.561	error	at emitOne (events.js:77:13)
ReferenceError:	2016-11-13 13:46:06.561	error	at Connection. (C:\Program Files\ioBroker\node_modules\iobroker.mqtt\lib\server.js:526:63)
ReferenceError:	2016-11-13 13:46:06.561	error	error is not defined
uncaught	2016-11-13 13:46:06.545	error	exception: error is not defined