New IotaWatt install, worked fine for first 24 hours, now can't get to web interface/unit flashing green

Support
1

Hey all,

Purchased an IotaWatt a few months ago and finally got around to installing it. I installed the CT’s, did initial connection to wifi yesterday, configured a few things and everything was working well.

Today I was testing a few circuits in the house (just plugging a heater in) to make sure my CT’s were properly picking up each circuit. Lost connection to the web interface all of a sudden, so I went to the unit and it was flashing green. Restarted a couple of times but still couldn’t get to the interface. Had not yet had a chance to set a static IP on the unit, but checked out my router, confirmed IP and hostname. Getting timeouts and destination host unreachable when trying to get to the interface.

I searched and found a couple of references to the LED flashing, but this didn’t seem to be my issue. In any case, pulling the SD card to poke around seemed to be the best option. I didn’t see anything odd in the config file (namely the “server” tag referenced in some of the other threads)

Log file shows that my unit updated to 02_06_02 yesterday, looked to have been successful. Only thing odd in the last few entries that I see is the hardware watchdog. Please let me know if any thoughts, thanks:

** Restart **

SD initialized.
7/23/21 15:38:51z Real Time Clock is running. Unix time 1627054731
7/23/21 15:38:51z Reset reason: Hardware Watchdog
7/23/21 15:38:51z Trace: 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3
7/23/21 15:38:51z ESP8266 ChipID: 12672349
7/23/21 15:38:51z IoTaWatt 5.0, Firmware version 02_06_02
7/23/21 15:38:51z SPIFFS mounted.
7/23/21 11:38:51 Local time zone: -5:00
7/23/21 11:38:51 Using Daylight Saving Time (BST) when in effect.
7/23/21 11:38:51 device name: IotaWatt
7/23/21 11:38:51 HTTP server started
7/23/21 11:38:51 timeSync: service started.
7/23/21 11:38:51 statService: started.
7/23/21 11:38:51 dataLog: service started.
7/23/21 11:38:51 dataLog: Last log entry 07/23/21 11:38:40
7/23/21 11:38:55 WiFi connected. SSID=mynetwork, IP=192.168.125.117, channel=11, RSSI -57db
7/23/21 11:38:55 MDNS responder started for hostname IotaWatt
7/23/21 11:38:55 LLMNR responder started for hostname IotaWatt
7/23/21 11:38:55 Updater: service started. Auto-update class is MINOR
7/23/21 11:38:56 historyLog: service started.
7/23/21 11:38:56 historyLog: Last log entry 07/23/21 11:38:00
7/23/21 11:38:56 Updater: Auto-update is current for class MINOR.

** Restart **

SD initialized.
7/23/21 17:02:49z Real Time Clock is running. Unix time 1627059769
7/23/21 17:02:49z Power failure detected.
7/23/21 17:02:49z Reset reason: External System
7/23/21 17:02:49z ESP8266 ChipID: 12672349
7/23/21 17:02:49z IoTaWatt 5.0, Firmware version 02_06_02
7/23/21 17:02:49z SPIFFS mounted.
7/23/21 13:02:49 Local time zone: -5:00
7/23/21 13:02:49 Using Daylight Saving Time (BST) when in effect.
7/23/21 13:02:49 device name: IotaWatt
7/23/21 13:02:52 HTTP server started
7/23/21 13:02:52 WiFi connected. SSID=mynetwork, IP=192.168.125.117, channel=11, RSSI -60db
7/23/21 13:02:52 MDNS responder started for hostname IotaWatt
7/23/21 13:02:52 LLMNR responder started for hostname IotaWatt
7/23/21 13:02:52 timeSync: service started.
7/23/21 13:02:52 statService: started.
7/23/21 13:02:52 Updater: service started. Auto-update class is MINOR
7/23/21 13:02:52 dataLog: service started.
7/23/21 13:02:52 dataLog: Last log entry 07/23/21 13:02:40
7/23/21 13:02:53 Updater: Auto-update is current for class MINOR.
7/23/21 13:02:57 historyLog: service started.
7/23/21 13:02:57 historyLog: Last log entry 07/23/21 13:02:00

** Restart **

SD initialized.
7/23/21 17:07:51z Real Time Clock is running. Unix time 1627060071
7/23/21 17:07:51z Power failure detected.
7/23/21 17:07:51z Reset reason: External System
7/23/21 17:07:51z ESP8266 ChipID: 12672349
7/23/21 17:07:51z IoTaWatt 5.0, Firmware version 02_06_02
7/23/21 17:07:51z SPIFFS mounted.
7/23/21 13:07:51 Local time zone: -5:00
7/23/21 13:07:51 Using Daylight Saving Time (BST) when in effect.
7/23/21 13:07:51 device name: IotaWatt
7/23/21 13:07:54 HTTP server started
7/23/21 13:07:54 WiFi connected. SSID=mynetwork, IP=192.168.125.117, channel=11, RSSI -56db
7/23/21 13:07:54 MDNS responder started for hostname IotaWatt
7/23/21 13:07:54 LLMNR responder started for hostname IotaWatt
7/23/21 13:07:54 timeSync: service started.
7/23/21 13:07:54 statService: started.
7/23/21 13:07:54 Updater: service started. Auto-update class is MINOR
7/23/21 13:07:54 dataLog: service started.
7/23/21 13:07:55 dataLog: Last log entry 07/23/21 13:07:30
7/23/21 13:07:55 Updater: Auto-update is current for class MINOR.
7/23/21 13:07:59 historyLog: service started.
7/23/21 13:07:59 historyLog: Last log entry 07/23/21 13:07:00

