Shelly 1PM suddenly extremly slow with Tasmota

[AleXSR700]

Hello again,
slowly but surely I am starting to get my Shellies switched over to Tasmota.

However, I have one Shelly 1PM (connected to the anode of a boiler) which is extremely slow. WebUI loads very slowly, sometimes not at all for a few seconds. Everything is slow and sluggish. All other devices seem to be fine.

Is there a way of checking what is causing this slow behavior?

Thank you all
Alex

[Jason2866]

Please post log output of status 0

[AleXSR700]

23:03:02.572 MQT: stat/tasmota_E588CD/STATUS = {"Status":{"Module":0,"DeviceName":"Boiler_3","FriendlyName":["Boiler_3"],"Topic":"tasmota_E588CD","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":0,"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}}
23:03:02.577 MQT: stat/tasmota_E588CD/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:17:23","StartupUTC":"2022-09-09T20:45:39","Sleep":50,"CfgHolder":4617,"BootCount":9,"BCResetTime":"2022-09-09T12:55:33","SaveCount":19,"SaveAddress":"F5000"}}
23:03:02.582 MQT: stat/tasmota_E588CD/STATUS2 = {"StatusFWR":{"Version":"12.1.1(tasmota)","BuildDateTime":"2022-08-25T11:33:55","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"391/699"}}
23:03:02.586 MQT: stat/tasmota_E588CD/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["temperatureHA24",""],"TelePeriod":600,"Resolution":"558980C0","SetOption":["0020800B","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
23:03:02.598 MQT: stat/tasmota_E588CD/STATUS4 = {"StatusMEM":{"ProgramSize":624,"Free":376,"Heap":23,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540EF","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8F9AC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","54000020","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,45,62","Sensors":"1,2,3,4,5,6"}}
23:03:02.606 MQT: stat/tasmota_E588CD/STATUS5 = {"StatusNET":{"Hostname":"tasmota-E588CD-2253","IPAddress":"192.168.0.213","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.0.1","DNSServer2":"0.0.0.0","Mac":"3C:61:05:E5:88:CD","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
23:03:02.611 MQT: stat/tasmota_E588CD/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.0.2","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_E588CD","MqttUser":"mus","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
23:03:02.617 MQT: stat/tasmota_E588CD/STATUS7 = {"StatusTIM":{"UTC":"2022-09-09T21:03:02","Local":"2022-09-09T23:03:02","StartDST":"2022-03-27T02:00:00","EndDST":"2022-10-30T03:00:00","Timezone":99,"Sunrise":"07:18","Sunset":"20:16"}}
23:03:02.620 MQT: stat/tasmota_E588CD/STATUS9 = {"StatusPTH":{"PowerDelta":[103,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
23:03:02.628 MQT: stat/tasmota_E588CD/STATUS10 = {"StatusSNS":{"Time":"2022-09-09T23:03:02","Switch1":"OFF","ANALOG":{"Temperature":47.3},"ENERGY":{"TotalStartTime":"2022-09-09T12:55:33","Total":0.750,"Yesterday":0.000,"Today":0.750,"Power":2.0},"TempUnit":"C"}}
23:03:02.635 MQT: stat/tasmota_E588CD/STATUS11 = {"StatusSTS":{"Time":"2022-09-09T23:03:02","Uptime":"0T00:17:23","UptimeSec":1043,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":7266,"MqttCount":1,"POWER":"ON","Wifi":{"AP":1,"SSId":"temperatureHA24","BSSId":"06:31:92:E7:DC:7E","Channel":6,"Mode":"11n","RSSI":92,"Signal":-54,"LinkCount":1,"Downtime":"0T00:00:04"}}}```

[AleXSR700]

Was this helpful @Jason2866 ?

[Jason2866]

This is not normal Dynamic","Sleep":50,"LoadAvg":7266," Try sleep 0 if device gets more responsive.

[arendst]

Pls measure the voltage on the Shelly with power off and with power on. This can be done on the outside of the device. See below picture:

[AleXSR700]

You mean when connected to mains measure voltage between N and L and between N and O?
Or connected to serial measure N/L and N/O?

[arendst]

No, when connected to mains measure voltage between GND and 3.3V. To see if it lowers due to extra load of the relay powered on.

[AleXSR700]

Nothing unusual:
Power off: 3.3 V
Power on: 3.3 V
Power off or on but SO47 timer running : 0 V

So all as expected

[arendst]

Pls try again starting with an empty template as possible. So add only the relay and see what happens. If it's fine, add the analog input and chk again.

[edegrave]

I have the same problem with 2 Shelly 1PMs. Both are flashed to the latest firmware 12.1.1 but the problem persists. Selecting menu items takes minutes to load and sometimes fails. The output of status 0:

11:59:17.560 MQT: stat/shelly_74DA65/STATUS = {"Status":{"Module":0,"DeviceName":"Shelly 1PM 01","FriendlyName":["Shelly 1PM 01"],"Topic":"shelly_74DA65","ButtonTopic":"0","Power":1,"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}} 11:59:17.568 MQT: stat/shelly_74DA65/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Blocked Loop","Uptime":"1T10:16:26","StartupUTC":"2022-09-15T00:42:51","Sleep":50,"CfgHolder":4617,"BootCount":380,"BCResetTime":"2021-09-30T19:20:17","SaveCount":790,"SaveAddress":"F4000"}} 11:59:17.576 MQT: stat/shelly_74DA65/STATUS2 = {"StatusFWR":{"Version":"12.1.1(tasmota)","BuildDateTime":"2022-08-25T11:33:55","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"449/699"}} 11:59:17.584 MQT: stat/shelly_74DA65/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["vKumo-IoT_2G",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A002800000000","00000080","00006000","00004000","00000000"]}} 11:59:17.597 MQT: stat/shelly_74DA65/STATUS4 = {"StatusMEM":{"ProgramSize":624,"Free":376,"Heap":24,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"15701C","FlashFrequency":40,"FlashMode":3,"Features":["00000809","8F9AC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","54000020","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,45,62","Sensors":"1,2,3,4,5,6"}} 11:59:17.606 MQT: stat/shelly_74DA65/STATUS5 = {"StatusNET":{"Hostname":"shelly-74DA65-6757","IPAddress":"192.168.6.61","Gateway":"192.168.6.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.88.8","DNSServer2":"192.168.88.124","Mac":"8C:AA:B5:74:DA:65","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}} 11:59:17.612 MQT: stat/shelly_74DA65/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.6.90","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_74DA65","MqttUser":"homeassistant","MqttCount":331,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}} 11:59:17.621 MQT: stat/shelly_74DA65/STATUS7 = {"StatusTIM":{"UTC":"2022-09-16T10:59:17","Local":"2022-09-16T11:59:17","StartDST":"2022-03-27T02:00:00","EndDST":"2022-10-30T03:00:00","Timezone":"+01:00","Sunrise":"06:28","Sunset":"19:01"}} 11:59:17.628 MQT: stat/shelly_74DA65/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}} 11:59:17.639 MQT: stat/shelly_74DA65/STATUS10 = {"StatusSNS":{"Time":"2022-09-16T11:59:17","Switch1":"OFF","ANALOG":{"Temperature":64.6},"ENERGY":{"TotalStartTime":"2021-09-30T19:20:17","Total":224.973,"Yesterday":1.144,"Today":1.383,"Power": 4},"TempUnit":"C"}} 11:59:17.648 MQT: stat/shelly_74DA65/STATUS11 = {"StatusSTS":{"Time":"2022-09-16T11:59:17","Uptime":"1T10:16:26","UptimeSec":123386,"Heap":24,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":16429,"MqttCount":331,"POWER":"ON","Wifi":{"AP":1,"SSId":"vKumo-IoT_2G","BSSId":"6A:D7:9A:3D:6A:5F","Channel":6,"Mode":"11n","RSSI":58,"Signal":-71,"LinkCount":1,"Downtime":"0T00:00:03"}}} 11:59:17.663 MQT: stat/shelly_74DA65/STATUS12 = {"StatusSTK":{"Exception":0,"Reason":"Blocked Loop","EPC":["00000000","00000000","00000000"],"EXCVADDR":"00000000","DEPC":"00000000","CallChain":["40201b5c","40250a2e","40275f90","4025182a","40275f9d","40275fe2","4024dad4","40000f49","40000f49","40000f49","40000e19","40105aa9","40105aaf","4010000d","4026ea18","4026e9c9","40100a7c","401016f5","40254839","401016ac","4000050c","40253d29","401016f5","4000050c","40253c0b","401016f5","4000050c","402542ba","401016f5","401016ac","4000050c"]}}

The other 1PM wontt outlput anything anymore. Should I return to Shelly firmware or is there something that can ben done?

[AleXSR700]

What kind of load is yours?

I now heard that sometimes RC snubbers are needed. But I think this should then also be noticable in stock firmware.
Or maybe this problem is somehow emphasized in Tasmota (if that were the cause, which I cannot test at the moment)?

[edegrave]

One is behind a tumble dryer the other behind a washing machine. So most of the day both have no load at all. Doesn't seem to matter for responsiveness of the web ui.

[AleXSR700]

Hmmm, no, those seem like normal loads to me. I have one behind my washing mashine and my dish washer and both are fine. Have you contacted Shelly support? Without mentioning Tasmota....

[edegrave]

I'll try going back to Shelly firmware first. Any idea where to get that? Seems harder than I thought.

[AleXSR700]

Did you use the OTA approach from github? If yes, there is the same but tasmota-to-mgos.
That worked for me. Just make sure to use the correct device's firmware.

[nima-1102]

I have the same problem, strangely enough only with one device out of 10. I've tried several times to fix the problem with 'Reset 5' & power-cycle, I haven't completely re-flashed via cable yet because the device is in use.

Use the Version 'Tasmota v12.4.0' & Template: {"NAME":"Shelly 1PM","GPIO":[56,0,0,0,82,134,0,0,0,0,0,21,0],"FLAG":2, "BASE":18}

If I remove the Relay 1 (GPIO15) & Switch_n 1 (GPIO4) from the template, everything runs great, as soon as I add the relay, LoadAvg goes to 12655+ and I can only access the web interface by trying and waiting several times.

Status 0 without Relay:

00:39:27.031 CMD: status 0
00:39:27.039 MQT: stat/tasmota_72B9B1/STATUS = {"Status":{"Module":0,"DeviceName":"Shelly-1PM-9","FriendlyName":["Shelly-1PM-9"],"Topic":"tasmota_72B9B1","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
00:39:27.077 MQT: stat/tasmota_72B9B1/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:08:04","StartupUTC":"2023-03-03T23:31:23","Sleep":50,"CfgHolder":4617,"BootCount":5,"BCResetTime":"2022-12-07T19:37:08","SaveCount":15,"SaveAddress":"FB000"}}
00:39:27.111 MQT: stat/tasmota_72B9B1/STATUS2 = {"StatusFWR":{"Version":"12.4.0(tasmota)","BuildDateTime":"2023-02-24T15:32:38","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"410/699"}}
00:39:27.132 MQT: stat/tasmota_72B9B1/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["FRITZ!Box 7430 WI",""],"TelePeriod":10,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
00:39:27.166 MQT: stat/tasmota_72B9B1/STATUS4 = {"StatusMEM":{"ProgramSize":632,"Free":368,"Heap":22,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"15400B","FlashFrequency":40,"FlashMode":"DOUT","Features":["00000809","8F9AC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","54000020","00000080"],"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,62","Sensors":"1,2,3,4,5,6"}}
00:39:27.202 MQT: stat/tasmota_72B9B1/STATUS5 = {"StatusNET":{"Hostname":"tasmota-72B9B1-6577","IPAddress":"192.168.178.115","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.230","DNSServer2":"0.0.0.0","Mac":"xxxxxxxxxxxxx","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
00:39:27.228 MQT: stat/tasmota_72B9B1/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.178.130","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_72B9B1","MqttUser":"mqtt","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
00:39:27.252 MQT: stat/tasmota_72B9B1/STATUS7 = {"StatusTIM":{"UTC":"2023-03-03T23:39:27","Local":"2023-03-04T00:39:27","StartDST":"2023-03-26T02:00:00","EndDST":"2023-10-29T03:00:00","Timezone":"+01:00","Sunrise":"07:26","Sunset":"18:37"}}
00:39:27.272 MQT: stat/tasmota_72B9B1/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
00:39:27.290 MQT: stat/tasmota_72B9B1/STATUS10 = {"StatusSNS":{"Time":"2023-03-04T00:39:27","ANALOG":{"Temperature":45.5},"ENERGY":{"TotalStartTime":"2022-12-07T19:37:08","Total":0.000,"Yesterday":0.000,"Today":0.000,"Power":0},"TempUnit":"C"}}
00:39:27.309 MQT: stat/tasmota_72B9B1/STATUS11 = {"StatusSTS":{"Time":"2023-03-04T00:39:27","Uptime":"0T00:08:04","UptimeSec":484,"Heap":22,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":24,"MqttCount":1,"Wifi":{"AP":1,"SSId":"xxxxxxxxxxxxxxxx","BSSId":"xxxxxxxxxxxxxxxx","Channel":1,"Mode":"11n","RSSI":46,"Signal":-77,"LinkCount":1,"Downtime":"0T00:00:05"}}}

Template:

00:54:38.262 MQT: stat/tasmota_72B9B1/RESULT = {"NAME":"Shelly 1PM","GPIO":[320,0,0,0,0,2720,0,0,0,0,0,0,0,4736],"FLAG":0,"BASE":18}

--

Status 0 with Relay:

00:45:54.774 CMD: status 0
00:45:54.782 MQT: stat/tasmota_72B9B1/STATUS = {"Status":{"Module":0,"DeviceName":"Shelly-1PM-9","FriendlyName":["Shelly-1PM-9"],"Topic":"tasmota_72B9B1","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
00:45:54.820 MQT: stat/tasmota_72B9B1/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:04:38","StartupUTC":"2023-03-03T23:41:16","Sleep":50,"CfgHolder":4617,"BootCount":6,"BCResetTime":"2022-12-07T19:37:08","SaveCount":18,"SaveAddress":"FA000"}}
00:45:54.856 MQT: stat/tasmota_72B9B1/STATUS2 = {"StatusFWR":{"Version":"12.4.0(tasmota)","BuildDateTime":"2023-02-24T15:32:38","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"410/699"}}
00:45:54.875 MQT: stat/tasmota_72B9B1/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["FRITZ!Box 7430 WI",""],"TelePeriod":10,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
00:45:54.910 MQT: stat/tasmota_72B9B1/STATUS4 = {"StatusMEM":{"ProgramSize":632,"Free":368,"Heap":22,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"15400B","FlashFrequency":40,"FlashMode":"DOUT","Features":["00000809","8F9AC787","04368001","000000CF","010013C0","C000F981","00004004","00001000","54000020","00000080"],"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,62","Sensors":"1,2,3,4,5,6"}}
00:45:54.946 MQT: stat/tasmota_72B9B1/STATUS5 = {"StatusNET":{"Hostname":"tasmota-72B9B1-6577","IPAddress":"192.168.178.115","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.230","DNSServer2":"0.0.0.0","Mac":"xxxxxxxxxxxxxxx","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
00:45:54.972 MQT: stat/tasmota_72B9B1/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.178.130","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_72B9B1","MqttUser":"mqtt","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
00:45:54.996 MQT: stat/tasmota_72B9B1/STATUS7 = {"StatusTIM":{"UTC":"2023-03-03T23:45:54","Local":"2023-03-04T00:45:54","StartDST":"2023-03-26T02:00:00","EndDST":"2023-10-29T03:00:00","Timezone":"+01:00","Sunrise":"07:26","Sunset":"18:37"}}
00:45:55.001 MQT: stat/tasmota_72B9B1/STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
00:45:55.021 MQT: stat/tasmota_72B9B1/STATUS10 = {"StatusSNS":{"Time":"2023-03-04T00:45:55","Switch1":"OFF","ANALOG":{"Temperature":46.4},"ENERGY":{"TotalStartTime":"2022-12-07T19:37:08","Total":0.000,"Yesterday":0.000,"Today":0.000,"Power":0},"TempUnit":"C"}}
00:45:55.043 MQT: stat/tasmota_72B9B1/STATUS11 = {"StatusSTS":{"Time":"2023-03-04T00:45:55","Uptime":"0T00:04:39","UptimeSec":279,"Heap":22,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":12655,"MqttCount":1,"POWER":"ON","Wifi":{"AP":1,"SSId":"xxxxxxxxxxxxxxxx","BSSId":"xxxxxxxxxxxxxxxx","Channel":1,"Mode":"11n","RSSI":50,"Signal":-75,"LinkCount":1,"Downtime":"0T00:00:03"}}}

Template:

00:51:52.672 MQT: stat/tasmota_72B9B1/RESULT = {"NAME":"Shelly 1PM","GPIO":[320,0,0,0,192,2720,0,0,0,0,0,224,0,4736],"FLAG":0,"BASE":18}

[AleXSR700]

I had tried reflashing via cable including erasing and it changed nothing for me.

[AleXSR700]

Any news from your side? Did you try measuring the voltages as described by arendst above?

[nima-1102]

Sorry for the late reply, I only found time today to test.

[nima-1102]

So I flashed several times via Serial (Tasmotizer) with option "Self-resettung device" & "Erase before flashing" activated.
With every version, I completely deleted the device and only changed the template & Wifi information after the flash.

Here are the results:

Tasmota 8.5.1 -- works -- LoadAvg: 20-30
Tasmota 9.1.0 -- works -- LoadAvg: 20-30

Tasmota 10.0.0 -- works -- LoadAvg: 60-240

Tasmota 10.1.0 -- Problem -- LoadAvg: 10000++
Tasmota 11.0.0 -- Problem -- LoadAvg: 10000++
Tasmota 12.4.0 -- Problem -- LoadAvg: 10000++
Tasmota 12.4.0.4 -- Problem -- LoadAvg: 10000++

As you can clearly see, the problem started very minimally at 10.0.0 with a higher LoadAvg (still ok), and then the problem has been constant since 10.1.0.

[arendst]

Give latest dev (v12.4.0.4) a try too.

[nima-1102]

Just tested, unfortunately the same problem.
The problem only happens when the device runs on AC power, otherwise I could provide a serial log.

So Serial Power -> Template = Works
Then AC power -> Works until I turn on the switch, then LoadAVG straight up -> Webgui just loads
Back to Serial Power = Works

So there seems to be a problem with the relay in the software.

[alistercole]

I have run into the same problem with 1 of my shelly 1PM devices, with an unresponsive web interface, that takes many attempts to load, like minutes!

Flashing back to Tasmota 10.0.0 resolves the slowness of the UI.

[AleXSR700]

If the problem starts with the upgrade from version 9.1, could it be relates to the --- Major change in internal GPIO function representation --- ?

[ivohulsman]

I can confirm this issue still persists on v13.1.8 on a Shelly 1PM. Downgrading back to v10.0.0 makes the device very smooth again.

[Bodengriller]

Similar phenomenon here
one of two shellys works perfectly even with v12.4
The other only works up to v10.0, after that it does nothing at all with 230V power.

So it seems to be a combination of software and hardware. But which one?
As it continues to work reliably with v10.0, I think the fault lies more in the software >v10.0

Has anyone here made any progress?

[Bodengriller]

Why has the LoadAvg increased so much since V10.1 and how is this related to the Shelly's power supply?
Are there proven ways to optimize the hardware (which ones)?
Why do you still measure 3.3V if the power supply is too borderline -> doesn't the voltage have to collapse?

[Jason2866]

Have you measured the 3.3V with an oscilloscope? A multimeter will not show small drops.
LoadAvg is not an indicator for bugs

[Bodengriller]

No, I haven't yet. I did play around with my DSO138 China junk today, but I didn't notice any significant voltage drops here either.
I have also tried a few other things.
V13.3 lite also works with 230V - but I'm missing the BL0937 driver for power measurement. (logical -> lite!)

whatever... After a lot of thinking back and forth, I came to the question of what a newer version of Tasmota would actually do for me or what I could expect from it.

The first rule of upgrading: If it ain't broke, don't fix it!
In other words, ensure that there is a good reason to mess with a working installation (e.g., a need to use a new feature or address a found problem fixed in the current version).

There is probably a reason why this is denounced big and bold on the helppage

There have been no notable innovations since the V10...., at least none that would be of interest to me.
So basically everything from v9.2 (because of Homeassistant) should be OK for my devices. Anything above that obviously only consumes performance unnecessarily due to the majority of new drivers and possibly unused functions.
There is probably nothing to consider in terms of safety or similar.
So my inner Monk is probably only bothered by the stupid number of the version

However, I still wonder why the number of (unused) drivers consumes power and is not only loaded when they are actually used.
That doesn't quite make sense to me yet.

[Jason2866]

New drivers do generate only load when used. But there are not just drivers, there are management functions and new features added and active with every newer version.
A borderline power supply is at some point at its edge.
So yes the disclaimer is there for a reason. Every major change in release number has major changes under the hood.

[AleXSR700]

Newer versions do offer nice stuff like support of special drivers or other new features. So the problem does remain.

Unfortunately I only have an oscilloscope at work and not at home. So I cannot test properly.

Strange thing is that some work and some do not. And the loads are far from any limits. It has been a while but from memory the problem arises even with the smallest possible loads connected. So no way the device is at any real limit.

[Wintespe]

A borderline power supply is at some point at its edge.

In these cases, the power supply is not borderline but Tasmota is no longer compatible with the design because it does not meet the hardware specification.

[AleXSR700]

But whose specification? After all, the device seems to work with stock firmware and old tasmota versions. So the hardware does seem to "work".
And I am not sure if Shelly would agree that the device is not in accordance with their specs.

[AleXSR700]

But whose specification? After all, the device seems to work with stock firmware and old tasmota versions. So the hardware does seem to "work".
And I am not sure if Shelly would agree that the device is not in accordance with their specs.

[Jason2866]

If power supply is the reason, most symptoms do assume this, the device does not follow hardware design specs from espressif.
In this case the device is not compatible to any other firmware than Shelly. Clearly no Tasmota problem.
Tasmota will not support crappy vendor design choices.

[Bodengriller]

I agree that everything looks like the voltage is dropping at startup.
But what makes me a bit suspicious is that the Shelly even works with the latest V13.3 if you supply it with 3.3V via an FTDI, which doesn't even have enough power to energize the relay
My gut feeling tells me that this is somehow related to the fact that the Shelly developers had the funny idea of connecting the GPIO-Pins to AC-Power
Again, everything speaks against it, as some Shellys work and some don't.
Meanwhile, the real reason for this phenomenon interests me more than having the latest Tasmota version on this shelly :D

[AleXSR700]

If power supply is the reason, most symptoms do assume this, the device does not follow hardware design specs from espressif.
In this case the device is not compatible to any other firmware than Shelly. Clearly no Tasmota problem.
Tasmota will not support crappy vendor design choices.

But would that not affect all devices then? So all Shelly 1PM? Because the design is unchanged and at least mine are from the same batch, so from the same batch, 3 work fine and one does not.

[Wintespe]

Tasmota will not support crappy vendor design choices.

A somewhat unconventional view.

When designing a system, the hardware and software are harmonised. This ensures a cost-effective and functional design. As a developer, I will certainly not pay attention to external (open source) software in the design.

[Wintespe]

If I understand correctly, the CPU is utilised more if a featrure is added to Tasmota even if it is not used. Wouldn't it make sense to activate this feature only when needed?

Of course it is always possible, as I do, to adapt the firmware and then compile it myself.

[sfromis]

In general, features are not burning extra CPU by being present, but initialization has grown, for some features, and upgrades to things like Arduino-Core may also change how much is needed.

Old degraded devices are a known risk for croaking, also without newer Tasmota versions. More generally, my point was not to suggest that Tasmota is "doing too much", but instead that a senescent device just does not have the power it started with. Thus any trimming of power usage might allow unreliable operation for a bit longer.

[AleXSR700]

Any way of finding the culprit?
If the primary candidate is wifi, then maybe there is a way of debugging the wifi access?

[sfromis]

No, the primary candidate is senescent devices with degraded hardware. Typically capacitors.

[AleXSR700]

I meant the software culprit. If the hardware works fine with stock and less feature rich tasmota, then some new feature is causing the additional load which pushes the power supply over the edge.
If so, disabling the cause could solve the problem.

[Wintespe]

Just try to convince a design manager to increase the price of a product if the entire design is within the specified quality standard and tolerance range. Good luck.

[Jason2866]

Didn't say that. Just saying bad design and Tasmota will not support this.

[arendst]

As words are not enough and picture tells a thousands words....

[sfromis]

Repair or replace the hardware. Software cannot do magic to invigorate senescent hardware.

[Bodengriller]

I replaced all three capacitors on the off chance. No difference.
Then I replaced the 100µF capacitor of the secondary power supply with a 220µF electrolytic capacitor. That made no difference.
A short test with 470µF in parallel to the 220F also made no difference.

The Shelly does not boot with 230V, but with 3.3V without any problems

[Wintespe]

Jason2866
With increasing Tasmota version numbers, features increased. So newer Tasmota versions do need a bit more power than older ones. That's all.

sfromis
In general, features are not burning extra CPU by being present, but initialization has grown, for some features, and upgrades to things like Arduino-Core may also change how much is needed.

Do I have to understand that? What is right?

[Jason2866]

Both. Features are added. Features needs management. This adds load.

[sfromis]

Both are right.

but initialization has grown, for some features

aligns perfectly with

With increasing Tasmota version numbers, features increased

This is not general for most features, but a few features does affect what happens at boot time.