NEWS
Seltsame Warnung beim Sonof Adapter
-
Ich bekomme immer wieder eine Warnmeldung beim Sonof Adapter im Bezug auf meinen Wemos der den Stromzähler ausliest:
sonoff.0 2022-09-25 19:07:27.719 warn Client [Zaehler] Received puback for unknown message ID: 17204 sonoff.0 2022-09-25 19:07:27.679 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 24948 sonoff.0 2022-09-25 19:07:17.789 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25448 sonoff.0 2022-09-25 19:07:17.788 warn Cannot parse data "SENSOR": _0�tele/tasmota_DAB8C4/STATE{"Time":"2022-09-25T19:07:12","Uptime":"1T03:01:19","UptimeSec":97279,"Heap":6,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":26,"MqttCount":79,"Wifi":{"AP":1,"SSId":"sxxx","BSSId":"82:8A:20:D4:C7:3E","Channel":6,"Mode":"11n","RSSI":52,"Signal":-74,"LinkCount":9,"Downtime":"0T00:05:47"}}0�tele/tasmota_DAB8C4/SENSOR{"Time":"2022-09-25T19:07:12","SML":{"Total_in":6505.51,"Power_curr":1169,_ - SyntaxError: Unexpected token � in JSON at position 1 sonoff.0 2022-09-25 19:06:29.805 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 8762 sonoff.0 2022-09-25 19:06:29.804 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 21349 sonoff.0 2022-09-25 19:06:29.804 warn Client [Zaehler] Received puback for unknown message ID: 14403 sonoff.0 2022-09-25 19:06:28.313 warn Client [Zaehler] Received pubcomp for unknown message ID: 28257 sonoff.0 2022-09-25 19:05:57.784 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 8266 sonoff.0 2022-09-25 19:05:57.783 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25951 sonoff.0 2022-09-25 19:05:57.783 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25903 sonoff.0 2022-09-25 19:05:57.782 warn Client [Zaehler] Received pubcomp for unknown message ID: 14905 sonoff.0 2022-09-25 19:05:57.781 warn Cannot parse data "STATE": _0�tele/tasmota_DAB8C4/STATE{"Time":"2022-09-25T19:05:52","Uptime":"1T02:59:59","UptimeSec":97199,"Heap":6,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":78,"Wifi":{"AP":1,"SSId":"sxxx","BSSId":"82:8A:20:D4:C7:3E","Channel":6,"Mode":"11n","RSSI":56,"Signal":-72,"LinkCoun_ - SyntaxError: Unexpected token � in JSON at position 1Ich kapiere aber leider nicht was da am JSON fehlerhaft ist und warum das dann nur in unregelmäßigen Abständen fehlerhaft kommt.
-
Ich bekomme immer wieder eine Warnmeldung beim Sonof Adapter im Bezug auf meinen Wemos der den Stromzähler ausliest:
sonoff.0 2022-09-25 19:07:27.719 warn Client [Zaehler] Received puback for unknown message ID: 17204 sonoff.0 2022-09-25 19:07:27.679 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 24948 sonoff.0 2022-09-25 19:07:17.789 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25448 sonoff.0 2022-09-25 19:07:17.788 warn Cannot parse data "SENSOR": _0�tele/tasmota_DAB8C4/STATE{"Time":"2022-09-25T19:07:12","Uptime":"1T03:01:19","UptimeSec":97279,"Heap":6,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":26,"MqttCount":79,"Wifi":{"AP":1,"SSId":"sxxx","BSSId":"82:8A:20:D4:C7:3E","Channel":6,"Mode":"11n","RSSI":52,"Signal":-74,"LinkCount":9,"Downtime":"0T00:05:47"}}0�tele/tasmota_DAB8C4/SENSOR{"Time":"2022-09-25T19:07:12","SML":{"Total_in":6505.51,"Power_curr":1169,_ - SyntaxError: Unexpected token � in JSON at position 1 sonoff.0 2022-09-25 19:06:29.805 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 8762 sonoff.0 2022-09-25 19:06:29.804 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 21349 sonoff.0 2022-09-25 19:06:29.804 warn Client [Zaehler] Received puback for unknown message ID: 14403 sonoff.0 2022-09-25 19:06:28.313 warn Client [Zaehler] Received pubcomp for unknown message ID: 28257 sonoff.0 2022-09-25 19:05:57.784 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 8266 sonoff.0 2022-09-25 19:05:57.783 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25951 sonoff.0 2022-09-25 19:05:57.783 warn Client [Zaehler] Received pubrel on Zaehler for unknown messageId 25903 sonoff.0 2022-09-25 19:05:57.782 warn Client [Zaehler] Received pubcomp for unknown message ID: 14905 sonoff.0 2022-09-25 19:05:57.781 warn Cannot parse data "STATE": _0�tele/tasmota_DAB8C4/STATE{"Time":"2022-09-25T19:05:52","Uptime":"1T02:59:59","UptimeSec":97199,"Heap":6,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":78,"Wifi":{"AP":1,"SSId":"sxxx","BSSId":"82:8A:20:D4:C7:3E","Channel":6,"Mode":"11n","RSSI":56,"Signal":-72,"LinkCoun_ - SyntaxError: Unexpected token � in JSON at position 1Ich kapiere aber leider nicht was da am JSON fehlerhaft ist und warum das dann nur in unregelmäßigen Abständen fehlerhaft kommt.
@chaot habe ich auch hin und wieder mal so ähnlich, aber bisher noch nicht herausgefunden warum und woher das kommt, bzw, tritt das hin und wieder auf, wenn ich mein tasmoadmin aufrufe
z.b.2022-09-22 14:46:09.221 - warn: sonoff.0 (1057) Client [Esstisch] Received pubrel on Esstisch for unknown messageId 14882 2022-09-22 14:46:09.222 - warn: sonoff.0 (1057) Client [Esstisch] Received puback for unknown message ID: 17748 2022-09-22 14:46:09.237 - warn: sonoff.0 (1057) Client [Esstisch] Received pubrel on Esstisch for unknown messageId 14882 2022-09-22 14:46:09.238 - warn: sonoff.0 (1057) Client [Esstisch] Received pubcomp for unknown message ID: 29793 2022-09-22 14:46:32.941 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 30067 2022-09-22 14:46:32.942 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubcomp for unknown message ID: 21875 2022-09-22 14:46:32.946 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 14882 2022-09-22 14:46:32.947 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 12148 2022-09-22 14:46:32.956 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubcomp for unknown message ID: 28535oder
2022-09-22 15:55:21.910 - warn: sonoff.0 (1057) Client [Brunnen] Received puback for unknown message ID: 8788 2022-09-22 15:55:21.913 - warn: sonoff.0 (1057) Client [Brunnen] Received pubrec on Brunnen for unknown messageId 20079 2022-09-22 15:55:22.589 - warn: sonoff.0 (1057) Client [Brunnen] Received puback for unknown message ID: 30574 -
@chaot habe ich auch hin und wieder mal so ähnlich, aber bisher noch nicht herausgefunden warum und woher das kommt, bzw, tritt das hin und wieder auf, wenn ich mein tasmoadmin aufrufe
z.b.2022-09-22 14:46:09.221 - warn: sonoff.0 (1057) Client [Esstisch] Received pubrel on Esstisch for unknown messageId 14882 2022-09-22 14:46:09.222 - warn: sonoff.0 (1057) Client [Esstisch] Received puback for unknown message ID: 17748 2022-09-22 14:46:09.237 - warn: sonoff.0 (1057) Client [Esstisch] Received pubrel on Esstisch for unknown messageId 14882 2022-09-22 14:46:09.238 - warn: sonoff.0 (1057) Client [Esstisch] Received pubcomp for unknown message ID: 29793 2022-09-22 14:46:32.941 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 30067 2022-09-22 14:46:32.942 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubcomp for unknown message ID: 21875 2022-09-22 14:46:32.946 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 14882 2022-09-22 14:46:32.947 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubrel on Geschirrspueler for unknown messageId 12148 2022-09-22 14:46:32.956 - warn: sonoff.0 (1057) Client [Geschirrspueler] Received pubcomp for unknown message ID: 28535oder
2022-09-22 15:55:21.910 - warn: sonoff.0 (1057) Client [Brunnen] Received puback for unknown message ID: 8788 2022-09-22 15:55:21.913 - warn: sonoff.0 (1057) Client [Brunnen] Received pubrec on Brunnen for unknown messageId 20079 2022-09-22 15:55:22.589 - warn: sonoff.0 (1057) Client [Brunnen] Received puback for unknown message ID: 30574@crunchip
Danke.
Das ist ja nur eine warnmeldung und alles funktioniert soweit. Also werde ich das wohl erstmal ignorieren.
Wenn das woanders ebenfalls auftaucht scheint es vermutlich irgendwas mit beschädigten Datenpaketen zu tun zu haben. Mal schauen ob ich mit Timeouts spielen kann.
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 Anmelden