I think I may have a bad IoTaWatt

I received my IoTaWatt last Monday and the next day I connected it to wifi and set it up. I’m thrilled with the features and functionality of the IoTaWatt. My issue is that the unit keeps resetting at random times, sometimes losing all data. I’ve since configured influxdb and grafana, so I’m not losing history other than the gaps during which it seems to be offline.

I thought it might be a power issue because I realized that I used the power supply from a Raspberry PI instead of the one that came with it. Yesterday I swapped it out with the one in the box but it didn’t make a difference. The one I used at the beginning was a 5v 2A supply vs the 600mA supplied one so that shouldn’t have been it. It has reset since then, so I’m ruling out the power supply as the issue.

This is connected in my basement approximately 30 feet from the wifi access point. I noticed on some of the messages that the RSSI was as low as -79db, so I moved the unit a bit higher and also increased the power output on my access point. After that, the log reset messages indicated that the RSSI was -69db to -67db so I don’t think wifi connectivity is the issue.

Today, it went offline and was pingable but would not accept connections on port 80 at all – it would just respond with a TCP RST. It stayed that way for hours. I got home this evening and power cycled it and it has started working again for now. Before power cycling it, I noticed that the LED was blinking green, red, red.

My questions are:

Is there a console/uart port that I might be able to get more details from?

Is there a tool to help debug what the reset trace is telling me?

It seems like this is using the ESP8266 and I have several NodeMCU boards from other projects. I haven’t disassembled the IoTaWatt, but if there is a NodeMCU board inside, would it be possible to flash firmware onto one and swap it in as a troubleshooting step?

I’m very excited about the IoTaWatt and am willing to try anything to get this to be stable. Any help would be appreciated.



** Restart **

SD initialized.
10/06/19 05:58:44z Real Time Clock is running. Unix time 1570341524
10/06/19 05:58:44z Reset reason: Software Watchdog
10/06/19 05:58:44z Trace:  9:9, 1:2, 1:3, 1:4, 1:5[7], 7:0, 7:7, 7:7, 7:7, 7:7, 7:7, 7:7, 1:6, 1:1[1], 1:2[2], 9:0[2], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[7], 7:0, 7:7, 7:7
10/06/19 05:58:44z ESP8266 ChipID: 2526429
10/06/19 05:58:44z IoTaWatt 5.0, Firmware version 02_04_02
10/06/19 05:58:44z SPIFFS mounted.
10/06/19 05:58:45z Local time zone: +0:00
10/06/19 05:58:45z device name: IotaWatt
10/06/19 05:58:45z MDNS responder started for hostname IotaWatt
10/06/19 05:58:45z LLMNR responder started for hostname IotaWatt
10/06/19 05:58:45z HTTP server started
10/06/19 05:58:45z timeSync: service started.
10/06/19 05:58:45z statService: started.
10/06/19 05:58:45z Updater: service started. Auto-update class is MINOR
10/06/19 05:58:45z dataLog: service started.
10/06/19 05:58:45z IotaLog: file damaged iotawatt/iotalog.log

10/06/19 05:58:45z IotaLog: Creating diagnostic file.
10/06/19 05:58:49z IotaLog: Deleting iotawatt/iotalog.log and restarting.

** Restart **

SD initialized.
10/06/19 05:58:49z Real Time Clock is running. Unix time 1570341529
10/06/19 05:58:49z Reset reason: Software/System restart
10/06/19 05:58:49z Trace:  5:0, 5:4, 1:6, 1:1[6], 1:2[7], 9:0[7], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19], 1:6, 1:1[7], 1:2, 9:0, 9:0, 8:4, 8:6, 8:8, 8:9, 1:2, 1:3, 1:4, 1:5[19]
10/06/19 05:58:49z ESP8266 ChipID: 2526429
10/06/19 05:58:49z IoTaWatt 5.0, Firmware version 02_04_02
10/06/19 05:58:49z SPIFFS mounted.
10/06/19 05:58:50z Local time zone: +0:00
10/06/19 05:58:50z device name: IotaWatt
10/06/19 05:58:50z MDNS responder started for hostname IotaWatt
10/06/19 05:58:50z LLMNR responder started for hostname IotaWatt
10/06/19 05:58:50z HTTP server started
10/06/19 05:58:50z timeSync: service started.
10/06/19 05:58:50z statService: started.
10/06/19 05:58:50z dataLog: service started.
10/06/19 05:58:50z dataLog: New current log created.
10/06/19 05:58:50z dataLog: Last history entry: 10/06/19 05:57:00
10/06/19 05:58:54z WiFi connected. SSID=TheDivas, IP=, channel=11, RSSI -67db
10/06/19 05:58:54z Updater: service started. Auto-update class is MINOR
10/06/19 05:58:55z influxDB: started, url=, db=iotawatt, interval=10
10/06/19 05:58:55z Updater: Auto-update is current for class MINOR.
10/06/19 05:58:57z influxDB: Start posting at 10/06/19 05:57:50
10/06/19 05:59:50z historyLog: service started.
10/06/19 05:59:50z historyLog: Last log entry 10/06/19 05:57:00

Your IotaWatt is set to UTC time, so the times in the message log may not be your local time. In any event,
today at 5:58z, your system restarted because of a Software Watchdog while in the influxDB service. A second later a problem with the datalog was found. A diagnostic file was produced and the current log was deleted.

The unit restarted and a new current log was created. That was at 5:59z today. Looking at thetrouble shooting guide at docs.iotawatt.com the GRR led code means the SDcard was not working.

There were some issues with bad cards during this last manufacturing run, and it may be that your card is defective. If you are running now, it may be best to see what happens before acting on that.

If the unit continues to reset, there may be a problem associated with your influxDB configuration, but I think this is all SD related. Let’s see what happens now that the datalog has been rebuilt. (The history log should still have your previous data at 60 second intervals).

I appreciate your willingness to apply heroic measures to diagnosing and fixing these problems, but the IoTaWatt is typically very stable and has plenty of diagnostic and remedial features built in.

The software is completely open on Github, so if you want to understand the trace, you can familiarize yourself with the code and it will become obvious. Right now, these problems are straightforward and I think worst case will only require a new SDcard. What was your order number?

Thank you for the prompt response. That is great news that it may simply be the SD card. If this continues to reset I will replace the card and see if that fixes the issue.

I haven’t had a chance to dig into the software, but I will take a look at that when I get some time.

I don’t think it is the influxdb configuration because this started happening before I had influxdb configured. In fact, it was the loss of history that pushed me to set up influxdb so I could have an external record of the power/energy data.

Also, my order number was 66790.

Thanks again!


I just wanted to circle back to say that replacing the micro SD card 100% fixed the issue. My IoTaWatt has been rock solid for four days now, so I’m calling it fixed.