logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

OpenBeken - Warning "Client [SH-EM-EB-Rolladen1] Message" Spam in IoBroker Log

TPTim 3117 24
Best answers

Why does OpenBeken cause ioBroker to spam warnings like "Client [...] Message ... deleted after 11 retries" over MQTT?

The warning spam is caused by the MQTT QoS setting: OpenBeken’s QoS 2 publishing does not work correctly with ioBroker’s Sonoff adapter, and switching OpenBeken to QoS 1 stops the repeated "deleted after 11 retries" messages [#20944778][#21116324] The fix was tested with the PR that changes QoS from 2 to 1, and the reporter confirmed that after flashing it, the warnings disappeared and both the minimum setup and the power-meter setup worked normally [#20944778][#20945916] The developer later said this likely means QoS 2 is not implemented in the MQTT library used by OpenBeken, so QoS 1 is the correct workaround [#21116324]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 20926348
    TPTim
    Level 2  
    Posts: 12

    Hey guys,
    I'm new to using the open source alternative software OpenBeken.
    I ordered some cheap current measurement power plugs from AliExpress and flashed the OpenBeken SW.

    Everything worked well. I connected the power plug via MQTT to my ioBroker.

    Now I get a ton of warning messages from the device, but I don't know what's wrong and why these messages appear.
    Can you please help me understand what's going on?

    Best Regards,
    TPTim

    Screenshot of logs from an application showing warning messages from sonoff.0 in ioBroker. Screenshot of OpenBeken application log showing MQTT operations and Wi-Fi status details.
  • ADVERTISEMENT
  • #2 20926477
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    Hello, I haven't used much ioBroker, but can you show the content of this "message 590" or whatever that is?
    Helpful post? Buy me a coffee.
  • #3 20927955
    TPTim
    Level 2  
    Posts: 12

    Hi,
    Thanks for your reply.

    The message itself is listed. There are no further details. Today I found over 38k messages in the log. See attachment.
    I found via google more users of OpenBeken in combination with ioBroker which have this problem, but nobody has a solution.

    The warning message in the error log appeared before I configured the flags. Is there something wrong?

    Hopefully,
    TPTim

    Monitor screen showing error message logs in a black console with yellow text. Configuration flags list for MQ, LED, POWER, etc.
  • #4 20929501
    TPTim
    Level 2  
    Posts: 12

    Hi,
    Does OpenBeken send messages to the MQTT broker every second?

    Best Regards,
    TPTim
  • #5 20929505
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    You can customize TELE/STAT intervals with
    Code: text Expand Select all Copy to clipboard
    TasTeleInterval
    command, the default settings are:
    Code: text Expand Select all Copy to clipboard
    
// interval for automatic publish of tasmota tele/sensor and tele/state
static short g_teleState_interval = 120;
static short g_teleSensor_interval = 3;

    See docs:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md

    Regarding the ioBroker message, I have tried searching on their Github but I haven't found any explanation what this might mean. I can change OBK behaviour quickly per request, but I would need to know what's going wrong in order to make a fix, and this message is so crypting that I have no idea what it relates to. Maybe we should first try asking ioBroker guy what does that mean so I can figure out a way to fix it...
    Helpful post? Buy me a coffee.
  • #6 20929812
    TPTim
    Level 2  
    Posts: 12

    Thank you for your reply and time spent on this issue.

    I have searched around regarding the failure behavior.
    I found a lot of people reporting these warnings. But no one was able to fix it.
    Someone wrote that it is related to MQTT messages without acknowledge flag. But I am not familiar enough to understand the behavior.

    Is this information helpful for you?

    Best Regards
    Tim
  • ADVERTISEMENT
  • #7 20943380
    TPTim
    Level 2  
    Posts: 12

    Hey,

    I am trying to figure out in a German forum the ioBroker problem. Until I found the root cause, I tried a different MQTT adapter.
    There I got this log and the connection is automatically closed. Can you tell me what is happening?

    Thank you !!

    Tim MQTT connection log showing various operations for client named SH-EM-EB-Rolladen. Screenshot of an MQTT log on a German forum.
  • #8 20943750
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    TPTim wrote:

    Someone wrote that it is related to MQTT messages without acknowledge flag. But I am not familiar enough to understand the behavior.

    Is this information helpful for you?

    Can you provide more information what is an ackownlodge flag and how it's set?
    We're using MQTT library from LWIP, here's how we publish data:
    Code: C / C++
    Log in, to see the code

    See more at:
    https://github.com/openshwprojects/OpenBK7231..._intf/lwip-2.1.3/src/include/lwip/apps/mqtt.h


    TPTim wrote:

    There i got this log and the connection is automatically closed. Can you tell me what is happening?

    For a start, I'd suggest to try connecting with the simplest device with no extra power metering topics. The disconnection reason is not shown on the log, it's just 256 - disconnected.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #9 20944572
    TPTim
    Level 2  
    Posts: 12
    I have now tried the minimum configuration.
    1 button and a relay configured in OpenBeken. Status/Flags - only flag 30 (for iobroker).

    I noticed that after connecting the warning messages from the "[SH-EM-EB-Rolladen]" device are now less than the other one with full energy meter configuration.
    There is a log that shows the behaviour (I know there are no deep details regarding the messages):

    Code: text Expand Select all Copy to clipboard
    Restart of mqtt broker:

2024-02-04 15:39:22.821 - info: host.ioBroker stopInstance system.adapter.sonoff.0 (force=false, process=true)
2024-02-04 15:39:22.823 - info: sonoff.0 (414) Got terminate signal TERMINATE_YOURSELF
2024-02-04 15:39:22.826 - warn: sonoff.0 (414) State "sonoff.0.SH-EM-EB-Rolladen.alive" has no existing object, this might lead to an error in future versions
2024-02-04 15:39:22.864 - info: host.ioBroker stopInstance system.adapter.sonoff.0 send kill signal
2024-02-04 15:39:23.324 - info: sonoff.0 (414) terminating
2024-02-04 15:39:23.325 - info: sonoff.0 (414) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-02-04 15:39:23.858 - info: host.ioBroker instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-02-04 15:39:25.890 - info: host.ioBroker instance system.adapter.sonoff.0 started with pid 2269
2024-02-04 15:39:26.650 - info: sonoff.0 (2269) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.sonoff, node: v18.19.0, js-controller: 5.0.17
2024-02-04 15:39:26.663 - info: sonoff.0 (2269) Starting MQTT authenticated server on port 1883
2024-02-04 15:39:34.854 - info: sonoff.0 (2269) Client [SH-EM-SA-Waschmaschine] connected with secret 1707061174851_1176
2024-02-04 15:39:34.942 - info: sonoff.0 (2269) Client [SH-EM-WZ-HomeCinema] connected with secret 1707061174941_7757
2024-02-04 15:39:35.162 - info: sonoff.0 (2269) Client [SH-EM-FL-Serverschrank] connected with secret 1707061175161_4821
2024-02-04 15:39:35.375 - info: sonoff.0 (2269) Client [SH-SW-HE-Deckenlicht] connected with secret 1707061175373_8438
2024-02-04 15:39:35.468 - info: sonoff.0 (2269) Client [SH-SW-KL-FlurDeckenLicht] connected with secret 1707061175468_8287
2024-02-04 15:39:35.587 - info: sonoff.0 (2269) Client [SH-SW-HE-Bewegungsmelder] connected with secret 1707061175584_6600
2024-02-04 15:39:35.705 - info: sonoff.0 (2269) Client [SH-EM-HR-CNCFraese] connected with secret 1707061175704_1693
2024-02-04 15:39:35.821 - info: sonoff.0 (2269) Client [SH-EM-KU-Spuelmaschine] connected with secret 1707061175819_5326
2024-02-04 15:39:35.874 - info: sonoff.0 (2269) Client [SH-SW-FL-FlurDeckenLicht] connected with secret 1707061175873_4324
2024-02-04 15:39:38.448 - info: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] connected with secret 1707061178448_4138
2024-02-04 15:39:39.713 - info: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] connected with secret 1707061179712_3072
2024-02-04 15:39:39.720 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen
2024-02-04 15:39:39.725 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.alive
2024-02-04 15:40:02.674 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 8 deleted after 11 retries
2024-02-04 15:40:02.674 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 8 deleted after 11 retries
2024-02-04 15:40:04.674 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 10 deleted after 11 retries
2024-02-04 15:40:04.675 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 9 deleted after 11 retries
2024-02-04 15:40:08.675 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 11 deleted after 11 retries
2024-02-04 15:40:12.677 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 13 deleted after 11 retries
2024-02-04 15:40:12.677 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 12 deleted after 11 retries
2024-02-04 15:40:14.677 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 14 deleted after 11 retries
2024-02-04 15:40:20.679 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 16 deleted after 11 retries
2024-02-04 15:40:20.679 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 15 deleted after 11 retries
2024-02-04 15:40:22.679 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 17 deleted after 11 retries
2024-02-04 15:40:26.680 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 18 deleted after 11 retries
2024-02-04 15:40:28.681 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 22 deleted after 11 retries
2024-02-04 15:40:28.681 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 21 deleted after 11 retries
2024-02-04 15:40:28.682 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 20 deleted after 11 retries
2024-02-04 15:40:28.682 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 19 deleted after 11 retries
2024-02-04 15:40:32.683 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 23 deleted after 11 retries
2024-02-04 15:40:33.728 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Time
2024-02-04 15:40:33.735 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Uptime
2024-02-04 15:40:33.741 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.SleepMode
2024-02-04 15:40:33.746 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.POWER
2024-02-04 15:40:33.751 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_SSId
2024-02-04 15:40:33.757 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_BSSId
2024-02-04 15:40:33.763 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_Channel
2024-02-04 15:40:33.769 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_Mode
2024-02-04 15:40:33.774 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_RSSI
2024-02-04 15:40:33.779 - info: sonoff.0 (2269) new object created: sonoff.0.SH-EM-EB-Rolladen.Wifi_Downtime
2024-02-04 15:40:34.685 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 24 deleted after 11 retries
2024-02-04 15:40:36.685 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 25 deleted after 11 retries
2024-02-04 15:40:38.685 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 26 deleted after 11 retries
2024-02-04 15:40:40.686 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 27 deleted after 11 retries
2024-02-04 15:40:42.686 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 29 deleted after 11 retries
2024-02-04 15:40:42.686 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 28 deleted after 11 retries
2024-02-04 15:40:44.687 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 30 deleted after 11 retries
2024-02-04 15:40:46.687 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 33 deleted after 11 retries
2024-02-04 15:40:46.688 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 32 deleted after 11 retries
2024-02-04 15:40:46.688 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 31 deleted after 11 retries
2024-02-04 15:40:48.688 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 36 deleted after 11 retries
2024-02-04 15:40:48.688 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 34 deleted after 11 retries
2024-02-04 15:40:50.689 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 37 deleted after 11 retries
2024-02-04 15:40:50.689 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 35 deleted after 11 retries
2024-02-04 15:40:52.690 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 38 deleted after 11 retries
2024-02-04 15:40:54.690 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 39 deleted after 11 retries
2024-02-04 15:40:56.690 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 40 deleted after 11 retries
2024-02-04 15:40:58.692 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 41 deleted after 11 retries
2024-02-04 15:40:58.692 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 9 deleted after 11 retries
2024-02-04 15:41:00.692 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 42 deleted after 11 retries
2024-02-04 15:41:04.693 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 43 deleted after 11 retries
2024-02-04 15:41:06.694 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 44 deleted after 11 retries
2024-02-04 15:41:08.695 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 45 deleted after 11 retries
2024-02-04 15:41:14.696 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 47 deleted after 11 retries
2024-02-04 15:41:14.697 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 46 deleted after 11 retries
2024-02-04 15:41:16.698 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 48 deleted after 11 retries
2024-02-04 15:41:22.700 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 50 deleted after 11 retries
2024-02-04 15:41:22.700 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 49 deleted after 11 retries
2024-02-04 15:41:24.701 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 51 deleted after 11 retries
2024-02-04 15:41:26.701 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 52 deleted after 11 retries
2024-02-04 15:41:28.702 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 54 deleted after 11 retries
2024-02-04 15:41:28.702 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 53 deleted after 11 retries
2024-02-04 15:41:30.703 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 56 deleted after 11 retries
2024-02-04 15:41:30.704 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 55 deleted after 11 retries
2024-02-04 15:41:32.704 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 57 deleted after 11 retries
2024-02-04 15:41:34.704 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 59 deleted after 11 retries
2024-02-04 15:41:34.704 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 58 deleted after 11 retries
2024-02-04 15:41:36.704 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 60 deleted after 11 retries
2024-02-04 15:41:38.705 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 62 deleted after 11 retries
2024-02-04 15:41:38.705 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 61 deleted after 11 retries
2024-02-04 15:41:40.705 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 63 deleted after 11 retries
2024-02-04 15:41:42.706 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 64 deleted after 11 retries
2024-02-04 15:41:44.707 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 65 deleted after 11 retries
2024-02-04 15:41:46.708 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 68 deleted after 11 retries
2024-02-04 15:41:46.708 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 67 deleted after 11 retries
2024-02-04 15:41:46.709 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 66 deleted after 11 retries
2024-02-04 15:41:48.709 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 69 deleted after 11 retries
2024-02-04 15:41:54.711 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 71 deleted after 11 retries
2024-02-04 15:41:54.712 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 70 deleted after 11 retries
2024-02-04 15:41:56.712 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 72 deleted after 11 retries
2024-02-04 15:41:58.712 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 74 deleted after 11 retries
2024-02-04 15:42:00.713 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 75 deleted after 11 retries
2024-02-04 15:42:00.713 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 73 deleted after 11 retries
2024-02-04 15:42:04.714 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 76 deleted after 11 retries
2024-02-04 15:42:06.715 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 78 deleted after 11 retries
2024-02-04 15:42:06.715 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 77 deleted after 11 retries
2024-02-04 15:42:10.716 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 79 deleted after 11 retries
2024-02-04 15:42:12.716 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 81 deleted after 11 retries
2024-02-04 15:42:12.717 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 80 deleted after 11 retries
2024-02-04 15:42:16.718 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 82 deleted after 11 retries
2024-02-04 15:42:18.719 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 84 deleted after 11 retries
2024-02-04 15:42:18.719 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 83 deleted after 11 retries
2024-02-04 15:42:22.720 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 85 deleted after 11 retries
2024-02-04 15:42:24.721 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 86 deleted after 11 retries
2024-02-04 15:42:26.721 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 87 deleted after 11 retries
2024-02-04 15:42:28.722 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 90 deleted after 11 retries
2024-02-04 15:42:28.723 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 89 deleted after 11 retries
2024-02-04 15:42:28.723 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 88 deleted after 11 retries
2024-02-04 15:42:30.723 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 91 deleted after 11 retries
2024-02-04 15:42:32.725 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 92 deleted after 11 retries
2024-02-04 15:42:34.727 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 93 deleted after 11 retries
2024-02-04 15:42:36.729 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 94 deleted after 11 retries
2024-02-04 15:42:40.730 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 96 deleted after 11 retries
2024-02-04 15:42:40.730 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 95 deleted after 11 retries
2024-02-04 15:42:42.730 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 97 deleted after 11 retries
2024-02-04 15:42:46.733 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 101 deleted after 11 retries
2024-02-04 15:42:46.733 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 100 deleted after 11 retries
2024-02-04 15:42:46.733 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 99 deleted after 11 retries
2024-02-04 15:42:46.734 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 98 deleted after 11 retries
2024-02-04 15:42:48.734 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 103 deleted after 11 retries
2024-02-04 15:42:48.734 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 102 deleted after 11 retries
2024-02-04 15:42:52.738 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 104 deleted after 11 retries
2024-02-04 15:42:54.738 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 106 deleted after 11 retries
2024-02-04 15:42:54.738 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 105 deleted after 11 retries
2024-02-04 15:43:00.740 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 107 deleted after 11 retries
2024-02-04 15:43:02.740 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 109 deleted after 11 retries
2024-02-04 15:43:02.741 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 108 deleted after 11 retries
2024-02-04 15:43:02.741 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 10 deleted after 11 retries
2024-02-04 15:43:06.742 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 110 deleted after 11 retries
2024-02-04 15:43:10.742 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 112 deleted after 11 retries
2024-02-04 15:43:10.742 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 111 deleted after 11 retries
2024-02-04 15:43:14.745 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 113 deleted after 11 retries
2024-02-04 15:43:16.745 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 114 deleted after 11 retries
2024-02-04 15:43:18.746 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 116 deleted after 11 retries
2024-02-04 15:43:18.746 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 115 deleted after 11 retries
2024-02-04 15:43:20.748 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 117 deleted after 11 retries
2024-02-04 15:43:22.748 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 118 deleted after 11 retries
2024-02-04 15:43:24.748 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 120 deleted after 11 retries
2024-02-04 15:43:24.748 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 119 deleted after 11 retries
2024-02-04 15:43:28.749 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 124 deleted after 11 retries
2024-02-04 15:43:28.749 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 123 deleted after 11 retries
2024-02-04 15:43:28.749 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 122 deleted after 11 retries
2024-02-04 15:43:28.750 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 121 deleted after 11 retries
2024-02-04 15:43:32.749 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 125 deleted after 11 retries
2024-02-04 15:43:34.751 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 14 deleted after 11 retries
2024-02-04 15:43:36.752 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 127 deleted after 11 retries
2024-02-04 15:43:36.752 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 126 deleted after 11 retries
2024-02-04 15:43:36.752 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 13 deleted after 11 retries
2024-02-04 15:43:36.752 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 12 deleted after 11 retries
2024-02-04 15:43:36.752 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 11 deleted after 11 retries
2024-02-04 15:43:40.752 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 128 deleted after 11 retries
2024-02-04 15:43:44.754 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 129 deleted after 11 retries
2024-02-04 15:43:46.755 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 131 deleted after 11 retries
2024-02-04 15:43:46.755 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 130 deleted after 11 retries
2024-02-04 15:43:50.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 133 deleted after 11 retries
2024-02-04 15:43:50.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 132 deleted after 11 retries
2024-02-04 15:43:52.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 135 deleted after 11 retries
2024-02-04 15:43:52.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 134 deleted after 11 retries
2024-02-04 15:43:52.757 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 16 deleted after 11 retries
2024-02-04 15:43:52.757 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 15 deleted after 11 retries
2024-02-04 15:43:54.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 137 deleted after 11 retries
2024-02-04 15:43:54.756 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 136 deleted after 11 retries
2024-02-04 15:43:54.757 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 18 deleted after 11 retries
2024-02-04 15:43:54.757 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 17 deleted after 11 retries
2024-02-04 15:43:58.757 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 138 deleted after 11 retries
2024-02-04 15:44:00.757 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 140 deleted after 11 retries
2024-02-04 15:44:00.757 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 139 deleted after 11 retries
2024-02-04 15:44:02.758 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 141 deleted after 11 retries
2024-02-04 15:44:02.759 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 20 deleted after 11 retries
2024-02-04 15:44:04.760 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 19 deleted after 11 retries
2024-02-04 15:44:06.760 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 143 deleted after 11 retries
2024-02-04 15:44:06.761 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 142 deleted after 11 retries
2024-02-04 15:44:08.760 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 144 deleted after 11 retries
2024-02-04 15:44:12.764 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 146 deleted after 11 retries
2024-02-04 15:44:12.764 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 145 deleted after 11 retries
2024-02-04 15:44:14.764 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 147 deleted after 11 retries
2024-02-04 15:44:16.764 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 149 deleted after 11 retries
2024-02-04 15:44:16.765 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 148 deleted after 11 retries
2024-02-04 15:44:18.765 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 150 deleted after 11 retries
2024-02-04 15:44:22.766 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 22 deleted after 11 retries
2024-02-04 15:44:22.766 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 21 deleted after 11 retries
2024-02-04 15:44:24.767 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 151 deleted after 11 retries
2024-02-04 15:44:26.767 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 153 deleted after 11 retries
2024-02-04 15:44:26.767 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 152 deleted after 11 retries
2024-02-04 15:44:30.770 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 154 deleted after 11 retries
2024-02-04 15:44:32.769 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 157 deleted after 11 retries
2024-02-04 15:44:32.769 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 156 deleted after 11 retries
2024-02-04 15:44:32.769 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 155 deleted after 11 retries
2024-02-04 15:44:34.770 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 158 deleted after 11 retries
2024-02-04 15:44:36.770 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 159 deleted after 11 retries
2024-02-04 15:44:40.770 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 160 deleted after 11 retries
2024-02-04 15:44:42.771 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 161 deleted after 11 retries
2024-02-04 15:44:44.771 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 163 deleted after 11 retries
2024-02-04 15:44:44.772 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 162 deleted after 11 retries
2024-02-04 15:44:46.772 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 164 deleted after 11 retries
2024-02-04 15:44:48.773 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 165 deleted after 11 retries
2024-02-04 15:44:50.774 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 169 deleted after 11 retries
2024-02-04 15:44:50.774 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 168 deleted after 11 retries
2024-02-04 15:44:50.774 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 167 deleted after 11 retries
2024-02-04 15:44:50.775 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 166 deleted after 11 retries
2024-02-04 15:44:52.775 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 170 deleted after 11 retries
2024-02-04 15:44:54.776 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 171 deleted after 11 retries
2024-02-04 15:44:56.776 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 172 deleted after 11 retries
2024-02-04 15:44:58.776 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 174 deleted after 11 retries
2024-02-04 15:44:58.776 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 173 deleted after 11 retries
2024-02-04 15:45:00.776 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 175 deleted after 11 retries
2024-02-04 15:45:00.777 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 23 deleted after 11 retries
2024-02-04 15:45:04.780 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 177 deleted after 11 retries
2024-02-04 15:45:04.780 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 176 deleted after 11 retries
2024-02-04 15:45:06.781 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 178 deleted after 11 retries
2024-02-04 15:45:10.782 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 180 deleted after 11 retries
2024-02-04 15:45:12.783 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 181 deleted after 11 retries
2024-02-04 15:45:12.783 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 179 deleted after 11 retries
2024-02-04 15:45:16.785 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 182 deleted after 11 retries
2024-02-04 15:45:18.785 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 184 deleted after 11 retries
2024-02-04 15:45:18.785 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 183 deleted after 11 retries
2024-02-04 15:45:22.787 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 185 deleted after 11 retries
2024-02-04 15:45:24.788 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 186 deleted after 11 retries
2024-02-04 15:45:26.789 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 187 deleted after 11 retries
2024-02-04 15:45:28.790 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 188 deleted after 11 retries
2024-02-04 15:45:30.791 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 191 deleted after 11 retries
2024-02-04 15:45:30.791 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 190 deleted after 11 retries
2024-02-04 15:45:30.791 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 189 deleted after 11 retries
2024-02-04 15:45:32.792 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 192 deleted after 11 retries
2024-02-04 15:45:32.793 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 26 deleted after 11 retries
2024-02-04 15:45:32.793 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 25 deleted after 11 retries
2024-02-04 15:45:32.793 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 24 deleted after 11 retries
2024-02-04 15:45:34.792 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 193 deleted after 11 retries
2024-02-04 15:45:36.793 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 194 deleted after 11 retries
2024-02-04 15:45:40.793 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 196 deleted after 11 retries
2024-02-04 15:45:40.794 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 195 deleted after 11 retries
2024-02-04 15:45:42.794 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 197 deleted after 11 retries
2024-02-04 15:45:42.794 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 29 deleted after 11 retries
2024-02-04 15:45:42.794 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 28 deleted after 11 retries
2024-02-04 15:45:42.794 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 27 deleted after 11 retries
2024-02-04 15:45:46.795 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 199 deleted after 11 retries
2024-02-04 15:45:46.795 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 198 deleted after 11 retries
2024-02-04 15:45:48.795 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 201 deleted after 11 retries
2024-02-04 15:45:48.795 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 200 deleted after 11 retries
2024-02-04 15:45:50.796 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 202 deleted after 11 retries
2024-02-04 15:45:52.796 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 204 deleted after 11 retries
2024-02-04 15:45:52.796 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 203 deleted after 11 retries
2024-02-04 15:45:54.797 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 205 deleted after 11 retries
2024-02-04 15:45:58.797 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 207 deleted after 11 retries
2024-02-04 15:45:58.797 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 206 deleted after 11 retries
2024-02-04 15:46:00.798 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 208 deleted after 11 retries
2024-02-04 15:46:04.801 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 210 deleted after 11 retries
2024-02-04 15:46:04.801 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 209 deleted after 11 retries
2024-02-04 15:46:06.801 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 211 deleted after 11 retries
2024-02-04 15:46:10.803 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 212 deleted after 11 retries
2024-02-04 15:46:12.803 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 214 deleted after 11 retries
2024-02-04 15:46:12.803 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 213 deleted after 11 retries
2024-02-04 15:46:16.804 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 215 deleted after 11 retries
2024-02-04 15:46:18.806 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 216 deleted after 11 retries
2024-02-04 15:46:20.806 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 217 deleted after 11 retries
2024-02-04 15:46:22.808 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 218 deleted after 11 retries
2024-02-04 15:46:24.808 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 219 deleted after 11 retries
2024-02-04 15:46:26.808 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 220 deleted after 11 retries
2024-02-04 15:46:28.808 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 221 deleted after 11 retries
2024-02-04 15:46:30.809 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 222 deleted after 11 retries
2024-02-04 15:46:32.810 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 225 deleted after 11 retries
2024-02-04 15:46:32.810 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 224 deleted after 11 retries
2024-02-04 15:46:32.810 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 223 deleted after 11 retries
2024-02-04 15:46:34.810 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 226 deleted after 11 retries
2024-02-04 15:46:36.811 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 227 deleted after 11 retries
2024-02-04 15:46:40.812 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 228 deleted after 11 retries
2024-02-04 15:46:42.813 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 229 deleted after 11 retries
2024-02-04 15:46:44.814 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 230 deleted after 11 retries
2024-02-04 15:46:48.816 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 232 deleted after 11 retries
2024-02-04 15:46:48.816 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 231 deleted after 11 retries
2024-02-04 15:46:50.816 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 234 deleted after 11 retries
2024-02-04 15:46:50.816 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 233 deleted after 11 retries
2024-02-04 15:46:52.817 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 236 deleted after 11 retries
2024-02-04 15:46:52.817 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 235 deleted after 11 retries
2024-02-04 15:46:54.817 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 238 deleted after 11 retries
2024-02-04 15:46:54.817 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 237 deleted after 11 retries
2024-02-04 15:46:56.817 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 239 deleted after 11 retries
2024-02-04 15:46:58.818 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 241 deleted after 11 retries
2024-02-04 15:47:00.818 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 242 deleted after 11 retries
2024-02-04 15:47:00.818 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 240 deleted after 11 retries
2024-02-04 15:47:00.818 - warn: sonoff.0 (2269) Client [SH-EM-EB-Rolladen] Message 30 deleted after 11 retries
2024-02-04 15:47:04.820 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 243 deleted after 11 retries
2024-02-04 15:47:06.820 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 245 deleted after 11 retries
2024-02-04 15:47:06.820 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 244 deleted after 11 retries
2024-02-04 15:47:12.822 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 246 deleted after 11 retries
2024-02-04 15:47:14.823 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 248 deleted after 11 retries
2024-02-04 15:47:14.823 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 247 deleted after 11 retries
2024-02-04 15:47:18.825 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 249 deleted after 11 retries
2024-02-04 15:47:20.827 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 251 deleted after 11 retries
2024-02-04 15:47:20.827 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 250 deleted after 11 retries
2024-02-04 15:47:24.828 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 252 deleted after 11 retries
2024-02-04 15:47:26.829 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 253 deleted after 11 retries
2024-02-04 15:47:27.520 - info: web.0 (490) ==> Connected system.user.admin from ::ffff:192.168.178.12
2024-02-04 15:47:28.830 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 254 deleted after 11 retries
2024-02-04 15:47:30.831 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 256 deleted after 11 retries
2024-02-04 15:47:30.831 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 255 deleted after 11 retries
2024-02-04 15:47:32.832 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 259 deleted after 11 retries
2024-02-04 15:47:32.832 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 258 deleted after 11 retries
2024-02-04 15:47:32.832 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 257 deleted after 11 retries
2024-02-04 15:47:34.833 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 260 deleted after 11 retries
2024-02-04 15:47:36.833 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 261 deleted after 11 retries
2024-02-04 15:47:40.835 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 263 deleted after 11 retries
2024-02-04 15:47:40.835 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 262 deleted after 11 retries
2024-02-04 15:47:42.835 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 264 deleted after 11 retries
2024-02-04 15:47:46.837 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 266 deleted after 11 retries
2024-02-04 15:47:46.838 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 265 deleted after 11 retries
2024-02-04 15:47:48.839 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 267 deleted after 11 retries
2024-02-04 15:47:50.839 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 268 deleted after 11 retries
2024-02-04 15:47:52.841 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 271 deleted after 11 retries
2024-02-04 15:47:52.841 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 270 deleted after 11 retries
2024-02-04 15:47:52.841 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 269 deleted after 11 retries
2024-02-04 15:47:54.841 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 272 deleted after 11 retries
2024-02-04 15:47:58.843 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 273 deleted after 11 retries
2024-02-04 15:48:00.843 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 275 deleted after 11 retries
2024-02-04 15:48:00.844 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 274 deleted after 11 retries
2024-02-04 15:48:04.845 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 276 deleted after 11 retries
2024-02-04 15:48:06.846 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 277 deleted after 11 retries
2024-02-04 15:48:08.846 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 278 deleted after 11 retries
2024-02-04 15:48:10.848 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 279 deleted after 11 retries
2024-02-04 15:48:12.849 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 280 deleted after 11 retries
2024-02-04 15:48:14.850 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 281 deleted after 11 retries
2024-02-04 15:48:16.851 - warn: sonoff.0 (2269) Client [SH-EM-WZ-Stehlampe] Message 282 deleted after 11 retries


    Added after 1 [hours] 9 [minutes]:

    >>20943750

    The ACK message is the response from the broker after receiving a published message. Sorry, it is not an ACK flag.
    I also found out that the ack message should not be the problem.

    What I also found while researching this error log problem is this gith thread:
    https://github.com/openshwprojects/OpenBK7231T_App/issues/634
    Have a look if you don't know. There are a lot of people with the same problem.


    Regards
    TPTim
  • #10 20944778
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    Thanks for reminding me about that Github discussion. I've checked it out and replied there, but I still don't know what OBK is exactly missing that is required for ioBroker to stop showing warnings.

    I can see some ACK information in Google:
    https://forum.iobroker.net/topic/33772/mqtt-message-xxx-deleted-after-11-retries/10
    but it still doesn't tell me what exactly is missing.

    Maybe it's related to QOS flag?

    Maybe I need to change QOS from 2 to 1?

    Try this build:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1063
    It has QOS changed from 2 to 1.
    NOTE: I am guessing, I still don't know what is exactly wrong.
    Helpful post? Buy me a coffee.
  • #11 20945090
    TPTim
    Level 2  
    Posts: 12

    Thanks for checking and answering the other git thread too!

    I will try the build with QUS 2.

    But I have to annoy you again... I am on this page:
    Screenshot of a GitHub pull request titled qos1-test #1063.

    How do I get the firmware file? Best would be an OTA flash file.
    I am an electrical engineer but not very familiar with GitHub... :(
  • ADVERTISEMENT
  • #12 20945133
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    Click details, then summary:
    Screenshot of a CI interface with a list of jobs.
    then scroll down:
    Screenshot of a version management platform showing build and artifact information.
    Helpful post? Buy me a coffee.
  • #13 20945916
    TPTim
    Level 2  
    Posts: 12

    😍 This is it! OMG 😍

    The QoS Level 2 is the answer!

    I have now flashed both units with your new SW version and it works. I configured the one back to the power meter settings and that works too. No warning spam in the log.

    System log table with connection and script operation information.

    That was an amazing discovery of yours!



    There are two little things:
    Screen displaying technical data on electricity consumption, including voltage, current, active power, apparent power, reactive power, power factor, and total energy.
    How is it possible to get yesterday's energy consumption?

    And the unit for energy consumption is missing:
    List of measured energy parameters with values in an app.

    If you can see, I have activated the flag:
    Checked option Flag 40 in settings, describing the use of kWh unit instead of Wh for energy consumption.
    It is displayed on the OpenBeken main page as kWh, but it is sent to the MQTT broker in Wh.
    I think if the user sets the flag, it should also be published in the same unit?


    Best regards
    TPTim
  • #14 20949057
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    Hey, I'm glad that you're saying it is solved, but I set QOS to 1, not to 2.
    So you're saying this PR helps on your issue: https://github.com/openshwprojects/OpenBK7231T_App/pull/1063

    This means I need to add ability to set QOS in flags, so all ioBroker users can set it to 1, I guess.


    TPTim wrote:

    There are two little things:
    Screen displaying technical data on electricity consumption, including voltage, current, active power, apparent power, reactive power, power factor, and total energy.
    How is it possible to get yesterday's energy consumption?

    I think I can add it for you, it's in StatusSNS in Tasmota:
    Screenshot of a JSON data snippet about energy consumption.

    TPTim wrote:

    And the unit for energy consumption is missing:
    List of measured energy parameters with values in an app.

    If you can see, I have activated the flag:
    Checked option Flag 40 in settings, describing the use of kWh unit instead of Wh for energy consumption.
    It is displayed on the OpenBeken main page as kwh, but it is sent to the mqtt broker in wh.
    I think if the user sets the flag, it should also be published in the same unit?

    To which publishing are you referring? If you are talking about StatusSNS, then I don't see energy unit there in Tasmota.
    Helpful post? Buy me a coffee.
  • #15 20956546
    TPTim
    Level 2  
    Posts: 12

    Hey @ElektrodaBot,
    thanks! Ok, then the QOS flag is 1. This is the right value for working with IOBroker SonOff Adapter.

    How can I get this JSON Data overview? I did not find the http request syntax on GitHub :(
    Screenshot of a JSON data snippet about energy consumption.

    ElektrodaBot wrote:

    To which publishing are you referring? If you are talking about StatusSNS, then I don't see energy unit there in Tasmota.

    I am referring to tele/SENSORS. This is used by the adapter as default data source.

    Best Regards
    Tim
  • #16 20956547
    ElektrodaBot
    AI OpenAI ChatGPT4  
    Posts: 8812
    Help: 357
    Rate: 937
    TPTim wrote:
    (...) for working with IOBroker SonOff Adapter.

    How can i get this JSON Data overview? I did not found the http request syntax on github :(
    https://obrazki.elektroda.pl/4809535100_1707291458.png


    I am reffering to tele/SENSORS. This is used by the adapter as defold data source.

    Best Regards
    Tim
    Hello Tim,

    It's great to hear that you have the QOS flag set correctly for the IOBroker SonOff Adapter.

    To get the JSON data overview, there is typically a way to make an HTTP request to the device running Tasmota to retrieve its status or sensor data in JSON format. This can usually be done by accessing the Tasmota device's web server using its IP address and the appropriate command. The command to retrieve sensor data is usually something like `http://<Tasmota-IP>/cm?cmnd=Status 10`.

    Regarding the `tele/SENSORS` topic, this is indeed the default payload for sensor data, which is published at regular intervals (as defined by the `TelePeriod` parameter in Tasmota). If you need to retrieve this data manually, you could publish a command to the topic `cmnd/<device_topic>/STATUS` with the payload `10`, which should prompt the device to publish its sensor data to the `tele/SENSORS` topic.

    To clarify, `Status 10` will give you the STATUS10 JSON result which contains the `StatusSNS` information, including sensor readings, which should look similar to the JSON snippet you are referring to.

    Regarding the image you've posted, it appears to be a JSON output showing the `StatusSNS` object with various energy readings, such as "Yesterday" and "Today" energy usage. If you're looking to obtain similar data, ensure that your Tasmota device has energy monitoring capabilities and the Tasmota firmware is configured correctly to report this data.

    If you could provide me with the model of your Tasmota device or any further specifics about your setup, I could perhaps give you a more detailed walkthrough on retrieving the data you're looking for.

    Best regards,
    ElektrodaBot
    You can call me in any topic by writing @ElektrodaBot. Disclaimer: Some answers provided by the ElektrodaBot may be inaccurate. Elektroda not responsible for accuracy, reliability or completeness of the information presented. All ElektrodaBot responses should be verified by the user. OpenAI can monitor and save information entered after calling ElektrodaBot.
  • #17 20972750
    TPTim
    Level 2  
    Posts: 12

    Hey @p.kaczmarek2,
    Thanks for your feedback. Sorry for the late reply, I'm working on other smart home stuff at the same time :)

    Regarding your snippet, I tried to get the energy data as 'yesterday'. But my SNS data does not provide that information.
    This is what I get back by reading 'http://192.168.178.161/cm?cmnd=Status%2010':
    Screenshot of formatted JSON data regarding energy consumption.

    And the web view does not provide it either:
    Smart socket user interface screen showing various energy parameters.

    The hardware is an energy meter plug with a BL0937 power meter chip:
    Energy meter plug with BL0937 chip, EU standard.

    Is it just a setting of open beken, or is it related to the firmware used?

    Best Regards
    Tim
  • #18 20972753
    ElektrodaBot
    AI OpenAI ChatGPT4  
    Posts: 8812
    Help: 357
    Rate: 937
    TPTim wrote:
    (...) ovide it either:
    https://obrazki.elektroda.pl/8578226300_1708553664.png

    The hardware is an energy meter plug with a BL0937 power meter chip:
    https://obrazki.elektroda.pl/8219059000_1708553751.png

    Is it just a setting of open beken, or is it related to the firmware used?

    Best Regards
    Tim
    Tim,

    Based on your description and the images you've provided, it seems that your Tasmota device is not reporting the "Yesterday" energy usage as part of the `StatusSNS` payload. This could be due to a few reasons:

    1. Firmware Support: Ensure that your Tasmota firmware version supports the feature of tracking and reporting "Yesterday" energy usage. You might need to update to the latest available Tasmota firmware version that includes this feature.

    2. Configuration: The Tasmota device needs to be configured correctly to track and report energy usage over time. You may need to enable specific features or set up the device to start recording these statistics.

    To enable periodic energy monitoring statistics, you can use the `EnergyReset` command:
    Code: Text
    Log in, to see the code

    This will reset all energy counters and start recording from that moment.

    3. Device Compatibility: Ensure that the BL0937 chip in your device is properly supported by the Tasmota firmware and is capable of providing the "Yesterday" energy data.

    4. Energy Monitoring Settings: It's possible that the device needs additional configuration to track and retain historical energy data. In the web interface screenshot, it mentions "Periodic Statistics disabled. Use startup command `SetupEnergyStats` to enable function." You may need to enter the command console on your device's web interface and execute the command `SetupEnergyStats` to enable these statistics.

    In the Tasmota console, you can try the following command:
    Code: Text
    Log in, to see the code

    This command might need to be adjusted according to the proper syntax for your Tasmota firmware version.

    5. MQTT and Web Server: If you're primarily using MQTT with Tasmota, make sure that the MQTT broker is correctly receiving and logging this data. If you're using the web server, ensure you're accessing the correct endpoints.

    If you've checked all these aspects and the issue persists, you may want to look into the release notes or documentation of the Tasmota firmware you are using to find any specific notes about energy monitoring.

    Lastly, if you're still not seeing the expected data, consider reaching out to the Tasmota community or checking the Tasmota GitHub issues page for similar cases or potential solutions.

    Best regards,
    ElektrodaBot
    You can call me in any topic by writing @ElektrodaBot. Disclaimer: Some answers provided by the ElektrodaBot may be inaccurate. Elektroda not responsible for accuracy, reliability or completeness of the information presented. All ElektrodaBot responses should be verified by the user. OpenAI can monitor and save information entered after calling ElektrodaBot.
  • #19 21020973
    Osrx
    Level 5  
    Posts: 11
    >>20949057
    Hello, and thank you for your support.

    I have exactly the same issue with iobroker and QOS on MQTT messages.
    Is there any chance that this setting become available in flags or elsewhere?
  • #20 21116324
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    I suspect that QOS 2 is not implemented in our MQTT library... that's why QOS 1 is the solution.

    I updated PR to the latest main version:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1063

    @divadiow @DeDaMrAz can you check that PR with MQTT (Home Assistant) and tell me if it's keeps the stability of the main releases, so I can merge it?
    Helpful post? Buy me a coffee.
  • #21 21116371
    divadiow
    Level 38  
    Posts: 5047
    Help: 438
    Rate: 893
    tested on BK-T plug.

    1063_merge_e4f2580591cb works. it communicates with HA/MQTT

    Desk 1 activity log from June 2024.

    Screenshot of a control interface for a device named Desk with RSSI value -66 dBm and an active toggle.

    Not sure about stability over time.
  • #22 21116445
    DeDaMrAz
    Level 22  
    Posts: 603
    Help: 34
    Rate: 129
    @p.kaczmarek2

    Can you check the N build, compilation failed. I have 2 N sockets that I can try it with.

    Added after 48 [minutes]:

    The PR works on N module

    User interface displaying energy consumption and electrical parameters of a device.
  • #23 21116512
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    Let's leave it overnight and report then to me if i can merge
    Helpful post? Buy me a coffee.
  • #24 21209765
    TPTim
    Level 2  
    Posts: 12
    >>21116512
    Hey, sorry for the very late answer.

    It's working well since weeks! It would be great if you can merge this solution!

    Thanks a lot!
  • #25 21210433
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14606
    Help: 654
    Rate: 12621
    merged, can you check main release?
    https://github.com/openshwprojects/OpenBK7231...mmit/816721e6a00f54b3292fd79f40daed71d94c5990
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around issues faced by a user after flashing OpenBeken firmware onto a current measurement power plug from AliExpress and connecting it to ioBroker via MQTT. The user reports receiving a significant number of warning messages in the ioBroker log, specifically related to MQTT message acknowledgments. Other participants suggest adjusting the QoS (Quality of Service) settings, with a consensus that setting it to QoS 1 resolves the warning spam. The conversation also touches on the need for proper configuration of the device to track energy usage, including the potential for firmware updates to support additional features like reporting yesterday's energy consumption. The final resolution involved merging a pull request that improved MQTT stability and functionality.
Generated by the language model.
Today's popular

FAQ

TL;DR: Users who saw 38k log messages in one day found that changing OpenBeken MQTT from QoS 2 to QoS 1 stopped the ioBroker Sonoff Adapter warning storm. One maintainer summed it up: "QOS 1 is the solution." This FAQ helps OpenBeken and ioBroker users fix Message X deleted after 11 retries, understand the cause, and verify the working firmware path. [#21116324]

Why it matters: This issue can flood ioBroker logs, hide real faults, and make otherwise stable energy-monitoring plugs look broken.

Option ioBroker Sonoff Adapter result MQTT behavior in thread Practical takeaway
OpenBeken with QoS 2 Warning spam appears Messages retried and deleted Poor fit for this adapter setup
OpenBeken with QoS 1 Warnings stopped Devices worked after flashing test build Best fix reported in the thread
Tasmota-style payloads/StatusSNS Used as compatibility reference JSON fields like Yesterday shown as comparison Helpful model, not the direct fix

Key insight: The thread points to a protocol-handling mismatch, not a bad relay, bad plug, or bad MQTT interval. In this setup, lowering MQTT QoS from 2 to 1 solved the problem and was later merged into the main OpenBeken code line. [#21210433]

Quick Facts

  • OpenBeken defaults shown in the thread were g_teleState_interval = 120 seconds and g_teleSensor_interval = 3 seconds, so sensor traffic can be much more frequent than state traffic. [#20929505]
  • One user reported over 38k messages in the ioBroker log before the fix, showing how fast retry-based warning spam can grow. [#20927955]
  • The ioBroker Sonoff Adapter warning format was consistent: Message X deleted after 11 retries, which indicates repeated resend attempts before the adapter dropped the message. [#20944572]
  • The successful test build changed MQTT QoS from 2 to 1; later posts reported it worked on both a BK-T plug and an N-module socket. [#21116445]
  • The problematic energy plug used a BL0937 metering chip, and its HTTP status example was queried with Status 10 from the device web endpoint. [#20972750]

Why does OpenBeken spam ioBroker logs with warnings like "Client [device] Message X deleted after 11 retries" when using the Sonoff MQTT adapter?

It happens because this OpenBeken-plus-ioBroker combination was sending MQTT traffic in a way the Sonoff Adapter kept retrying and then dropping. The thread’s working diagnosis is that QoS 2 caused the mismatch, while QoS 1 stopped the warnings. One affected setup produced tens of thousands of log entries, even with devices otherwise connected and publishing. [#20945916]

How can I fix OpenBeken MQTT warning spam in ioBroker by changing the QoS level from 2 to 1?

Flash a build that changes OpenBeken MQTT QoS from 2 to 1. 1. Open the GitHub pull request build linked in the thread. 2. Download the OTA artifact from the build summary. 3. Flash the device and retest in ioBroker. After that change, the user reported both plugs worked again and the warning spam disappeared, including the unit with full energy-meter settings. [#20945916]

What is MQTT QoS, and why did QoS 1 work with ioBroker Sonoff Adapter while QoS 2 caused problems in OpenBeken?

"MQTT QoS" is a message-delivery setting that controls how an MQTT client sends data and expects confirmation, with higher levels requiring more handshake steps. In this thread, QoS 1 worked because the maintainer suspected QoS 2 was not implemented correctly in the LWIP MQTT library used by OpenBeken. That would explain why ioBroker kept retrying and deleting messages, while QoS 1 stayed stable. [#21116324]

What does the ioBroker warning "Message deleted after 11 retries" actually mean in MQTT communication?

It means the adapter retried a queued MQTT message 11 times and then dropped it. In the logs, ioBroker repeatedly printed lines such as Client [device] Message 8 deleted after 11 retries, which shows the problem was not a single publish failure but a repeated acknowledgement or delivery failure. The warning points to transport-level handling, not to a wrong relay state or wrong power reading. [#20944572]

How do I change the TELE/STAT publish intervals in OpenBeken with TasTeleInterval to reduce MQTT traffic?

Use the TasTeleInterval command to change the automatic Tasmota-style publish intervals. The maintainer stated that the default values were 120 seconds for tele/state and 3 seconds for tele/sensor. Increasing the sensor interval reduces message volume and can make troubleshooting easier, but it did not solve the retry warning by itself in this thread. [#20929505]

Where can I download the OTA firmware file from an OpenBeken GitHub pull request build?

Get it from the pull request build artifacts page. 1. Open the PR. 2. Click Details, then Summary. 3. Scroll down to the generated firmware files and download the OTA image. That was the exact path the maintainer gave when the user asked how to obtain the test firmware without being familiar with GitHub. [#20945133]

How do I request OpenBeken or Tasmota-style JSON data with an HTTP command like Status 10?

Send an HTTP request to the device using http://<device-ip>/cm?cmnd=Status%2010. The thread shows that this returns a JSON-style status payload comparable to Tasmota StatusSNS, and one user tested it directly against 192.168.178.161. This was used to check whether fields like Yesterday energy were present. [#20972750]

Why does OpenBeken disconnect from some MQTT adapters with a generic reason like "256 - disconnected"?

The thread does not show a precise root cause, only a generic disconnect code. The maintainer explicitly said the log showed only 256 - disconnected and did not include the real reason, so he suggested testing first with the simplest device and no extra power-meter topics. That makes this an incomplete diagnostic signal, not a definitive fault code. [#20943750]

What is the BL0937 power metering chip, and how is it used in OpenBeken energy-monitoring plugs?

"BL0937" is a power-metering chip that measures electrical usage data in smart plugs, including the values OpenBeken publishes for energy monitoring. In the thread, the affected plug used a BL0937-based board, and OpenBeken exposed live energy data in its web view and MQTT payloads. The chip itself was not identified as the cause of the retry spam. [#20972750]

How can I get yesterday's energy consumption from an OpenBeken power plug, and is it supported for BL0937 devices?

You cannot assume it is available by default. In the thread, the user queried Status 10 and checked the OpenBeken web view, but Yesterday was still missing on a BL0937 plug. The maintainer said he could add it because Tasmota includes that field in StatusSNS, which means the thread treated it as a firmware-feature gap rather than a simple user setting. [#20949057]

Why is energy shown as kWh on the OpenBeken web page but published as Wh to tele/SENSORS over MQTT?

Because the web UI unit flag did not automatically change the MQTT payload unit in this case. The user reported that OpenBeken displayed kWh on the main page, but tele/SENSORS still published Wh, even after the relevant flag was enabled. The maintainer replied that he did not see an energy unit in Tasmota StatusSNS, so this mismatch remained unresolved in the thread. [#20956546]

OpenBeken vs Tasmota for MQTT with ioBroker: which one is more compatible for energy-monitoring smart plugs?

In this thread, OpenBeken became compatible enough for ioBroker after switching to QoS 1, while Tasmota was mainly a reference for expected JSON fields and payload structure. OpenBeken worked on real energy-monitoring plugs after the patched build, and the maintainer later merged that fix. If you need this exact ioBroker Sonoff Adapter setup, patched or current OpenBeken was the confirmed working path here. [#21210433]

What is the difference between tele/SENSORS, TELE/STAT, and StatusSNS in OpenBeken or Tasmota MQTT payloads?

tele/SENSORS is the default periodic sensor data source the ioBroker adapter used in this setup. tele/state is a separate automatic state publish channel with its own interval, shown as 120 seconds by default. StatusSNS is the JSON block returned by Status 10 over HTTP and was used in the thread as the reference view for fields like energy values, Today, and potentially Yesterday. [#20956546]

If OpenBeken QoS 2 is not fully implemented in the LWIP MQTT library, what side effects should I expect in Home Assistant or ioBroker?

Expect retries, dropped messages, noisy logs, or unstable acknowledgements. The maintainer wrote, "I suspect that QOS 2 is not implemented in our MQTT library... that's why QOS 1 is the solution," and other testers confirmed the QoS 1 PR worked with Home Assistant MQTT on BK-T and N-module devices. The edge case is long-term stability, which testers said still needed overnight confirmation. [#21116371]

What is the best minimal OpenBeken test configuration for troubleshooting MQTT issues before enabling full energy-meter topics?

Use one button, one relay, and only flag 30 for ioBroker first. The user tried exactly that minimal setup and saw fewer warnings than on the full energy-meter configuration, which made it easier to separate MQTT transport issues from extra topic volume. That is the best thread-backed baseline before re-enabling BL0937 power topics and other telemetry. [#20944572]
Generated by the language model.
ADVERTISEMENT