Tasmota often restart reason Hardware Watchdog #19942
-
PROBLEM DESCRIPTIONA clear and concise description of what the problem is. REQUESTED INFORMATIONMake sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Configuration output here:
Rules output here:
STATUS 0 output here:
STATUS = {"Status":{"Module":18,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"tasmota_B6C53F","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,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}}
STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota-IT.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:19:21","StartupUTC":"2023-11-06T04:59:49","Sleep":50,"CfgHolder":4617,"BootCount":68,"BCResetTime":"2023-10-22T20:53:33","SaveCount":115,"SaveAddress":"F7000"}}
STATUS2 = {"StatusFWR":{"Version":"13.2.0(tasmota)","BuildDateTime":"2023-10-19T09:07:34","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"372/699"}}
STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["FASTWEB-7HpvD6-2.4GHZ",""],"TelePeriod":10,"Resolution":"558180C0","SetOption":["00008009","2805C80000000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
STATUS4 = {"StatusMEM":{"ProgramSize":637,"Free":364,"Heap":22,"ProgramFlashSize":1024,"FlashSize":4096,"FlashChipId":"16405E","FlashFrequency":40,"FlashMode":"DOUT","Features":["00000410","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,68","Sensors":"1,2,3,4,5,6","I2CDriver":"7"}}
STATUS5 = {"StatusNET":{"Hostname":"tasmota-B6C53F-1343","IPAddress":"192.168.1.63","Gateway":"192.168.1.254","Subnetmask":"255.255.255.0","DNSServer1":"192.168.1.254","DNSServer2":"0.0.0.0","Mac":"7C:87:CE:B6:C5:3F","Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.69","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_B6C53F","MqttUser":"mosquitto","MqttCount":2,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
STATUS7 = {"StatusTIM":{"UTC":"2023-11-06T05:19:10","Local":"2023-11-06T06:19:10","StartDST":"2023-03-26T02:00:00","EndDST":"2023-10-29T03:00:00","Timezone":"+01:00","Sunrise":"07:44","Sunset":"17:22"}}
STATUS9 = {"StatusPTH":{"PowerDelta":[0,0,0],"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
STATUS10 = {"StatusSNS":{"Time":"2023-11-06T06:19:10","ENERGY":{"TotalStartTime":"2023-10-22T21:45:01","Total":3.153,"Yesterday":1.752,"Today":0.172,"Period":[0,0,0],"Power":[0,0,2],"ApparentPower":[0,0,5],"ReactivePower":[0,0,5],"Factor":[0.00,0.00,0.34],"Frequency":[50,50,50],"Voltage":[240,240,240],"Current":[0.000,0.000,0.021]}}}
STATUS11 = {"StatusSTS":{"Time":"2023-11-06T06:19:10","Uptime":"0T00:19:21","UptimeSec":1161,"Heap":22,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":2,"Wifi":{"AP":1,"SSId":"FASTWEB-7HpvD6-2.4GHZ","BSSId":"CC:B1:82:1F:4F:F8","Channel":1,"Mode":"11n","RSSI":100,"Signal":-29,"LinkCount":1,"Downtime":"0T00:00:05"}}}
Console output here:
TO REPRODUCESteps to reproduce the behavior: EXPECTED BEHAVIOURA clear and concise description of what you expected to happen. SCREENSHOTSIf applicable, add screenshots to help explain your problem. ADDITIONAL CONTEXTAdd any other context about the problem here. (Please, remember to close the issue when the problem has been addressed) |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 16 replies
-
|
Known problem of the Wemos D1 mini clones. The onboard 3.3V Voltage regulator is to weak. |
Beta Was this translation helpful? Give feedback.
-
|
Thank's for your reply. Can you tell me how I can replace the voltage regulator or link me a NodeMCU board? |
Beta Was this translation helpful? Give feedback.
-
|
Replacement is a quite tricky operation because it is very tiny on the board. But you can easily install a second one between the 5V, 3.3V and ground connector. This works very well. You might order at AliExpress e.g. the HT7833 with the long pins. |
Beta Was this translation helpful? Give feedback.
-
No, it's not my forte operating on these small circuits. I think I explained myself badly. I intended to exchange the Wemos D1 for a decent one. |
Beta Was this translation helpful? Give feedback.
-
|
If you are on changing for another board, I strongly suggest going for a board based on ESP32-C3 |
Beta Was this translation helpful? Give feedback.
-
|
I have a pair of Esp32 wrom32s, can I use one of these instead of the wemos? |
Beta Was this translation helpful? Give feedback.
-
|
Dev boards based on ESP32-WROOM are like NodeMCU, just with ESP32 instead of ESP8266. Should generally be fine, as they are well supported by Tasmota. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I was able to replace the Wemos D1 with an Esp32 board. The three Pzem-004T sensors connected to the board work well. |
Beta Was this translation helpful? Give feedback.
-
|
On ESP32 you can get up to 8 PZEM |
Beta Was this translation helpful? Give feedback.
-
|
I'm not an expert in these things and I couldn't answer. I'm tempted to say that it is more convenient to have more wires but perhaps the card would be overloaded? On the other hand, adding a wireless device to the router shouldn't cause any problems... what would you do? |
Beta Was this translation helpful? Give feedback.
-
|
From my viewpoint, long wires can be badly inconvenient to mess with. Thus, it depends on the practicality of handling the wires. I'd not expect an ESP32 to be anywhere near overloaded by 8 PZEM devices. |
Beta Was this translation helpful? Give feedback.
-
|
I replaced the Wemos D1 Mini with an Esp32, I no longer have reboots. Thank you all. |
Beta Was this translation helpful? Give feedback.
-
I'm reopening this thread for an update. I installed 3 Pzem using esphome and everything works fine. So I thought about adding more Pzem to the same Esp32 board but as soon as I add the fourth one only two work. If I leave three they all work. So I have to think that the Esp32 board doesn't support more than three Pzem or is the problem EspHome? |
Beta Was this translation helpful? Give feedback.
-
|
This is Tasmota Discussions. If you have questions regarding esphome ask there. |
Beta Was this translation helpful? Give feedback.
-
|
And the discussion is about hardware watchdog, not PZEM |
Beta Was this translation helpful? Give feedback.
-
|
is there any documentation on the voltage regulator issue? My D1 mini clone appears to have a DE=A1D marking, suggesting it is a WL9003S5-33 300mA linear voltage regulator. My 12VDC power supply provides 750mA of current, and reads at approximately 14V. I'm using a DC power shield and relay shield, so the D1 and relay are both powered from the 5V rail and should not be drawing current. My design is such that the relay is configured to always be ON but is wired in the NO position and tasmota default poweron state is ON. I have a switch that is NC and pushing it opens the circuit, triggering the relay to turn off. So the switch being NC probably has a negligible current draw. I still think that the 300mA would be sufficient. The restarts only appear to happen when the relay (powering a magnetic door lock, also energized via the 12V 750mA supply) re-engages ONLY in the case where the door is shut. If the relay engages while the door is still open, the restart does not happen. My only suspicion here is that the power supply is not providing clean enough power. The DC adapter appears to read closer to 14V when measured by a DMM. Do you still suspect the onboard regulator to be a problem in this case? |
Beta Was this translation helpful? Give feedback.
-
|
that's MAX current through an entire lock engage/disengage cycle. |
Beta Was this translation helpful? Give feedback.
-
|
That's the problem |
Beta Was this translation helpful? Give feedback.
-
|
Would this also be a solution for Shelly devices like 1PM, 2.5 etc.? (the non-plus versions) I had a few watchdog restarts on a 2.5 and when searching for reasons, I found this thread. |
Beta Was this translation helpful? Give feedback.
-
|
That would depend on what voltage regulator is already on the boards. When it comes to Shelly 2.5, I think I saw someone report better stability after replacing a capacitor gone bad. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, one of the Elkos died on me. Will need to check if that is the only issue. |
Beta Was this translation helpful? Give feedback.
Known problem of the Wemos D1 mini clones. The onboard 3.3V Voltage regulator is to weak.
The orig Wemos D1 minis do have an 500mA Type. Nearly all so called Wemos D1 minis are fake/clones and do have only a 150mA Type. This is causing issues. To be clear, NOT an Tasmota problem.
Solving: Replace the Voltage regulator against a 500mA type or use a NodeMCU board.
NodeMCU boards (even the clones) have a decent 3.3V Voltage regulator.