search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
21.96k stars 4.77k forks source link

Shelly 2.5 gets significantly hotter since 8.2.0.1 #7991

Closed kugelkopf123 closed 3 years ago

kugelkopf123 commented 4 years ago

PROBLEM DESCRIPTION

A clear and concise description of what the problem is. With the current version from the Dev Branch my Shelly2.5 is obviously much warmer than with the version from 15.03.2020.

REQUESTED INFORMATION

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

03:53:22 MQT: stat/Shelly25_5/RESULT = {"NAME":"Shelly 2.5 (bu","GPIO":[56,0,19,0,21,127,0,0,6,126,5,22,156],"FLAG":2,"BASE":18} 03:53:22 MQT: stat/Shelly25_5/RESULT = {"Module":{"0":"Shelly 2.5 (bu"}} 03:53:23 MQT: stat/Shelly25_5/RESULT = {"GPIO0":{"56":"Led1i"},"GPIO1":{"0":"None"},"GPIO2":{"19":"Button3"},"GPIO3":{"0":"None"},"GPIO4":{"21":"Relay1"},"GPIO5":{"127":"Button2in"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"6":"I2C SDA"},"GPIO13":{"126":"Button1in"},"GPIO14":{"5":"I2C SCL"},"GPIO15":{"22":"Relay2"},"GPIO16":{"156":"ADE7953 IRQ"}}

Shelly with Version 8.2.0.1:

04:12:29 MQT: stat/Shelly25_4/RESULT = {"NAME":"Shelly 2.5 (bu","GPIO":[56,0,19,0,21,127,0,0,6,126,5,22,156],"FLAG":2,"BASE":18} 04:12:30 MQT: stat/Shelly25_4/RESULT = {"Module":{"0":"Shelly 2.5 (bu"}} 04:12:30 MQT: stat/Shelly25_4/RESULT = {"GPIO0":{"56":"Led1i"},"GPIO1":{"0":"None"},"GPIO2":{"19":"Button3"},"GPIO3":{"0":"None"},"GPIO4":{"21":"Relay1"},"GPIO5":{"127":"Button2in"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"6":"I2C SDA"},"GPIO13":{"126":"Button1in"},"GPIO14":{"5":"I2C SCL"},"GPIO15":{"22":"Relay2"},"GPIO16":{"156":"ADE7953 IRQ"}}

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

Rules output here: Shelly with Version 8.1.0.11: :53:49 MQT: stat/Shelly25_5/RESULT = {"Rule1":"OFF","Once":"OFF","StopOnError":"OFF","Free":511,"Rules":""} 03:53:49 MQT: stat/Shelly25_5/RESULT = {"Rule2":"ON","Once":"OFF","StopOnError":"OFF","Free":370,"Rules":"on SHUTTER1#Position do backlog publish stat/%topic%/RESULT {"ShutterPosition1":%value%}; publish cmnd/%topic%/ShutterPosition1 %value% endon"} 03:53:49 MQT: stat/Shelly25_5/RESULT = {"Rule3":"OFF","Once":"OFF","StopOnError":"OFF","Free":511,"Rules":""}

Shelly with Version 8.2.0.1: 04:13:57 MQT: stat/Shelly25_4/RESULT = {"Rule1":"OFF","Once":"OFF","StopOnError":"OFF","Free":511,"Rules":""} 04:13:57 MQT: stat/Shelly25_4/RESULT = {"Rule2":"ON","Once":"OFF","StopOnError":"OFF","Free":370,"Rules":"on SHUTTER1#Position do backlog publish stat/%topic%/RESULT {"ShutterPosition1":%value%}; publish cmnd/%topic%/ShutterPosition1 %value% endon"} 04:13:57 MQT: stat/Shelly25_4/RESULT = {"Rule3":"OFF","Once":"OFF","StopOnError":"OFF","Free":511,"Rules":""}

- [ ] Provide the output of this command: `Status 0`:

STATUS 0 output here:

Shelly with Version 8.1.0.11:

03:55:19 MQT: stat/Shelly25_5/STATUS = {"Status":{"Module":0,"FriendlyName":["Shelly25_5","Shelly25_52"],"Topic":"Shelly25_5","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}} 03:55:19 MQT: stat/Shelly25_5/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"wohnzimmer","OtaUrl":"http://192.168.1.32:8000/shelly25.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:57:39","StartupUTC":"2020-03-24T01:57:40","Sleep":50,"CfgHolder":4617,"BootCount":18,"BCResetTime":"2020-03-20T18:24:36","SaveCount":763,"SaveAddress":"1F9000"}} 03:55:19 MQT: stat/Shelly25_5/STATUS2 = {"StatusFWR":{"Version":"8.1.0.11(tasmota)","BuildDateTime":"2020.03.24 02:55:46","Boot":31,"Core":"STAGE","SDK":"2.2.2-dev(38a443e)","Hardware":"ESP8266EX","CR":"414/699"}} 03:55:19 MQT: stat/Shelly25_5/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Eiswuerstchen",""],"TelePeriod":300,"Resolution":"559980C0","SetOption":["0000C80B","1405C8000100060000005A00000000000000","408000E8","00000000"]}} 03:55:19 MQT: stat/Shelly25_5/STATUS4 = {"StatusMEM":{"ProgramSize":497,"Free":1528,"Heap":23,"ProgramFlashSize":2048,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000407","8F000197","040003A1","00000004","010000C0","40008100","00000000"],"Drivers":"1,2,3,4,9,10,27,30","Sensors":"2,3"}} 03:55:19 MQT: stat/Shelly25_5/STATUS5 = {"StatusNET":{"Hostname":"shelly25-5","IPAddress":"192.168.1.207","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"98:F4:AB:F3:0F:80","Webserver":2,"WifiConfig":4,"WifiPower":17.0}} 03:55:19 MQT: stat/Shelly25_5/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.73","MqttPort":1883,"MqttClientMask":"Shelly25_5","MqttClient":"Shelly25_5","MqttUser":"tasmota","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30}} 03:55:19 MQT: stat/Shelly25_5/STATUS7 = {"StatusTIM":{"UTC":"2020-03-24T02:55:19","Local":"2020-03-24T03:55:19","StartDST":"2020-03-29T02:00:00","EndDST":"2020-10-25T03:00:00","Timezone":99,"Sunrise":"06:23","Sunset":"18:51"}} 03:55:19 MQT: stat/Shelly25_5/STATUS9 = {"StatusPTH":{"PowerDelta":0,"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}} 03:55:19 MQT: stat/Shelly25_5/STATUS10 = {"StatusSNS":{"Time":"2020-03-24T03:55:19","ANALOG":{"Temperature":47.9},"ENERGY":{"TotalStartTime":"2020-03-18T23:06:37","Total":0.202,"Yesterday":0.005,"Today":0.000,"Power":[0.000,0.000],"ApparentPower":[0.000,0.000],"ReactivePower":[0.000,0.000],"Factor":[0.00,0.00],"Voltage":0,"Current":[0.000,0.000]},"Shutter1":{"Position":0,"Direction":0,"Target":0},"TempUnit":"C"}} 03:55:19 MQT: stat/Shelly25_5/STATUS11 = {"StatusSTS":{"Time":"2020-03-24T03:55:19","Uptime":"0T00:57:39","UptimeSec":3459,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Eiswuerstchen","BSSId":"10:9A:DD:84:A0:07","Channel":6,"RSSI":64,"Signal":-68,"LinkCount":1,"Downtime":"0T00:00:09"}}}

Shelly with Version 8.2.0.1:

04:37:45 MQT: stat/Shelly25_4/STATUS = {"Status":{"Module":0,"FriendlyName":["Shelly25_4","Shelly25_42"],"Topic":"Shelly25_4","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}} 04:37:45 MQT: stat/Shelly25_4/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"wohnzimmer","OtaUrl":"http://192.168.1.32:8000/shelly25.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:03:09","StartupUTC":"2020-03-24T03:34:36","Sleep":50,"CfgHolder":4617,"BootCount":2,"BCResetTime":"2020-03-20T18:24:44","SaveCount":10,"SaveAddress":"1F8000"}} 04:37:45 MQT: stat/Shelly25_4/STATUS2 = {"StatusFWR":{"Version":"8.2.0.1(tasmota)","BuildDateTime":"2020.03.24 04:29:37","Boot":31,"Core":"STAGE","SDK":"2.2.2-dev(38a443e)","Hardware":"ESP8266EX","CR":"414/699"}} 04:37:45 MQT: stat/Shelly25_4/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Eiswuerstchen",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["0020C80B","1405C8000100060000005A00000000000000","408000E8","00000000"]}} 04:37:45 MQT: stat/Shelly25_4/STATUS4 = {"StatusMEM":{"ProgramSize":493,"Free":1532,"Heap":25,"ProgramFlashSize":2048,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000407","8F000196","040003A1","00000004","010000C0","40000100","00000000"],"Drivers":"1,2,3,4,9,10,27","Sensors":"2,3"}} 04:37:45 MQT: stat/Shelly25_4/STATUS5 = {"StatusNET":{"Hostname":"shelly25-4","IPAddress":"192.168.1.206","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"98:F4:AB:F3:EF:1F","Webserver":2,"WifiConfig":4,"WifiPower":17.0}} 04:37:45 MQT: stat/Shelly25_4/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.73","MqttPort":1883,"MqttClientMask":"Shelly25_4","MqttClient":"Shelly25_4","MqttUser":"tasmota","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30}} 04:37:45 MQT: stat/Shelly25_4/STATUS7 = {"StatusTIM":{"UTC":"2020-03-24T03:37:45","Local":"2020-03-24T04:37:45","StartDST":"2020-03-29T02:00:00","EndDST":"2020-10-25T03:00:00","Timezone":99,"Sunrise":"06:23","Sunset":"18:51"}} 04:37:45 MQT: stat/Shelly25_4/STATUS10 = {"StatusSNS":{"Time":"2020-03-24T04:37:45","ANALOG":{"Temperature":72.2},"ENERGY":{"TotalStartTime":"2020-03-18T22:50:13","Total":0.000,"Yesterday":0.003,"Today":0.000,"Power":[0,0],"ApparentPower":[0,0],"ReactivePower":[0,0],"Factor":[0.00,0.00],"Frequency":50,"Voltage":238,"Current":[0.000,0.000]},"Shutter1":{"Position":0,"Direction":0,"Target":0},"TempUnit":"C"}} 04:37:45 MQT: stat/Shelly25_4/STATUS11 = {"StatusSTS":{"Time":"2020-03-24T04:37:45","Uptime":"0T00:03:09","UptimeSec":189,"Heap":25,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Eiswuerstchen","BSSId":"10:9A:DD:84:A0:07","Channel":6,"RSSI":72,"Signal":-64,"LinkCount":1,"Downtime":"0T00:00:07"}}}

- [ ] Provide the output of the Console log output when you experience your issue; if applicable:
  _(Please use_ `weblog 4` _for more debug information)_

Console output here:


### TO REPRODUCE
_Steps to reproduce the behavior:_
Compile with Options:

define WEBSERVER_ADVERTISE

undef MQTT_HOST_DISCOVERY

define MDNS_ENABLED 1

undef USE_ADC_VCC

define USE_ADE7953

define USE_SHUTTER

define USE_EXPRESSION

define SUPPORT_IF_STATEMENT



### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._

Run with normal Temperature.

### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._
<img width="443" alt="Bildschirmfoto 2020-03-24 um 03 08 39" src="https://user-images.githubusercontent.com/45996965/77383976-899b7a00-6d84-11ea-9019-ce6c3e77d110.png">
<img width="411" alt="Bildschirmfoto 2020-03-24 um 03 08 33" src="https://user-images.githubusercontent.com/45996965/77383980-8bfdd400-6d84-11ea-96af-d503eac95b4d.png">

### ADDITIONAL CONTEXT
_Add any other context about the problem here._

The two Shellys2.5 are both flush-mounted in one wall directly next to each other. To have a direct comparison, I flashed only one of the two Shellys back to the state of the 15.03.2020. 

**(Please, remember to close the issue when the problem has been addressed)**
arendst commented 4 years ago

Just did a quick check and I see indeed a higher temperature reading but using an external thermometer it is still at the "old" temperature.

Apparently something has changed aroung the analog input (where the shelly temp sensor is connected). I'll investigate.

BTW. Could you report the output of command adcparam for both shellies pls.

arendst commented 4 years ago

As I upggraded my shelly 2.5 yesterday I see indeed a jump in temperature (+10 C) as soon as the latest development firmware version is active.

So this must be a software fault and not a real high temp error. Continue investigating...

kugelkopf123 commented 4 years ago

Hi! Thanks for checking. It's good to hear that only the display has changed and not the real temperature.

adcparam for 8.11.0.1: 11:30:51 MQT: stat/Shelly25_5/RESULT = {"AdcParam":[2,32000,10000,3350]}

for 8.2.0.1: 11:31:05 MQT: stat/Shelly25_4/RESULT = {"AdcParam":[2,32000,10000,3350]}

arendst commented 4 years ago

Pls also provide the output of command webrefresh

arendst commented 4 years ago

I currently see no relation to firmware changes. I do see an increase in measured temperature but not the amount you encounter. Also opening the webpage increases temp with 10 C but that's normal as it has to update the webpage regularly.

Are you sure the "hot" shelly reported cooler temps before or is this a new shelly with possible different NTC hardware?

kugelkopf123 commented 4 years ago

Both Shellys give:

11:58:13 MQT: stat/Shelly25_4/RESULT = {"WebRefresh":2345} as answer. Yes I had investigate myself in the Code but cant find anything. This Morning I had updated all Shellys2.5 to V8.2.0.1 then I noticed the higher values in all of them. To have a better comparison, I took exactly the pair that sits directly next to each other in the wall and only brought one back to the state of 15.03.2020 and thus had directly lower values. Apart from that, both Shellys came from the same box, I assume they have the same hardware. It is correct that opening the WEBGUI causes the temperature to rise. But with one it rises to about 45°C with the other to 65°C. Have opend both next to each other for some minutes. Bildschirmfoto 2020-03-24 um 12 07 46

arendst commented 4 years ago

Agree. Will need more investigation....

arendst commented 4 years ago

Problem is I do not feel the higher temp. I also do not measure the higher temp.

meingraham commented 4 years ago

@kugelkopf123

To eliminate difference in the hardware, perhaps you can reverse the firmware versions on your two Shelly devices to see if the higher temp readings follow the firmware regardless of which device. I know you had both on the new firmware but having one each on the older & the newer with the same environmental conditions and then "swapping" may provide some additional clues.

Mike

kugelkopf123 commented 4 years ago

@meingraham Did it. I have tried your suggestion and can confirm that the error goes with it. In general it was obvious, because Theo could also confirm it with his Shelly25 in his frist post.

kugelkopf123 commented 4 years ago

Bildschirmfoto 2020-03-24 um 15 11 24

The ambient Temp has rised that is the reason why the overall Temp is higher than this morning at 4 o Clock.

meingraham commented 4 years ago

Yes... it just makes it "definitive". Eliminates that question.

enricota66 commented 4 years ago

My device also heats up a lot. I tried with "Sleep 250" and "WifiPower" in command. But WifiPower doesn't seem to work. I put WifiPower 1 with the device near the router, but the signal does not go down Istantanea

kugelkopf123 commented 4 years ago

My device also heats up a lot. I tried with "Sleep 250" and "WifiPower" in command. But WifiPower doesn't seem to work. I put WifiPower 1 with the device near the router, but the signal does not go down Istantanea

BTW. I tested this WiFipower a week before on another Shelly that is 1m away from the router,too. Tried it down to the value of 0.1. nothing changed. Nor in the information or on the router setup page.

Jason2866 commented 4 years ago

First step it needs a measurement if the device is really! getting warmer. At the moment we have only displayed "something" This can NOT be done with Tasmota. Use a extra thermometer to measure with old and new firmware. Depending on this we know (a bit more) where to look.

enricota66 commented 4 years ago

I have tested with version 8.1.0.I have read similar heat values of version 8.2.0.1 I don't have a thermoscanner but at the touch of the device the values seem plausible. I have seen that temperatures rise a lot when the all 2 relays are turned on. However, high temperatures do not depend on the load applied. I have no experience with Shelly because I have only sonoff on my home. I'm afraid Shelly's heat may be a device construction problem

kugelkopf123 commented 4 years ago

Unfortunately I currently have no Shelly2.5 that is not yet installed in any wall on my desk. I have to remove one first. Furthermore I also lack a suitable thermometer to validate the values. Also I could only operate the Shelly via 3.3V and feel it with my finger when the case is open. But this would be a very subjective evaluation. @enricota66 Actually the design of the Shelly2.5 is not yet the yellow one. Switching on the relays increases the temperature. That is correct. However, I use all of the Shelly2.5 in my home to control my blinds. So the relays are only running for a few seconds. My tests have always been done with relays switched off for a long time. Does i get you right? Have you done your test now with a sonoff device or shelly?

If I understood Theo's first post correctly, he could not detect any physical increase in temperature. I can see that the temperature is high at the beginning and then lower when flashing back, but this can also be related to the fact that the built-in ESP works more when flashing and therefore a high temperature is reached.

enricota66 commented 4 years ago

I Have sonoff basic and sonoff mini inside the electrical boxes of the wall to control the house lights and HomeAssitant automatisms and MQTT protocol. Everything works perfectly with the Tasmota firmware. My intent was to replace 2 basic sonoff devices inside a box with Shelly 2.5 Before doing this I am tensing shelly on the desk for my use the relays must remain on for a long time. I have 2 shelly2.5 devices on the desk, the first with one with tasmota firmware and the second with original firmware. From the tests I'm doing with 2 relays on, the original one seems to be more cooler. However I want to measure the temperature with an instrument

Jason2866 commented 4 years ago

Please dont mix up different devices in this thread. It is about Shelly 2.5 Feeling is no validate way of measuring ;-) Please post only measured values of a Shelly 2.5

arendst commented 4 years ago

@enricota66 pls do measure externally. The shelly 2.5 internal temperature is measured by a NTC thermistor. To get a reasonable reading it's result needs to be calculated. The current calculation is based on parameters I once received from Shelly. These parameters might have been changed so in that case the AdcParam parameters need a change too.

enricota66 commented 4 years ago

@enricota66 pls do measure externally. The shelly 2.5 internal temperature is measured by a NTC thermistor. To get a reasonable reading it's result needs to be calculated. The current calculation is based on parameters I once received from Shelly. These parameters might have been changed so in that case the AdcParam parameters need a change too.

Tried one hour and 30 minutes with the relays on. Indeed, there seem to be no important differences on the devices ( Tasmota ver is 8.2.0.1)

IMG-20200325-WA0008~2 IMG-20200325-WA0009~2

arendst commented 4 years ago

Great! Now what are the temperatures reported by Shelly and Tasmota in those situations?

enricota66 commented 4 years ago

Great! Now what are the temperatures reported by Shelly and Tasmota in those situations?

Sure The Tasmota temperature in that situation is around 60 c. But I was unable to find Shelly's data in its application. Can anyone help me, where can I find it?

arendst commented 4 years ago

Background info shelly https://www.facebook.com/groups/1686781668087857/permalink/2054834997949187/

ascillato commented 4 years ago

From previous link:

About question:How much is PCB operating temperature to Shelly2.5, Shelly1PM and Shelly PlugS: Max ambient temperature is 40 degree. With no load PCB temperature is 55-60 degree. At MAX load continuesly is 87-90 degree. Heating protection will switch off device at 95 degree. All parts inside are 105-120 degree certifed for continuous usage.

So, the actual reported value of Tasmota is Right and in previous versions was reported wrongly. No real increase of PCB temperature between Tasmota versions.

effelle commented 4 years ago

Meaning the Shelly 2.5 needs a special adcparam setup to work properly, I suppose. Not easy without knowing the actual resistor used and what type of NTC is inside it...

kugelkopf123 commented 4 years ago

@enricota66 pls do measure externally. The shelly 2.5 internal temperature is measured by a NTC thermistor. To get a reasonable reading it's result needs to be calculated. The current calculation is based on parameters I once received from Shelly. These parameters might have been changed so in that case the AdcParam parameters need a change too.

Tried one hour and 30 minutes with the relays on. Indeed, there seem to be no important differences on the devices ( Tasmota ver is 8.2.0.1)

IMG-20200325-WA0008~2 IMG-20200325-WA0009~2

First of all, thank you very much for your commitment! So how exactly is this meant? The temperature of the measured external thermometer and the one displayed in the Tasmota WebGUI did not differ?

Or both devices, one with the current Dev Branch and one with the original FW, got almost identical temperatures on the external thermometer?

If that was the case, what did the ShellyConnect app provide for a temperature value at that time? And was this value identical to the value from the Tasmota WebGUI?

effelle commented 4 years ago

@enricota66 now that you have your Shellys in "test mode", you could try to change the value of the resistor using the command adcparm and see if you can match the temperature shown by the one with Tasmota and your thermometer. The default values are 2,32000,10000,3350, where the third value is the resistor (10k). Changing the resistor value you will have a proportional higher/lower reading. Dai che risolviamo! :)

arendst commented 4 years ago

Stop!

No need to change adcparam. The internal shelly tmperature IS 60 degrees C as also reported by shelly. See link above.

The shelly should report it's internal temp and not the external temp.

As already was concluded the tasmota adcparam are ok (I got them from shelly) and result in the same theoretic shelly temp.

To extract the original shelly temp a mqtt server is needed to address a documented topic within the device.

effelle commented 4 years ago

Understood, then the NTC is NOT for external reading but just for thermal control. That changes all.

ascillato commented 4 years ago

The temperature is measured IN the internal PCB. Comparing to a measurement from the exterior is going to be a lot lower than the actual pcb temperature. As Tasmota is reading now is OK. About 40 to 60C when relays are OFF.

kugelkopf123 commented 4 years ago

I found out that if you remove the ADE7953 chip from the template, the temperature is much lower. Maybe interesting for some people who use the Shelly2.5 only for the shutters and therefore don't need a power meter.

{"NAME":"Shelly 2.5 test","GPIO":[56,0,19,0,21,127,0,0,0,126,0,22,0],"FLAG":2,"BASE":18}

ascillato commented 4 years ago

From the shelly support group on Facebook. Posted by Shelly.

shelly thermal

kugelkopf123 commented 4 years ago

Didnt knew that its possible to run it without N. I saw it yesterday with the Shelly Dimmer SL? I think. Would be nice to know how big this load was in this picture.

BassT23 commented 4 years ago

I found out that if you remove the ADE7953 chip from the template, the temperature is much lower. Maybe interesting for some people who use the Shelly2.5 only for the shutters and therefore don't need a power meter.

{"NAME":"Shelly 2.5 test","GPIO":[56,0,19,0,21,127,0,0,0,126,0,22,0],"FLAG":2,"BASE":18}

Thanks for the tip. -11°C with ADE7953 disabled!

Smandurlo commented 4 years ago

I have the same issue with my shelly(s) 2.5. With original firmware the temperature is 60°C with both relays ON, with Tasmota 8.3.1 the temperature is 87°C (and probably increasing) with both relays ON. Nothing connected to the relays. I flashed 8 of them with the same behaviour. Four of them were in use with the original firmware (so I know their temperature while in use), I flashed the other 4 directly from the box. Did you find a solution for it? Thanks! EDIT: temperature arrived to 89,9°C without loads, just both relays on. Should we just set SetOption42 to 0 to disable the overtemp protection until this is fixed? EDIT2: it went to overtemp and switched off both relays. No powers on the relays. This is weird

stefxx commented 4 years ago

I recently installed 4 of those Shelly 2.5 devices, and without any load the temperature is between 65 and 80 degrees. I use them for shutters, and the max I've seen is 89.6. Using Tasmota 8.4.0.

I really hope something is wrong with the reading, because those temperatures scare me a little...

Should I be worried? Please advise.

BassT23 commented 4 years ago

No. If you use as shutter control, the temp is only a few seconds high. But Im also confused; my Shelly 2.5 had a safety switch by ~75°C, so why could you see so hight temps?

I use it as a double switch. Only if my secound Relais (with nothing connected) the temp will climb over 75° in hot summer. For me, I disabled PowerMeter and the secound Relais. The secound switch will only send message (MQTT) while switching - without Relais switching. So for me no temp problems any more, also in hot summer :)

stefxx commented 4 years ago

Thanks. With power measurements turned off (by using the template from the post of @kugelkopf123 #issuecomment-606963545) the temperature remains between 54 and 62 degrees C. Which is fine for the shutters.

But I want to use those devices as normal dual switches as well, preferable including power measurements. Not sure if that is a good idea at temperatures of 80 C and up.

stefxx commented 4 years ago

One of the Shelly 2.5 devices I configured for shutter operation climbed back to 72 C without any operation/load. Even with all power measurements disabled... the other one remains quite stable around 54/55 degrees.

stefxx commented 4 years ago

I did a few tests in trying to get the temp down. I have found two workarounds:

Both bring the temp down to a max 55-60 range, without any load.

Smandurlo commented 4 years ago

You could edit che template to remove the ADE chip. It won't show the power consumption, but you will get much lower temperature. I think there is a bug in newer tasmota versions

Il sab 22 ago 2020, 23:18 stefxx notifications@github.com ha scritto:

I did a few tests in trying to get the temp down. I have found two workarounds:

  • Downgrade to 8.1.0.
  • Set "Sleep" to 250

Both bring the temp down to a max 55-60 range, without any load.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7991#issuecomment-678695962, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXTCZN474SNFXLHBC73TDDSCAY23ANCNFSM4LSK5EZQ .

ascillato commented 4 years ago

The temperature values measured with and without load using Tasmota, are nearly the same as with stock firmware. The higher value of temperature is dependant on how much current is passing thru your device. The CPU usage (like with sleep set to 0) also increments it but not as much as the actual load connected to the shelly.

stefxx commented 4 years ago

@ascillato , I have to disagree. There is a significant temperature difference between the stock firmware and Tasmota 8.4.0. Without any load the difference is around 20 degrees in my tests, with similar circumstances.

Between the stock firmware and Tasmota 8.1.0 the difference is negligible.

If I could use the Shutter functions with 8.1.0 I would revert to this version. For now, I mitigated the issue by disabling power measurements and a higher sleep value.

Smandurlo commented 4 years ago

I agree with stefxx. The only way to keep the temperature the same like the stock firmware is to disable the ADE chip. With the ADE chip the temperature goes too high. If I keep the web page open, without any load, the shelly goes to 90°C and more and it switches off due to the termal protection. This is obviously totally wrong.

Il giorno dom 23 ago 2020 alle ore 09:06 stefxx notifications@github.com ha scritto:

@ascillato https://github.com/ascillato , I have to disagree. There is a significant temperature difference between the stock firmware and Tasmota 8.4.0. Without any load the difference is around 20 degrees in my tests, with similar circumstances.

Between the stock firmware and Tasmota 8.1.0 the difference is negligible.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7991#issuecomment-678738287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXTCZN3TR4KHRO744HUDH3SCC5V7ANCNFSM4LSK5EZQ .

kugelkopf123 commented 4 years ago

I don’t know how precisely This ade chip works. But perhaps the original software doesn’t read the chip that often as Tasmota do? Perhaps this could be a reason.

Sent with GitHawk

stefxx commented 4 years ago

Can we re-open this issue? It is a real issue, not something with wrong readings

From previous link:

About question:How much is PCB operating temperature to Shelly2.5, Shelly1PM and Shelly PlugS: Max ambient temperature is 40 degree. With no load PCB temperature is 55-60 degree. At MAX load continuesly is 87-90 degree. Heating protection will switch off device at 95 degree. All parts inside are 105-120 degree certifed for continuous usage.

So, the actual reported value of Tasmota is Right and in previous versions was reported wrongly. No real increase of PCB temperature between Tasmota versions.

Either way, there is a real increase in the actual temperature of the device since version 8.2.0. It can be felt easily by simply touching the Shelly 2.5 by hand. I have two of them next to each other, one with 8.1 and one with 8.4 and the difference is huge!

Can we please reopen this issue and have another look into this? Thanks!

Smandurlo commented 4 years ago

I think so. I keep the ADE chip not reading the power consumption otherwise the Shelly switch off because of overheating eventually.

Il sab 12 set 2020, 11:27 stefxx notifications@github.com ha scritto:

Can we re-open this issue? It is a real issue, not something with wrong readings

From previous link:

About question:How much is PCB operating temperature to Shelly2.5, Shelly1PM and Shelly PlugS: Max ambient temperature is 40 degree. With no load PCB temperature is 55-60 degree. At MAX load continuesly is 87-90 degree. Heating protection will switch off device at 95 degree. All parts inside are 105-120 degree certifed for continuous usage.

So, the actual reported value of Tasmota is Right and in previous versions was reported wrongly. No real increase of PCB temperature between Tasmota versions.

Either way, there is a real increase in the actual temperature of the device since version 8.2.0. It can be felt easily by simply touching the Shelly 2.5 by hand. I have two of them next to each other, one with 8.1 and one with 8.4 and the difference is huge!

Can we please reopen this issue and have another look into this? Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7991#issuecomment-691454569, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIXTCZKQODJIXQX7WZV6XTLSFM5GPANCNFSM4LSK5EZQ .

kugelkopf123 commented 4 years ago

I have no Idea how that can be. If you have two devices, perhaps it is possible for you to make a real mesurament. With two Sensors. One on each shelly. Best if its open. Perhaps in the latest Version from Tasmota, the ADE Chip gets triggerd more often? Perhaps this is the reason...

stefxx commented 4 years ago

To get out of the right/wrong game here, I did some more testing in a more controlled way. Note that all tests have been done with an ambient temperature of 22-22 degrees, and the Shelly 2.5 PM devices are on my tabletop, not enclosed in any way.

One device has stock firmware 1.8.3 installed. The other one has Tasmota 8.5.0, using the default Blackadder device template. They are only connected to L and N, no load connected to them.

First, with both switches ON, I’ve let them run for about 45 minutes. At that point the temperature stabilized around 75 degrees on both. image

Then I let the browser open on both devices, which has a (known) effect on the temperature of a Tasmota device of ~10 degrees. And indeed, after 10 minutes, the Tasmota stabilized around 85 degrees. No changes to the stock Shelly: image

Next, I stopped actively monitoring the web interface and I switched both switches off, on both devices. They stabilized just above 60 degrees. image

So far, so good. Still think that the temperature is quite high, but the difference with the stock firmware is negligible.

Next step is to downgrade the Tasmota device to firmware 8.1.0. Switches still of, no webserver session active, and after some time the temperature stabilizes around 50 degrees! More than 10 degrees less than 8.5.0! image

Final test with both switches on, on both devices. Still no load connected. Stock firmware 75 degrees, Tasmota 8.1.0 “only” 62. image

My conclusion: as the issue starter stated, there is a significant difference in Shelly 2.5PM temperatures between Tasmota versions, most likely introduced with 8.2.0. 10 to 13 degrees to be exact. However, the difference between stock firmware and Tasmota 8.5.0 is next to nothing.

Also, in general I find the temperature of those devices high. It might be within specs, but you can feel they are getting quite hot and that will only increase when built in small boxes with no space to breathe. So, if we can lower the temperature somehow (preferably not by disabling the PWM or increase the Sleep) that would be very welcomed. The question remains what changed in 8.2.0 wrt these devices… and is it something that might be reversed or corrected?