Recurrent Hardware Watchdog Restarts

[meingraham]

• Searched the problem in issues (https://github.com/arendst/Sonoff-Tasmota/issues)
• Searched the problem in the wiki (https://github.com/arendst/Sonoff-Tasmota/wiki/Troubleshooting)
• Searched the problem in the forum (https://groups.google.com/d/forum/sonoffusers)
• Searched the problem in the chat (https://discord.gg/Ks2Kzd4)
• Development/Compiler/Upload tools used: TASMOTA OTA
• Hardware used: HW-655 w/ PZEM-004T
• If a pre-compiled release or development binary was used, which one?:

Program Version: 6.3.0.16(a516b25-sonoff)
Build Date & Time: 2018-12-09T18:24:40
Core/SDK Version: 2_4_2/2.2.1(cfd48f3)

• You have tried latest release or development binaries? Not yet. Trying to not introduce variables to my troubleshooting.

STATUS = {"Status":{"Module":18,"FriendlyName":["Power Monitor HW-655 PZEM"],"Topic":"PZEM_PowerMonitor","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":0,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/sonoff-sensors.bin","RestartReason":"Hardware Watchdog","Uptime":"1T02:16:52","StartupUTC":"2019-01-20T17:00:27","Sleep":25,"BootCount":53,"SaveCount":184,"SaveAddress":"FB000"}}
STATUS2 = {"StatusFWR":{"Version":"6.3.0.16(a516b25-sonoff)","BuildDateTime":"2018-12-09T18:24:40","Boot":6,"Core":"2_4_2","SDK":"2.2.1(cfd48f3)"}}
STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":2,"SysLog":2,"LogHost":"myHost","LogPort":514,"SSId":["mySSID",""],"TelePeriod":300,"SetOption":["00208108","559580C0","000000C0"]}}
STATUS4 = {"StatusMEM":{"ProgramSize":520,"Free":480,"Heap":16,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"146085","FlashMode":3,"Features":["00000809","0FDAE794","000383A0","23B617CE","00003BC0"]}}
STATUS5 = {"StatusNET":{"Hostname":"PZEM_PowerMonitor-8082","IPAddress":"192.168.1.nnn","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"myMAC","Webserver":2,"WifiConfig":4}}
STATUS6 = {"StatusMQT":{"MqttHost":"myHost","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_myMAC","MqttUser":"myUserID","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
STATUS7 = {"StatusTIM":{"UTC":"Mon Jan 21 19:17:19 2019","Local":"Mon Jan 21 14:17:19 2019","StartDST":"Sun Mar 10 02:00:00 2019","EndDST":"Sun Nov 03 02:00:00 2019","Timezone":99,"Sunrise":"07:32","Sunset":"17:43"}}
STATUS9 = {"StatusPTH":{"PowerDelta":0,"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0}}
STATUS10 = {"StatusSNS":{"Time":"2019-01-21T14:17:19","ENERGY":{"TotalStartTime":"2018-12-10T17:32:10","Total":23.483,"Yesterday":1.175,"Today":2.619,"Power":0.00,"ApparentPower":0.00,"ReactivePower":0.00,"Factor":0.00,"Voltage":121.70,"Current":0.000}}}
STATUS11 = {"StatusSTS":{"Time":"2019-01-21T14:17:19","Uptime":"1T02:16:52","Vcc":3.438,"SleepMode":"Dynamic","Sleep":25,"LoadAvg":39,"Wifi":{"AP":1,"SSId":"mySSID","BSSId":"myBSSIdMAC","Channel":1,"RSSI":52}}}

Jan  9 00:11:12: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}
Jan 14 21:05:17: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}
Jan 15 03:38:30: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}
Jan 15 22:52:44: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}
Jan 18 00:17:55: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}
Jan 20 12:00:35: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Hardware Watchdog"}

I don't see a pattern as to what might be causing this. I have looked at the logs to see if there was something logged that was similar each time and I can't spot a pattern. I have the SysLog level 2 log files (compressed) for these days if you would like for me to PM them to you to see if you can spot something relevant.

Thanks.

Mike

[arendst]

Check if you use software serial (at power up) and if so change to hardware serial by selecting the correct GPIOs. See Whats New for correct GPIO selection

[meingraham]

@arendst Theo,

This is what I have - connection diagram and Generic Module configuration screenshots

Full write-up - https://github.com/arendst/Sonoff-Tasmota/wiki/US-240V-Clothes-Dryer-PZEM004T-Energy-Monitor

if you use software serial (at power up)

At power up? I'm not sure I understand the question.

The device operates for long periods of time. I saw the restart reason when I was performing a STATUS 0 a few days ago. That's when I implemented my syslog server to capture more information because the Hardware Watchdog restart doesn't happen that often.

Mike

[ascillato]

Hi,

There isn't a clear bug. Could be a bad flashing, a defective device, a power source regulator issue.

You have tried latest release or development binaries? Not yet. Trying to not introduce variables to my troubleshooting.

As there isn't a clear bug, you should try latest version to see if your issue repeats. Also you should try another device also to avoid a defective hardware.

[arendst]

Right.

At power up I meant that there will be a message telling you if either Software or Hardware Serial is detected.

From your config it seems you are using software serial. Just swap both config GPIOS (do not swap cables) and it should start using hardware serial.

[meingraham]

@arendst @ascillato

1. I'll give Theo's suggestion a try first for a few days to see if that resolves the issue. Theo - please confirm this is what you mean by "swap both config GPIOS".
   
   I will not swap the physical cables.
   Current configuration
   
   I do not see any message on the web Console (weblog 4) at startup indicating that it has detected what type of serial connection (hardware or software) is present.

2. I will update the firmware on the ESP-01 (onboard module of the HW-655) to the latest development release. Depending on whether I have hardware or software serial will determine whether I use the 2.3.0 or 2.4.2 Core (I have better luck with 2.3.0 although this unit with 2.4.2 seems to keep a pretty good Wi-Fi connection).

3. I will take out the ESP-01 and erase the flash memory and flash the latest firmware.

4. I don't have any additional ESP-01 so I don't have the option to swap hardware. I'd have to order one. As that's the module that is "Watchdog" restarting, I'm assuming that the HW-655 and the PZEM would not be the ones causing the issue. But I won't cross this bridge before I try a new ESP-01... which is a bridge way down the road for now.

Mike

[arendst]

Bullet 1 is hardware serial indeed.

If you restart with weblog set to 2 you could see:

00:00:00 Project sonoff Pzem (Topic pzem, Fallback DVES_0CA8BA, GroupTopic sonoffs) Version 6.4.0.1(sonoff)-2_4_2
00:00:00 SNS: Hardware Serial
00:00:00 WIF: Connecting to AP2 indebuurt2 in mode 11N as pzem...
00:00:04 WIF: Connected
00:00:04 HTP: Web server active on pzem with IP address 192.168.2.157
00:00:05 MQT: Attempting connection...
00:00:05 MQT: Connected
00:00:05 MQT: tele/pzem/LWT = Online (retained)
00:00:05 MQT: cmnd/pzem/POWER = 
00:00:06 MQT: tele/pzem/INFO1 = {"Module":"Sonoff Basic","Version":"6.4.0.1(sonoff)","FallbackTopic":"DVES_0CA8BA","GroupTopic":"sonoffs"}
00:00:06 MQT: tele/pzem/INFO2 = {"WebServerMode":"Admin","Hostname":"pzem","IPAddress":"192.168.2.157"}
00:00:06 MQT: tele/pzem/INFO3 = {"RestartReason":"Software/System restart"}
00:00:06 MQT: stat/pzem/RESULT = {"POWER":"ON"}
00:00:06 MQT: stat/pzem/POWER = ON
00:00:07 MQT: domoticz/in = {"idx":118,"nvalue":1,"svalue":"","Battery":88,"RSSI":7}
00:00:14 MQT: tele/pzem/STATE = {"Time":"1970-01-01T00:00:14","Uptime":"0T00:00:14","Vcc":3.490,"SleepMode":"Dynamic","Sleep":0,"LoadAvg":29,"POWER":"ON","Wifi":{"AP":2,"SSId":"indebuurt2","BSSId":"00:22:6B:FE:8E:20","Channel":6,"RSSI":72}}
00:00:14 MQT: domoticz/in = {"idx":213,"nvalue":0,"svalue":"0;8964.0","Battery":88,"RSSI":7}
00:00:14 MQT: domoticz/in = {"idx":214,"nvalue":0,"svalue":"230.0","Battery":88,"RSSI":7}
00:00:14 MQT: domoticz/in = {"idx":215,"nvalue":0,"svalue":"0.000","Battery":88,"RSSI":7}
00:00:14 MQT: tele/pzem/SENSOR = {"Time":"1970-01-01T00:00:14","ENERGY":{"TotalStartTime":"2018-10-30T17:07:01","Total":8.964,"Yesterday":0.166,"Today":0.113,"Period":0.00,"Power":0.00,"ApparentPower":0.00,"ReactivePower":0.00,"Factor":0.00,"Voltage":230.0,"Current":0.000}}

Line 2 tells you it's using Hardware Serial.

[andrethomas]

@meingraham

The first image is hardware serial - The MHZ19 Co2 sensor has similar issues with software serial insofar that it loses connectivity or sync and stops giving data to Tasmota (or Tasmota stops receiving it)

Configuring as per your first image is hardware serial, but yes - you need to swap the wires around also to correct the direction of communication to the PZEM module.

[meingraham]

@arendst - I just restarted it and went straight to look at the web log. No SNS message.

00:00:00 Project sonoff Power Monitor HW-655 PZEM (Topic PZEM_PowerMonitor, Fallback DVES_231F92, GroupTopic sonoffs) Version 6.3.0.16(a516b25-sonoff)-2_4_2
00:00:04 WIF: Connecting to AP1 mySSID in mode 11N as PZEM_PowerMonitor-myDVES...
00:00:08 WIF: Connected
00:00:08 DNS: Initialized
00:00:08 HTP: Web server active on PZEM_PowerMonitor-myDVES.local with IP address 192.168.1.nnn
15:50:37 MQT: Attempting connection...
15:50:37 MQT: Connected
15:50:37 MQT: tele/PZEM_PowerMonitor/LWT = Online (retained)
15:50:37 MQT: cmnd/PZEM_PowerMonitor/POWER = 
15:50:37 MQT: tele/PZEM_PowerMonitor/INFO1 = {"Module":"Generic","Version":"6.3.0.16(a516b25-sonoff)","FallbackTopic":"DVES_231F92","GroupTopic":"sonoffs"}
15:50:37 MQT: tele/PZEM_PowerMonitor/INFO2 = {"WebServerMode":"Admin","Hostname":"PZEM_PowerMonitor-8082","IPAddress":"192.168.1.nnn"}
15:50:37 MQT: tele/PZEM_PowerMonitor/INFO3 = {"RestartReason":"Software/System restart"}
15:50:45 MQT: tele/PZEM_PowerMonitor/STATE = {"Time":"2019-01-21T15:50:45","Uptime":"0T00:00:18","Vcc":3.438,"SleepMode":"Dynamic","Sleep":25,"LoadAvg":39,"Wifi":{"AP":1,"SSId":"mySSID","BSSId":"myBSSId","Channel":1,"RSSI":54}}
15:50:45 MQT: tele/PZEM_PowerMonitor/SENSOR = {"Time":"2019-01-21T15:50:45","ENERGY":{"TotalStartTime":"2018-12-10T17:32:10","Total":23.483,"Yesterday":1.175,"Today":2.619,"Period":0.00,"Power":0.00,"ApparentPower":0.00,"ReactivePower":0.00,"Factor":0.00,"Voltage":122.00,"Current":0.000}}

@andrethomas OK - the first image is the update Theo is suggesting... but he recommended NOT swapping the cables.

[meingraham]

Swapped the configuration. Did not swap the cables. I got the SNS message.

00:00:00 SNS: Hardware Serial

Don't seem to be getting any data... which says I likely DO need to swap Rx/Tx. Unfortunately, this is going to require some surgery as I've hot glued stuff inside the circuit box to keep it all from coming loose. I think I'll go back to software serial for now and live with the Watchdog restart... until I get some time to open that box up.

I'll close this issue for now and re-open when I make some progress on the hardware change.

Mike

[andrethomas]

Theo is suggesting... but he recommended NOT swapping the cables

Could be I got that part wrong... it seemed logical that you would need to swap them but I did not study the code to confirm.

[meingraham]

it seemed logical that you would need to swap them but I did not study the code to confirm.

Did to me too. And my tests seems to confirm it.

[arendst]

Mike did the correct assumption (as I did) that cable swap was not needed. But this seems only the case for versions before 6.3.0.3. Sorry.

As Mike does not receive any data he will have to swap the cables indeed.