Constant rebooting of the unit

Support
1

I noticed yesterday that my unit continually reboots about every 30 seconds. I recently purchased and installed this unit about a month ago and didn’t have any issues until sometime recently. The update is set to “minor” and I am running version 02_07_05. I am not use any server uploaders. I am pulling data from Iotawatt into Home Assistant.

** Restart **

SD initialized.
1/25/22 13:06:55z Real Time Clock is running. Unix time 1643116015
1/25/22 13:06:55z Reset reason: Software Watchdog
1/25/22 13:06:55z Trace: 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[5], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[4], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[3], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[2], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 25:18, 25:19
1/25/22 13:06:55z ESP8266 ID: 430435, RTC M41T81 (68)
1/25/22 13:06:55z IoTaWatt 5.0, Firmware version 02_07_05
1/25/22 13:06:55z SPIFFS mounted.
1/25/22 08:06:55 Local time zone: -5:00, using DST/BST when in effect.
1/25/22 08:06:55 device name: IotaWatt
1/25/22 08:06:55 HTTP server started
1/25/22 08:06:55 timeSync: service started.
1/25/22 08:06:55 statService: started.
1/25/22 08:06:55 dataLog: service started.
1/25/22 08:06:55 dataLog: Last log entry 01/25/22 08:06:50
1/25/22 08:06:59 WiFi connected. SSID=wifi_ap, IP=192.168.1.36, channel=11, RSSI -66db
1/25/22 08:06:59 MDNS responder started for hostname IotaWatt
1/25/22 08:06:59 LLMNR responder started for hostname IotaWatt
1/25/22 08:06:59 Updater: service started. Auto-update class is MINOR
1/25/22 08:07:00 historyLog: service started.
1/25/22 08:07:00 historyLog: Last log entry 01/25/22 08:06:00
1/25/22 08:07:00 Updater: Auto-update is current for class MINOR.

** Restart **

SD initialized.
1/25/22 13:07:31z Real Time Clock is running. Unix time 1643116051
1/25/22 13:07:31z Reset reason: Software Watchdog
1/25/22 13:07:31z Trace: 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[5], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[4], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[3], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[2], 34:0, 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 25:18, 25:19
1/25/22 13:07:31z ESP8266 ID: 430435, RTC M41T81 (68)
1/25/22 13:07:31z IoTaWatt 5.0, Firmware version 02_07_05
1/25/22 13:07:31z SPIFFS mounted.
1/25/22 08:07:31 Local time zone: -5:00, using DST/BST when in effect.
1/25/22 08:07:31 device name: IotaWatt
1/25/22 08:07:31 HTTP server started
1/25/22 08:07:31 timeSync: service started.
1/25/22 08:07:31 statService: started.
1/25/22 08:07:31 dataLog: service started.
1/25/22 08:07:32 dataLog: Last log entry 01/25/22 08:07:25
1/25/22 08:07:35 WiFi connected. SSID=wifi_ap, IP=192.168.1.36, channel=11, RSSI -67db
1/25/22 08:07:35 MDNS responder started for hostname IotaWatt
1/25/22 08:07:35 LLMNR responder started for hostname IotaWatt
1/25/22 08:07:35 Updater: service started. Auto-update class is MINOR
1/25/22 08:07:36 historyLog: service started.
1/25/22 08:07:36 historyLog: Last log entry 01/25/22 08:07:00
1/25/22 08:07:36 Updater: Auto-update is current for class MINOR.

2

The trace indicates that it is hanging up while trying to read from the datalog during a query. That probably doesn’t help you much. From what you have said and what I see in the message log, the query is probably one of the queries sent by the home assistant integration. To prove that out, could you disable the IoTaWatt integration for a few minutes to see if the rebooting stops?

Could you also post your IoTaWatt status display with the Data Logs tab expanded.

Finally, could you use Graph+ to do a query of any input with a period of “last 12 months” and post if you get a result or if that causes the IoTaWatt to reboot?

3

HA integration is now disabled but reboots are still occurring.

Inputs/Outputs Status

Inputs Outputs
Input_0: 122.3 Volts

main_right: 1269 Watts, pf .92
main_left: 510 Watts, pf .87
Well_Pump: 0 Watts
HVAC_Condenser: 0 Watts
Septic: 0 Watts
Washer_Dryer: 6 Watts
Refridgerator: 125 Watts, pf .55
HVAC: 14 Watts
Server_2nd_Fridge: 442 Watts, pf .85
Ryan_Office: 313 Watts, pf .90
Microwave: 2 Watts
Garage: 13 Watts MainsConsumption: 1778.8 Watts

MainsExport: 0.0 Watts
Voltage: 122.3 Volts

IoTaWatt Statistics

Firmware version: 02_07_05

Running time: 0h 0m 21s
free Heap: 26040 644 samples per AC cycle

39.1 AC cycles sampled/second
60.0 Hz

WiFiData Logs

Current Log: 01/22/2022 18:56:05 - 01/25/2022 14:57:30 11.96 MB
History Log: 12/25/2021 21:35:00 - 01/25/2022 14:57:00 10.80 MB

iotawatt
iotawatt2039×1178 99.3 KB

iotawatt2
iotawatt2924×1165 92.7 KB

One additional data point, HA shows the last good communication was from January 23 at 10:31 pm

4

Just following up. I did disable the Iotawatt integration but I failed to restart the HA core which I believe I need to do. I had in the meantime just shutdown the HA VM just in case and because of that Iotawatt has been up for several minutes now. I believe there was an HA update that I applied around the 23rd that might be culprit.

5

Possibly, but I’m not aware of any updates to the HASS IoTaWatt integration recently.

Your current log appears to have been recreated a few days ago on January 22. I suspect that is related to this problem.

Did you delete it?

6

No, I haven’t deleted anything off the IoTa.

So IoTa ran for 8 hours yesterday with no reboots and HA integration turned off. I turned on the integration before bed and when I woke this morning I had 17 hours of uptime. I am not clear on what was occurring on the HA side but I had rebooted HA completely so maybe some process was running out of the control.

7

Thanks for the update. Even if it was precipitated by HASS, if you don’t mind, I’d like to follow up on a few loose ends to see if I can’t make IoTaWatt more bulletproof.

By all indications this is a datalog issue. If you didn’t delete it, it was probably found to be inconsistent while starting on January 22 around 6:56 pm. Can download /iotawatt/iotamsgs.txt and upload it into a PM to me so I can look into the sequence of events at that time.

Also, can you check to see if there is a file /iotawatt/logdiag.txt and if so, can you upload that file in the same pm please?