** Restart **

SD initialized.
7/23/21 17:15:50z Real Time Clock is running. Unix time 1627060550
7/23/21 17:15:50z Power failure detected.
7/23/21 17:15:50z Reset reason: External System
7/23/21 17:15:50z ESP8266 ChipID: 12672349
7/23/21 17:15:50z IoTaWatt 5.0, Firmware version 02_06_02
7/23/21 17:15:50z SPIFFS mounted.
7/23/21 13:15:50 Local time zone: -5:00
7/23/21 13:15:50 Using Daylight Saving Time (BST) when in effect.
7/23/21 13:15:50 device name: IotaWatt
7/23/21 13:15:53 HTTP server started
7/23/21 13:15:53 WiFi connected. SSID=mynetwork, IP=192.168.125.117, channel=11, RSSI -70db
7/23/21 13:15:53 MDNS responder started for hostname IotaWatt
7/23/21 13:15:53 LLMNR responder started for hostname IotaWatt
7/23/21 13:15:53 timeSync: service started.
7/23/21 13:15:53 statService: started.
7/23/21 13:15:53 Updater: service started. Auto-update class is MINOR
7/23/21 13:15:53 dataLog: service started.
7/23/21 13:15:53 dataLog: Last log entry 07/23/21 13:15:40
7/23/21 13:15:54 Updater: Auto-update is current for class MINOR.
7/23/21 13:15:58 historyLog: service started.
7/23/21 13:15:58 historyLog: Last log entry 07/23/21 13:15:00

2

Okay, just inserted SD card and powered unit back on and all seems fine now…weird. Nothing looks different in most recent log (below). Light is still kinda flashing fast green as opposed to being solid.

Will write back if more issues…

SD initialized.
7/23/21 17:52:19z Real Time Clock is running. Unix time 1627062739
7/23/21 17:52:19z Power failure detected.
7/23/21 17:52:19z Reset reason: External System
7/23/21 17:52:19z ESP8266 ChipID: 12672349
7/23/21 17:52:19z IoTaWatt 5.0, Firmware version 02_06_02
7/23/21 17:52:19z SPIFFS mounted.
7/23/21 13:52:19 Local time zone: -5:00
7/23/21 13:52:19 Using Daylight Saving Time (BST) when in effect.
7/23/21 13:52:19 device name: IotaWatt
7/23/21 13:52:22 Connecting with WiFiManager.
7/23/21 13:52:25 HTTP server started
7/23/21 13:52:25 WiFi connected. SSID=mynetwork, IP=192.168.125.117, channel=11, RSSI -76db
7/23/21 13:52:25 MDNS responder started for hostname IotaWatt
7/23/21 13:52:25 LLMNR responder started for hostname IotaWatt
7/23/21 13:52:25 timeSync: service started.
7/23/21 13:52:25 statService: started.
7/23/21 13:52:25 Updater: service started. Auto-update class is MINOR
7/23/21 13:52:26 dataLog: service started.
7/23/21 13:52:26 dataLog: Last log entry 07/23/21 13:19:45
7/23/21 13:52:27 Updater: Auto-update is current for class MINOR.
7/23/21 13:52:30 historyLog: service started.
7/23/21 13:52:30 historyLog: Last log entry 07/23/21 13:19:00

3

In all four of the restarts included in the above logs, the IoTaWatt did successfully connect to WiFi. It also verified that your release is current by connecting with the IoTaWatt server. So you were connected to WiFi, and it successfully accessed the internet. All that indicates that the unit was working OK.

All of the restarts show that the datalog was being updated right up to the time of each restart, indicating that the SDcard was working fine.

4

Thanks for the quick reply, maybe my network acting up then, converted the DHCP to a static lease going forward so we’ll see how it goes. Appreciate it!

5

I think I have the same problem. I have tried re-seating the SD card but it made no difference to me. As far as I can tell everything keeps working except the web interface is inaccessible. Last two logs:

** Restart **

