(Mqtt) 2.3.4 hat noch jemand damit ein Problem?
-
Hallo
Frage in die Runde, habe auf 2.3.4 upgedatet und seither einen wiederkehrenden Fehler, es werden keine Werte mehr eingelesen / aktualisiert.
Meine Tests bisher waren downgrade auf 2.3.3 und dann fkt. es einwandfrei, nach Update auf 2.3.4 kommen nach 1-2Tagen keine Werte mehr. Wiederherstellbar.
das schaut dann so aus:
mqtt.0 2021-03-11 18:45:38.942 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:28.142 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:17.467 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:06.768 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:55.918 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:45.169 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:34.569 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:23.769 debug (27026) Client [AMIS] pingreqso wenn es funktioniert:
mqtt.0 2021-03-11 18:51:07.231 debug (23924) Client [AMIS] pingreq mqtt.0 2021-03-11 18:51:06.895 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846746,"2.8.0":19496162,"3.8.1":10815187,"4.8.1":4812729,"1.7.0":5090,"2.7.0":0,"3.7.0":2461,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:51:03.885 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846742,"2.8.0":19496162,"3.8.1":10815185,"4.8.1":4812729,"1.7.0":5090,"2.7.0":0,"3.7.0":2433,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:51:00.877 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846738,"2.8.0":19496162,"3.8.1":10815183,"4.8.1":4812729,"1.7.0":5098,"2.7.0":0,"3.7.0":2446,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:50:59.746 debug (23924) system.adapter.admin.0: logging true mqtt.0 2021-03-11 18:50:57.875 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846734,"2.8.0":19496162,"3.8.1":10815181,"4.8.1":4812729,"1.7.0":5246,"2.7.0":0,"3.7.0":2426,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:56.482 debug (23924) Client [AMIS] pingreq mqtt.0 2021-03-11 18:50:54.873 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846728,"2.8.0":19496162,"3.8.1":10815178,"4.8.1":4812729,"1.7.0":5211,"2.7.0":0,"3.7.0":2439,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:51.877 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846724,"2.8.0":19496162,"3.8.1":10815176,"4.8.1":4812729,"1.7.0":5107,"2.7.0":0,"3.7.0":2449,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:48.879 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846719,"2.8.0":19496162,"3.8.1":10815174,"4.8.1":4812729,"1.7.0":5097,"2.7.0":0,"3.7.0":2439,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:45.873 debug (23924) stateChange mqtt.0.info.connection: {"val":"AMIS","ack":true,"ts":1615485045869,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1615485045869} mqtt.0 2021-03-11 18:50:45.846 debug (23924) Client [AMIS] with keepalive 15 set timeout to 22.5 seconds mqtt.0 2021-03-11 18:50:45.694 info (23924) Client [AMIS] connected with secret 1615485045684_2430 -
Hallo
Frage in die Runde, habe auf 2.3.4 upgedatet und seither einen wiederkehrenden Fehler, es werden keine Werte mehr eingelesen / aktualisiert.
Meine Tests bisher waren downgrade auf 2.3.3 und dann fkt. es einwandfrei, nach Update auf 2.3.4 kommen nach 1-2Tagen keine Werte mehr. Wiederherstellbar.
das schaut dann so aus:
mqtt.0 2021-03-11 18:45:38.942 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:28.142 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:17.467 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:45:06.768 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:55.918 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:45.169 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:34.569 debug (27026) Client [AMIS] pingreq mqtt.0 2021-03-11 18:44:23.769 debug (27026) Client [AMIS] pingreqso wenn es funktioniert:
mqtt.0 2021-03-11 18:51:07.231 debug (23924) Client [AMIS] pingreq mqtt.0 2021-03-11 18:51:06.895 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846746,"2.8.0":19496162,"3.8.1":10815187,"4.8.1":4812729,"1.7.0":5090,"2.7.0":0,"3.7.0":2461,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:51:03.885 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846742,"2.8.0":19496162,"3.8.1":10815185,"4.8.1":4812729,"1.7.0":5090,"2.7.0":0,"3.7.0":2433,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:51:00.877 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846738,"2.8.0":19496162,"3.8.1":10815183,"4.8.1":4812729,"1.7.0":5098,"2.7.0":0,"3.7.0":2446,"4.7.0":0,"1.128.0":0}","ack":true,"t mqtt.0 2021-03-11 18:50:59.746 debug (23924) system.adapter.admin.0: logging true mqtt.0 2021-03-11 18:50:57.875 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846734,"2.8.0":19496162,"3.8.1":10815181,"4.8.1":4812729,"1.7.0":5246,"2.7.0":0,"3.7.0":2426,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:56.482 debug (23924) Client [AMIS] pingreq mqtt.0 2021-03-11 18:50:54.873 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846728,"2.8.0":19496162,"3.8.1":10815178,"4.8.1":4812729,"1.7.0":5211,"2.7.0":0,"3.7.0":2439,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:51.877 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846724,"2.8.0":19496162,"3.8.1":10815176,"4.8.1":4812729,"1.7.0":5107,"2.7.0":0,"3.7.0":2449,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:48.879 debug (23924) stateChange mqtt.0.AMIS: {"val":"{"1.8.0":13846719,"2.8.0":19496162,"3.8.1":10815174,"4.8.1":4812729,"1.7.0":5097,"2.7.0":0,"3.7.0":2439,"4.7.0":0,"1.128.0":0}","ack":true," mqtt.0 2021-03-11 18:50:45.873 debug (23924) stateChange mqtt.0.info.connection: {"val":"AMIS","ack":true,"ts":1615485045869,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1615485045869} mqtt.0 2021-03-11 18:50:45.846 debug (23924) Client [AMIS] with keepalive 15 set timeout to 22.5 seconds mqtt.0 2021-03-11 18:50:45.694 info (23924) Client [AMIS] connected with secret 1615485045684_2430@humidor
Da gibt es schon die Version 2.3.5. Vielleicht mal versuchen? Ansonsten Issue anlegen:
https://github.com/ioBroker/ioBroker.mqtt/issuesNUC i7 64GB mit Proxmox ---- Jarvis Infos Aktualisierungen der Doku auf Instagram verfolgen -> mcuiobroker Instagram
Wenn Euch mein Vorschlag geholfen hat, bitte rechts "^" klicken. -
@humidor
Da gibt es schon die Version 2.3.5. Vielleicht mal versuchen? Ansonsten Issue anlegen:
https://github.com/ioBroker/ioBroker.mqtt/issues -
@humidor
Da gibt es schon die Version 2.3.5. Vielleicht mal versuchen? Ansonsten Issue anlegen:
https://github.com/ioBroker/ioBroker.mqtt/issues
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden539
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge