New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shelly 2.5 gets significantly hotter since 8.2.0.1 #7991
Comments
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 |
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... |
Hi! adcparam for 8.11.0.1: for 8.2.0.1: |
Pls also provide the output of command |
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? |
Agree. Will need more investigation.... |
Problem is I do not feel the higher temp. I also do not measure the higher temp. |
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 |
@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. |
Yes... it just makes it "definitive". Eliminates that question. |
First step it needs a measurement if the device is really! getting warmer. |
I have tested with version 8.1.0.I have read similar heat values of version 8.2.0.1 |
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. If I understood Theo's first post correctly, he could not detect any physical increase in temperature. |
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. |
Please dont mix up different devices in this thread. It is about Shelly 2.5 |
@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 |
Tried one hour and 30 minutes with the relays on. |
Great! Now what are the temperatures reported by Shelly and Tasmota in those situations? |
Sure |
Background info shelly https://www.facebook.com/groups/1686781668087857/permalink/2054834997949187/ |
From previous link:
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. |
Meaning the Shelly 2.5 needs a special |
First of all, thank you very much for your commitment! 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? |
@enricota66 now that you have your Shellys in "test mode", you could try to change the value of the resistor using the command |
Thx again. I will dive in today. |
Fix Shelly 2.5 higher temperature regression from 8.2.0.1 (#7991)
I think the issue is solved! Based on the latest temp pictures showing tasmota versions with higher values starting from version 8.3.0 AND the initial issue where it seemed to start from v8.2.0.1 I could easily conclude where the higher temp came from. Since v8.2.0.1 all GPIO's are no longer set to input at restart first before they are initialized by tasmota but after tasmota configures the GPIO. For the ADE7953 this lead to an anomaly where the IRQ input was never set to input but stayed in limbo which could easily be an output which in turn would make the IRQ circuit act as a load resulting in additional heat. The latest commit solves this and I noticed indeed a major temp decrease on my Shelly 2.5 Thx to all who have helped in solving this issue especially the images helped a lot! |
So, if I will set the ADE chip on again, I shouldn't see the temperature
going high anymore, isn't it?
Thank for all your efforts guys!
Il gio 24 set 2020, 12:14 Theo Arends <notifications@github.com> ha scritto:
… I think the issue is solved!
Based on the latest temp pictures showing tasmota versions with higher
values starting from version 8.3.0 AND the initial issue where it seemed to
start from v8.2.0.1 I could easily conclude where the higher temp came from.
Since v8.2.0.1 all GPIO's are no longer set to input at restart first
before they are initialized by tasmota but after tasmota configures the
GPIO. For the ADE7953 this lead to an anomaly where the IRQ input was never
set to input but stayed in limbo which could easily be an output which in
turn would make the IRQ circuit act as a load resulting in additional heat.
The latest commit solves this and I noticed indeed a major temp decrease
on my Shelly 2.5
Thx to all who have helped in solving this issue especially the images
helped a lot!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7991 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIXTCZMN5W7PCEZLLJ4U73DSHMLZRANCNFSM4LSK5EZQ>
.
|
This is excellent! Great teamwork! Can wait to test it (probably tonight). Thanks!! |
Running 3 devices with latest build for about 2 hours. Temperature stabilizes between 45 and 55 degrees. Very happy with this!! |
I am glad that this problem, which I discovered at the end of March, has finally been solved. So I can switch on the ADE again. |
Before people start comparing this with my previous measurements; this is with both relays off. When they are both on, add about 10 degrees. Still, much lower then before! |
See my explaination earlier. Remeber, IRQ is an Interrupt Request from the ade to the esp8266 and not a reset signal. As gpio16 cannot handle interrupts the IRQ is not used. Due to the gpio init change the IRQ gpio was never correctly initialized resulting in an output signal from the esp8266 which would be shorted to gnd by any ade irq resulting in heat and possibly hardware failure over time. |
Wow, what a quick fix of the issue! According to the ADE's datasheet, it's /IRQ is low-active, meaning it stays high for most of the time. If the ESP continuously outputs a low, the one sources a current which the other one immediately sinks. You write it is the GPIO16. That means, to select this Pin as an Input, like Button or Switch would have made the problem go away? Or set it to counter and count the interrupts? Fabulous, will try it out ASAP. |
Tried it today. Updated from 8.3.1 to todays Dev Branch. Works as long as i don't set GPIO GPIO16 to ADE7953 IRQ.
|
No problem at all:
Pls try with the default template as I noticed you use a strange template with even a button3 in it... |
@arendst it was the default template from blackadder. Frist i´ve tried my own. But it was the same as the one from the template website. Then i tried the template from blackadder via:
And btw. There is no switch 3 in my template... |
Anyway it's not related to high temp so I suggest you open a new issue with thorough logging. |
@arendst Wasnt shure. Because it has to do with this "fix". Thought it might me better to post here. |
If you install the 8.5 (without fix) and turn on the ADE chip, do you still
have that problem? The temp should be higher, but at least you address the
problem
Il ven 25 set 2020, 11:46 kugelkopf123 <notifications@github.com> ha
scritto:
… @arendst <https://github.com/arendst> Wasnt shure. Because it has to do
with this "fix". Thought it might me better to post here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7991 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIXTCZIE5F4L3XNNDTSZ3VDSHRRFZANCNFSM4LSK5EZQ>
.
|
Closing this temperature issue as it has been fixed. Thanks everyone for the hard work. It is very appreciated. 👍 Support InformationSee Docs for more information. |
Can confirm that the Temp is better now with the fix! My problem with the Exception was fixed via a "reset 1" and reconfig the Shutter. |
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!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
Compile with Options:
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.
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)
The text was updated successfully, but these errors were encountered: