I'm hitting the same issue as well.

Ouput of STATUS 0:

15:49:12.195 MQT: stat/smartIR01/STATUS = {"Status":{"Module":62,"DeviceName":"smartIR01","FriendlyName":["smartIR01"],"Topic":"smartIR01","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
15:49:12.202 MQT: stat/smartIR01/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"https://ota.tasmota.com/tasmota/tasmota-ir.bin","RestartReason":"Software/System restart","Uptime":"0T00:04:57","StartupUTC":"2021-06-24T14:44:15","Sleep":50,"CfgHolder":4617,"BootCount":16,"BCResetTime":"2021-06-20T14:27:13","SaveCount":49,"SaveAddress":"FA000"}}
15:49:12.209 MQT: stat/smartIR01/STATUS2 = {"StatusFWR":{"Version":"9.5.0(tasmota)","BuildDateTime":"2021-06-17T08:26:35","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"402/699"}}
15:49:12.216 MQT: stat/smartIR01/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["LaLiLuLeLo",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A0A000000000000","00000180","00006000","00000000"]}}
15:49:12.230 MQT: stat/smartIR01/STATUS4 = {"StatusMEM":{"ProgramSize":607,"Free":396,"Heap":24,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540C8","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45","Sensors":"1,2,3,4,5,6"}}
15:49:12.239 MQT: stat/smartIR01/STATUS5 = {"StatusNET":{"Hostname":"smartIR01-6472","IPAddress":"192.168.1.58","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"8.8.8.8","Mac":"BC:DD:C2:51:99:48","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
15:49:12.244 MQT: stat/smartIR01/STATUS6 = {"StatusMQT":{"MqttHost":"12.12.12.12","MqttPort":12,"MqttClientMask":"smartIR01","MqttClient":"smartIR01","MqttUser":"hehehe","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
15:49:12.252 MQT: stat/smartIR01/STATUS7 = {"StatusTIM":{"UTC":"2021-06-24T14:49:12","Local":"2021-06-24T15:49:12","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"04:47","Sunset":"20:57"}}
15:49:12.259 MQT: stat/smartIR01/STATUS10 = {"StatusSNS":{"Time":"2021-06-24T15:49:12"}}
15:49:12.267 MQT: stat/smartIR01/STATUS11 = {"StatusSTS":{"Time":"2021-06-24T15:49:12","Uptime":"0T00:04:57","UptimeSec":297,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"LaLiLuLeLo","BSSId":"DC:A6:32:EC:BB:E4","Channel":7,"Mode":"11n","RSSI":100,"Signal":-40,"LinkCount":1,"Downtime":"0T00:00:03"}}}```

Console Output : 

15:45:04.307 CMD: IRSend 0,350,300,350,600,300,300,650,600,350,300,600,600,650,600,650,600,300,300,350,300,350,250,650,600,300
15:45:04.314 MQT: stat/smartIR01/RESULT = {"IRSend":"Invalid JSON"}
15:53:41.108 CMD: IRsend 0 +3565-1640+480-360+420-1290+430dE-380D-495+475-410J-335+485dJd+425-445CdN-385MdC-1205N-390+375-460Ct+405dCdNrC-1250Cs+455qG-1260+530rMdC-1255E-345Y-365WdC-365N-1235WcU-330YlMdC-1210E-1230MdCd+370-440CvSt+510dJdN-1240C-355J-365N
15:53:41.115 MQT: stat/smartIR01/RESULT = {"IRSend":"Invalid JSON"}
15:53:59.740 CMD: irsend 0,+3565-1640+480-360+420-1290+430dE-380D-495+475-410J-335+485dJd+425-445CdN-385MdC-1205N-390+375-460Ct+405dCdNrC-1250Cs+455qG-1260+530rMdC-1255E-345Y-365WdC-365N-1235WcU-330YlMdC-1210E-1230MdCd+370-440CvSt+510dJdN-1240C-355J-365N
15:53:59.748 MQT: stat/smartIR01/RESULT = {"IRSend":"Invalid JSON"}

Sorry for bring up this old topic. Is there something that I missed out? I'm using the version 9.5.0 tasmota-ir.bin file alright.

@ascillato I'll be glad to, wait for pull request this week

Description:

This makes changing the fade or speed consistent with other commands that change the light config/state, ie, if SetOption59 is enabled, changes will generate STATE messages. The values of these fields are already part of the STATE information, so this change just makes the STATE messages appear when the values are set.

This allows me to easily add clicky-clicky things in HA to control these parameters. Here's an example of a simple light set up in HA with a switch entity to control whether fade is enabled or not:

light test:
  - platform: mqtt
    name: "Test Light"
    command_topic: "cmnd/twinkle_D41199/POWER"
    state_topic: "tele/twinkle_D41199/STATE"
    state_value_template: "{{value_json.POWER}}"
    payload_on: "ON"
    payload_off: "OFF"
    availability_topic: "tele/twinkle_D41199/LWT"
    payload_available: "Online"
    payload_not_available: "Offline"
    brightness_state_topic: "tele/twinkle_D41199/STATE"
    brightness_command_topic: "cmnd/twinkle_D41199/Dimmer"
    brightness_scale: 100
    brightness_value_template: "{{ value_json.Dimmer }}"

switch test_fade:
  - platform: mqtt
    name: "Test Light Fade"
    availability_topic: "tele/twinkle_D41199/LWT"
    payload_available: "Online"
    payload_not_available: "Offline"
    state_topic: "tele/twinkle_D41199/STATE"
    value_template: "{{ value_json.Fade }}"
    state_on: "ON"
    state_off: "OFF"
    command_topic: "cmnd/twinkle_D41199/FADE"

Checklist:

• [x] The pull request is done against the latest development branch
• [x] Only relevant files were touched
• [x] Only one feature/fix was added per PR and the code change compiles without warnings
• [x] The code change is tested and works on Tasmota core ESP8266 V.2.7.4.9
• [ ] The code change is tested and works with core ESP32 V.1.0.6
• [x] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

This PR was automatically closed because of being stale.

@nightphobos

Hi, please, can you make a PR with your new driver to Tasmota? Thanks

<!-- Thanks for reporting a problem for this project. READ THIS FIRST:

This issue template is meant to REPORT Tasmota software PROBLEMS ONLY

Please DO NOT OPEN AN ISSUE:

• If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Your problem might already be solved. The latest precompiled binaries of Tasmota can be downloaded from http://ota.tasmota.com/tasmota/
• If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team
• If your issue is a flashing issue, please address it to the Tasmota Support Chat
• If your issue is compilation problem, please address it to the Tasmota Support Chat
• If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue
• If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the FAQ and Troubleshooting

Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.

DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed. -->

PROBLEM DESCRIPTION

As mentioned in the title, Tasmota's Telegram command tmsend stopped working with no change in either the Tasmota build or Tasmota settings

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [x] Read the Contributing Guide and Policy and the Code of Conduct
• [x] Searched the problem in issues
• [x] Searched the problem in discussions
• [x] Searched the problem in the docs
• [x] Searched the problem in the chat
• [x] Device used : Wemos D1 Mini
• [x] Tasmota binary firmware version number used: 9.3.1.2
  • [ ] Pre-compiled
  • [x] Self-compiled
• [x] Flashing tools used: PlatformIO
• [x] Provide the output of command: Backlog Template; Module; GPIO 255:

07:39:02.890 CMD: Backlog Template; Module; GPIO 255
07:39:02.893 SRC: WebConsole from 172.20.1.2
07:39:02.896 CMD: Group 0, Index 1, Command "BACKLOG", Data "Template; Module; GPIO 255"
07:39:02.925 SRC: Backlog
07:39:02.928 CMD: Group 0, Index 1, Command "TEMPLATE", Data ""
07:39:02.935 RSL: stat/tasmota_74E359/RESULT = {"NAME":"Generic","GPIO":[1,1,1,1,1856,1888,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}
07:39:03.163 SRC: Backlog
07:39:03.166 CMD: Group 0, Index 1, Command "MODULE", Data ""
07:39:03.171 RSL: stat/tasmota_74E359/RESULT = {"Module":{"18":"Generic"}}
07:39:03.414 SRC: Backlog
07:39:03.417 CMD: Group 0, Index 1, Command "GPIO", Data "255"
07:39:03.425 RSL: stat/tasmota_74E359/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"1856":"SR04 Tri/TX"},"GPIO5":{"1888":"SR04 Ech/RX"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}
07:39:19.761 WIF: Checking connection...

• [ ] If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

• [x] Provide the output of this command: Status 0:

07:40:07.680 CMD: Status 0
07:40:07.683 SRC: WebConsole from 172.20.1.2
07:40:07.686 CMD: Group 0, Index 1, Command "STATUS", Data "0"
07:40:07.691 RSL: stat/tasmota_74E359/STATUS = {"Status":{"Module":18,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"tasmota_74E359","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
07:40:07.696 RSL: stat/tasmota_74E359/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"External System","Uptime":"0T00:13:31","StartupUTC":"2021-06-23T06:26:36","Sleep":50,"CfgHolder":4620,"BootCount":30,"BCResetTime":"2021-06-23T05:41:48","SaveCount":41,"SaveAddress":"FB000"}}
07:40:07.704 RSL: stat/tasmota_74E359/STATUS2 = {"StatusFWR":{"Version":"9.3.1.2(tasmota)","BuildDateTime":"2021-06-23T11:55:37","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"404/699"}}
07:40:07.709 RSL: stat/tasmota_74E359/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":4,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Andromeda",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A0A000000000000","00000080","00006000","00000000"]}}
07:40:07.718 RSL: stat/tasmota_74E359/STATUS4 = {"StatusMEM":{"ProgramSize":647,"Free":356,"Heap":25,"ProgramFlashSize":1024,"FlashSize":4096,"FlashChipId":"16405E","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","020000CF","050013C0","C000F981","0000C004","00001000","00000000"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,40,45","Sensors":"1,2,3,4,5,6,22,45"}}
07:40:07.727 RSL: stat/tasmota_74E359/STATUS5 = {"StatusNET":{"Hostname":"tasmota_74E359-0857","IPAddress":"172.20.1.222","Gateway":"172.20.1.1","Subnetmask":"255.255.255.0","DNSServer":"172.20.1.1","Mac":"8C:AA:B5:74:E3:59","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
07:40:07.733 RSL: stat/tasmota_74E359/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_74E359","MqttUser":"DVES_USER","MqttCount":0,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
07:40:07.739 RSL: stat/tasmota_74E359/STATUS7 = {"StatusTIM":{"UTC":"2021-06-23T06:40:07","Local":"2021-06-23T07:40:07","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"04:47","Sunset":"20:57"}}
07:40:07.745 RSL: stat/tasmota_74E359/STATUS10 = {"StatusSNS":{"Time":"2021-06-23T07:40:07"}}
07:40:07.751 RSL: stat/tasmota_74E359/STATUS11 = {"StatusSTS":{"Time":"2021-06-23T07:40:07","Uptime":"0T00:13:31","UptimeSec":811,"Heap":25,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Wifi":{"AP":1,"SSId":"Andromeda","BSSId":"00:11:32:6C:33:E2","Channel":8,"RSSI":98,"Signal":-51,"LinkCount":1,"Downtime":"0T00:00:03"}}}

• [x] Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

09:04:13.940 MQT: stat/BELL/RESULT = {"WebLog":4}
09:04:13.025 CFG: Saved to flash at 3F9, Count 186, Bytes 4096
09:04:19.189 WIF: Checking connection...
09:04:25.695 CMD: tmsend test
09:04:25.696 SRC: WebConsole from 172.20.1.2
09:04:25.698 CMD: Group 0, Index 1, Command "TMSEND", Data "test"
09:04:25.700 TGM: sendMessage
09:04:27.098 MQT: stat/BELL/RESULT = {"TmSend":"Failed"}
09:04:40.636 WIF: Checking connection...

TO REPRODUCE

0. Make sure you're running a new Tasmota built with #define USE_TELEGRAM
1. set Telegram Bot Token in console with tmtoken <token>
2. set Telegram Chat Id in console with tmchatid <tmchatid>
3. set tmstate 1
4. Send a message with tmsend test

EXPECTED BEHAVIOUR

The test message should be sent to the bot and received in the TG mobile app

SCREENSHOTS

NA

ADDITIONAL CONTEXT

This issue started around 20-21 June without any changes in either the Tasmota build nor the settings.

Closing issue as it is fixed.

It works now, thank you!

And to think I almost got it yesterday ... I just missed the '\r'. I added the "Host: ..." line and terminated it with only a "\n" instead of "\r\n" :)

https://github.com/nightphobos/tasmota-am2320-i2c-driver - fixes & binary for 9.5.0

Custom made platform not needed anymore. Relevant only for ESP32-C3

Checklist:

• [X] The pull request is done against the latest development branch
• [X] Only relevant files were touched
• [X] Only one feature/fix was added per PR and the code change compiles without warnings
• [X] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [X] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [X] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

Custom made platform not needed anymore. Relevant only for ESP32-C3

Checklist:

• [X] The pull request is done against the latest development branch
• [X] Only relevant files were touched
• [X] Only one feature/fix was added per PR and the code change compiles without warnings
• [X] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [X] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [X] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

Checklist:

• [x] The pull request is done against the latest development branch
• [x] Only relevant files were touched
• [x] Only one feature/fix was added per PR and the code change compiles without warnings
• [x] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [x] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [x] I accept the CLA.

Hello, I can not receive the code of 433 to some it happened to him?

Yes I just spotted you had Tx and Rx on wrong GPIOs

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: dajrekt ***@***.***> Sent: Wednesday, June 23, 2021 10:28:34 PM To: arendst/Tasmota ***@***.***> Cc: pmknowles ***@***.***>; Mention ***@***.***> Subject: Re: [arendst/Tasmota] Any Sonoff device compatible with a clamp on current meter such as STC-013 (#3626)

It has started working! This is my config

[20210623_185927]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F78508173%2F123169939-d1bab800-d471-11eb-8d2d-1be3aebd70af.jpg&data=04|01||a3eeca3faa484099e10208d9368ddb96|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637600805163689569|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=n3I5mBrGy4k4EOJpDjDv%2F4HRFXZtf9eNCx8%2Fv72mGCs%3D&reserved=0

I also set the address of the modbus to 1 with this command in the console ModuleAddress 1

This is comparison with Sonoff Pow R2 [20210623_180718 (1)]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F78508173%2F123170152-16465380-d472-11eb-9724-4b2d83501d4b.jpg&data=04|01||a3eeca3faa484099e10208d9368ddb96|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637600805163689569|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9HJ8xuNeU5BNbU9s5U0YF1hpWuPGWKdS5rSqJucA0IE%3D&reserved=0

Now I need to build another two meters and call for electrician to mess with my fuse box :)

Thanks for your help!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farendst%2FTasmota%2Fissues%2F3626%23issuecomment-867171777&data=04|01||a3eeca3faa484099e10208d9368ddb96|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637600805163699522|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=EzOgMnSarANB%2FEYz5PyVd9LLz%2FrmBIfrsjNLUcmNk3A%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAI5KPMYL67MRAR7XL6K5QOTTUJGYFANCNFSM4FSBPY3Q&data=04|01||a3eeca3faa484099e10208d9368ddb96|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637600805163699522|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=i2VB3esGBaNh75HjuKuh35g%2FmbpAw3ERVGus3TFLyLc%3D&reserved=0.

It has started working! This is my config

I also set the address of the modbus to 1 with this command in the console ModuleAddress 1

This is comparison with Sonoff Pow R2

Now I need to build another two meters and call for electrician to mess with my fuse box :)

Thanks for your help!

Description:

Partition Manager v1.

Allows to resize the SPIFFS partition, or to change the global partitioning of Esp32. This means that you don't need to reflash with serial if you want to change the sizes of partitions.

How to use:

• upload partition.be or the pre-compiled partition.bec on the file system of Esp32
• in the Tasmota console type br import partition
• (or in the Berry console, type import partition)
• go the the "Consoles" page and click on "Partition Manager"

Note: this component is entirely developed in Berry code.

Note 2: added the following to webserver library:

• arg_name to enumerate web arguments and get their names
• redirect to send an HTTP redirect (code 302)

Checklist:

• [x] The pull request is done against the latest development branch
• [x] Only relevant files were touched
• [x] Only one feature/fix was added per PR and the code change compiles without warnings
• [ ] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [x] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [x] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

Description:

Partition Manager v1.

Allows to resize the SPIFFS partition, or to change the global partitioning of Esp32. This means that you don't need to reflash with serial if you want to change the sizes of partitions.

How to use:

• upload partition.be or the pre-compiled partition.bec on the file system of Esp32
• in the Tasmota console type br import partition
• (or in the Berry console, type import partition)
• go the the "Consoles" page and click on "Partition Manager"

Note: this component is entirely developed in Berry code.

Note 2: added the following to webserver library:

• arg_name to enumerate web arguments and get their names
• redirect to send an HTTP redirect (code 302)

Checklist:

• [x] The pull request is done against the latest development branch
• [x] Only relevant files were touched
• [x] Only one feature/fix was added per PR and the code change compiles without warnings
• [ ] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [x] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [x] I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

Checklist:

• [x] The pull request is done against the latest development branch
• [x] Only relevant files were touched
• [x] Only one feature/fix was added per PR and the code change compiles without warnings
• [x] The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• [x] The code change is tested and works with Tasmota core ESP32 V.1.0.7
• [x] I accept the CLA.

Please, could you be so kind on completing the troubleshooting template in order to have more information so as to properly help you?

Remember to read the Contributing Guideline and Policy. Thanks.

Support Information

See Docs for more information. See Chat for more user experience. See Code of Conduct

<!-- Thanks for reporting a problem for this project. READ THIS FIRST:

This issue template is meant to REPORT Tasmota software PROBLEMS ONLY

Please DO NOT OPEN AN ISSUE:

• If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Your problem might already be solved. The latest precompiled binaries of Tasmota can be downloaded from http://ota.tasmota.com/tasmota/
• If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team
• If your issue is a flashing issue, please address it to the Tasmota Support Chat
• If your issue is compilation problem, please address it to the Tasmota Support Chat
• If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue
• If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the FAQ and Troubleshooting

Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.

DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed. -->

PROBLEM DESCRIPTION

A clear and concise description of what the problem is. I'm seeing below messages repeatedly on the Tasmota console.

21:40:09.190 CMD: 21:40:09.130 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
21:40:09.197 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
21:40:09.211 CMD: Serial buffer overrun
21:40:09.221 CMD: Serial buffer overrun
21:40:09.231 CMD: Serial buffer overrun
21:40:09.243 CMD: Serial buffer overrun

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [X] Read the Contributing Guide and Policy and the Code of Conduct
• [X] Searched the problem in issues
• [X] Searched the problem in discussions
• [X] Searched the problem in the docs
• [X] Searched the problem in the chat
• [X] Device used (e.g., Sonoff Basic): https://templates.blakadder.com/WP40.html
• [X] Tasmota binary firmware version number used: 9.4.0.6
  • [X] Pre-compiled
  • [ ] Self-compiled
• [ ] Flashing tools used: hard-wired
• [ ] Provide the output of command: Backlog Template; Module; GPIO 255:

  Configuration output here:
21:43:00.112 CMD: Backlog Template; Module; GPIO 255
21:43:01.839 CMD: Serial buffer overrun
21:43:01.851 CMD: 21:43:01.796 CMD: Serial buffer overrun

• [ ] If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

• [x] Provide the output of this command: Status 0:

  STATUS 0 output here:
21:43:53.195 CMD: status 0
21:43:53.204 MQT: stat/tasmota_867FC6/STATUS = {"Status":{"Module":0,"DeviceName":"Plug 3","FriendlyName":["Plug 3-1","Plug 3-2","Plug 3-3","USB Right","USB Left"],"Topic":"tasmota_867FC6","ButtonTopic":"0","Power":25,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
21:43:53.243 MQT: stat/tasmota_867FC6/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/tasmota.bin","RestartReason":"Software/System restart","Uptime":"0T00:13:47","StartupUTC":"2021-06-21T20:30:06","Sleep":50,"CfgHolder":4617,"BootCount":45,"BCResetTime":"2021-02-08T20:03:59","SaveCount":709,"SaveAddress":"F5000"}}
21:43:53.276 MQT: stat/tasmota_867FC6/STATUS2 = {"StatusFWR":{"Version":"9.4.0.6(tasmota)","BuildDateTime":"2021-06-16T06:48:06","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"394/699"}}
21:43:53.295 MQT: stat/tasmota_867FC6/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["xxxxxx",""],"TelePeriod":300,"Resolution":"55A180C0","SetOption":["00008009","2805C8000100060000005A0A000000000000","00000080","00006000","00000000"]}}
21:43:53.329 MQT: stat/tasmota_867FC6/STATUS4 = {"StatusMEM":{"ProgramSize":607,"Free":396,"Heap":15,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"1440C8","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8FDAC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45","Sensors":"1,2,3,4,5,6"}}
21:43:53.365 MQT: stat/tasmota_867FC6/STATUS5 = {"StatusNET":{"Hostname":"tasmota_867FC6-8134","IPAddress":"192.168.1.X","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.X","Mac":"68:C6:3A:86:7F:C6","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
21:43:53.387 MQT: stat/tasmota_867FC6/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.199","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_867FC6","MqttUser":"XXXXX","MqttCount":14,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
21:43:53.412 MQT: stat/tasmota_867FC6/STATUS7 = {"StatusTIM":{"UTC":"2021-06-21T20:43:53","Local":"2021-06-21T21:43:53","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"04:46","Sunset":"20:57"}}
21:43:53.431 MQT: stat/tasmota_867FC6/STATUS10 = {"StatusSNS":{"Time":"2021-06-21T21:43:53"}}
21:43:53.440 MQT: stat/tasmota_867FC6/STATUS11 = {"StatusSTS":{"Time":"2021-06-21T21:43:53","Uptime":"0T00:13:47","UptimeSec":827,"Heap":15,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":39,"MqttCount":14,"POWER1":"ON","POWER2":"OFF","POWER3":"OFF","POWER4":"ON","POWER5":"ON","Wifi":{"AP":1,"SSId":"xxxxxxx","BSSId":"54:A0:50:59:91:28","Channel":2,"Mode":"11n","RSSI":44,"Signal":-78,"LinkCount":1,"Downtime":"0T00:00:03"}}}
21:43:55.160 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}

• [x] Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:
19:04:00.668 SRC: Serial
19:04:00.671 CMD: Grp 0, Cmnd '', Idx 19, Len 66, Data ':04:00.609 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}'
19:04:00.675 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.689 CMD: Serial buffer overrun
19:04:00.699 CMD: Serial buffer overrun
19:04:00.703 UDP: Packet (101)
19:04:00.707 WMO: WeMo Type 2, Response sent to 192.168.1.200:39168
19:04:00.711 WMO: WeMo Type 2, Response sent to xxx.xxx.xxx.xxx:39168
19:04:00.714 WMO: WeMo Type 2, Response sent to xxx.xxx.xxx.xxx:39168
19:04:00.717 WMO: WeMo Type 2, Response sent to xxx.xxx.xxx.xxx:39168
19:04:00.721 WMO: WeMo Type 2, Response sent to xxx.xxx.xxx.xxx:39168
19:04:00.723 UDP: Packet (101)
19:04:00.733 CMD: Serial buffer overrun
19:04:00.745 CMD: Serial buffer overrun
19:04:00.758 CMD: 19:04:00.675 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.760 SRC: Serial
19:04:00.762 CMD: Grp 0, Cmnd '', Idx 19, Len 66, Data ':04:00.675 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}'
19:04:00.767 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.781 CMD: Serial buffer overrun
19:04:00.790 CMD: Serial buffer overrun
19:04:00.801 CMD: Serial buffer overrun
19:04:00.813 CMD: Serial buffer overrun
19:04:00.826 CMD: 19:04:00.767 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.828 SRC: Serial
19:04:00.830 CMD: Grp 0, Cmnd '', Idx 19, Len 66, Data ':04:00.767 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}'
19:04:00.835 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.848 CMD: Serial buffer overrun
19:04:00.858 CMD: Serial buffer overrun
19:04:00.868 CMD: Serial buffer overrun
19:04:00.881 CMD: Serial buffer overrun
19:04:00.893 CMD: 19:04:00.835 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.895 SRC: Serial
19:04:00.898 CMD: Grp 0, Cmnd '', Idx 19, Len 66, Data ':04:00.835 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}'
19:04:00.903 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.915 CMD: Serial buffer overrun
19:04:00.925 CMD: Serial buffer overrun
19:04:00.935 CMD: Serial buffer overrun
19:04:00.948 CMD: Serial buffer overrun
19:04:00.963 CMD: 19:04:00.903 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.965 SRC: Serial
19:04:00.968 CMD: Grp 0, Cmnd '', Idx 19, Len 66, Data ':04:00.903 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}'
19:04:00.973 MQT: stat/tasmota_867FC6/RESULT = {"Command":"Unknown"}
19:04:00.986 CMD: Serial buffer overrun
19:04:00.996 CMD: Serial buffer overrun
19:04:01.007 CMD: Serial buffer overrun
19:04:01.022 CMD: Serial buffer overrun

TO REPRODUCE

Open console

EXPECTED BEHAVIOUR

I didn't expect to see any error messages in the console.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

I'm changing the configuration to {"NAME":"WP40","GPIO":[33,0,0,0,56,0,0,0,21,17,22,23,32],"FLAG":0,"BASE":18} as per device documentation on https://templates.blakadder.com/WP40.html. However, it always goes back to {"NAME":"WP40","GPIO":[260,0,0,0,320,0,0,0,224,32,225,226,259,0],"FLAG":0,"BASE":18} which is weird I guess?... I don't know much about this firmware but it looks strange that config changes on its own... Thank you for your help.

(Please, remember to close the issue when the problem has been addressed)

I can confirm the issue is solved in 9.5.0.1. The extended Rule display (now without truncation) makes it possible to verify the integrity of the rule as received and stored in Tasmota. The whole rule uploading process is now more robust. Thank you!!

ps. one small glitch is still there: the http response payload for the Rulex commands AFTER the ruleset begins compressing comes preceded by surplus data from previous Rulex commands. As far as I can tell this has no impact in the process and can be easily circumvented by skiping any data before the expected payload => { "Rule...

Thank you very much. I made the changes you recommended, it stopped throwing those messages. I have to say I'm really impressed with Tasmota and thank you very much for your help!!!. This kind of dedication makes this project very successful. When I find the time I will inspect the hardware to find if I caused a short-circuit between TX and RX. I will report back on that later. Once again, thank you for your time and help.