SD initialized.
9/13/21 11:51:50z Real Time Clock is running. Unix time 1631533910 
9/13/21 11:51:50z Power failure detected.
9/13/21 11:51:50z Reset reason: External System
9/13/21 11:51:50z ESP8266 ChipID: 13632022
9/13/21 11:51:50z IoTaWatt 5.0, Firmware version 02_06_05
9/13/21 11:51:50z SPIFFS mounted.
9/13/21 21:51:50 Local time zone: +10:00
9/13/21 21:51:50 device name: IotaWatt
9/13/21 21:51:53 Connecting with WiFiManager.
9/13/21 21:51:58 HTTP server started
9/13/21 21:51:58 WiFi connected. SSID=wlan-ap-2.4g, IP=192.168.1.233, channel=6, RSSI -44db
9/13/21 21:51:58 MDNS responder started for hostname IotaWatt
9/13/21 21:51:58 LLMNR responder started for hostname IotaWatt
9/13/21 21:51:58 timeSync: service started.
9/13/21 21:51:59 statService: started.
9/13/21 21:51:59 Updater: service started. Auto-update class is MINOR
9/13/21 21:51:59 dataLog: service started.
9/13/21 21:51:59 dataLog: Last log entry 09/13/21 21:44:30
9/13/21 21:52:03 Updater: Auto-update is current for class MINOR.
9/13/21 21:52:04 historyLog: service started.
9/13/21 21:52:04 historyLog: Last log entry 09/13/21 21:44:00

** Restart **

SD initialized.
9/13/21 13:01:06z Real Time Clock is running. Unix time 1631538066 
9/13/21 13:01:06z Power failure detected.
9/13/21 13:01:06z Reset reason: External System
9/13/21 13:01:06z ESP8266 ChipID: 13632022
9/13/21 13:01:06z IoTaWatt 5.0, Firmware version 02_06_05
9/13/21 13:01:06z SPIFFS mounted.
9/13/21 23:01:06 Local time zone: +10:00
9/13/21 23:01:06 device name: IotaWatt
9/13/21 23:01:09 Connecting with WiFiManager.
9/13/21 23:01:14 HTTP server started
9/13/21 23:01:15 WiFi connected. SSID=wlan-ap-2.4g, IP=192.168.1.233, channel=6, RSSI -44db
9/13/21 23:01:15 MDNS responder started for hostname IotaWatt
9/13/21 23:01:15 LLMNR responder started for hostname IotaWatt
9/13/21 23:01:15 timeSync: service started.
9/13/21 23:01:15 statService: started.
9/13/21 23:01:15 Updater: service started. Auto-update class is MINOR
9/13/21 23:01:15 dataLog: service started.
9/13/21 23:01:15 dataLog: Last log entry 09/13/21 23:01:00
9/13/21 23:01:16 Updater: Auto-update is current for class MINOR.
9/13/21 23:01:20 historyLog: service started.
9/13/21 23:01:20 historyLog: Last log entry 09/13/21 23:01:00

Status page:
https://imgur.com/a/X6lQcRW

Any ideas?
6

As it appears to have turned out, that wasn’t actually a problem with the IoTaWatt. It had been working properly. Apparently it is resolved. I suspect a WiFi issue.

PLEASE, PEOPLE, STOP REMOVING YOUR SDCARD. There is no indication of an SDcard problem here. More cards are broken or otherwise damaged by unnecessary removal than by any natural cause. DONT OPEN UP THE UNIT, unless instructed to do so.

If your LED is solid or dull green, there is no problem with the IoTaWatt. The log shows it is sampling and logging just fine.

Have you tried using a different browser device? Is yopur browser on the same WiFi network? Have you tried accessing using the IP address?

7

Hah good advice (with respect to the SD card), in my case I did a fairly good dive to try and solve the problem, tried by IP, different browsers, checked DNS at different levels, etc. before opening it up to check logs.

I think the best advice when first setting up the device is to set a static IP, or static lease ASAP. Other than that, turning the power off for a while (like 15-30 minutes) and then back on seemed to help in my case (give router a chance to discombobulate a little or something…). No issues with connectivity that I’ve seen since doing that and setting a static lease

8

WiFi is a black art. Unfortunately I’m at the mercy of the TCP stack that comes with the ESP8266. Most of the time it works great, but it seems there is some equipment that it doesn’t get along with very well. I had my own saga until I switched to Ubiquiti APs.

9

No it is flashing very fast green. Everything else seems to be working fine except for the web interface. I am not ruling out a network issue as I am using a older modem as the WAP in the garage. Having said that I did have nine out of ten CTs backwards (as I stopped reading the instructions at “Connecting the CTs” instead of also reading “CT Basics”) and I have just flipped them all around and seems better so maybe something was going on there? Edit: Still happening but did come back up again without me doing anything.

I can add one more thing. When it has started to fail sometimes the screen would appear in just black and white but I could see the words “configuration not found.” In fact I was just about to post and this happened: Configuration not found

10

That is the dull green. It’s a red herring.

Another red-herring. Reversing the CTs will not cause any problems like you are describing.

That’s poor WiFi. It tries top load the config app and doesn’t get part of it. It also needs to load the config, which it doesn’t seem able to do.

Your RSSI is very good, so maybe it’s interference from something else. You might try changing the WiFi channel, or better yet connecting to a different WiFi network if one is available.

11

Thanks. Yes the IotaWatt is only 30cm from the WAP. I will see if I can find another one in my box of bits and swap it out and see what happens. Will report back when I can…

12

Maybe move it away a bit?

13

Thanks I have replaced what I was using with a cheap WAP and all seems to be well . Sometimes the loading is a bit slow but haven’t had any timeouts and I’m not seeing any errors in the HA logs about being unable to connect.
Thanks for the support!

1 Like