Failure after power outage - RESOLVED

Hello community,

I’ve had my unit for about a month working flawlessly, but we just had our first winter power outage (about 6 hours) and my IotaWatt has stopped working - it no longer exports data to Emoncms or can be accessed by a browser (yes tried several devices)

I’ve reset it a dozen times now and each time when first plugged in, I get the R-G-G code, then after a few minutes and then it switches to either dull red that pulses slightly, unless this is R-R-R. When in the R-G-G I can access the initial connection wizard, but once it restarts itself upon completion of setup, I am back to square one.

I’ve also reset my router and access point, without any changes.

Once out of the 12 resets, and waiting overnight I was able to get to the login screen (I have an admin user and password), but after entering the credentials nothing would progress.

Also a second time I managed to get into the main menu, (setup/tools/status) but clicking on the buttons did not progress anything.

After reading through the forums, I suspect the SDCARD has corrupted. I am willing to attempt to reset through the initial setup screen, but thought someone might want the log before I do this. Since I cannot access the file manager will need to remove the SDCARD. Any other suggestions before cracking it open?

Thanks

From what you describe, it’s not connecting to your WiFi. The message log would be helpful. As you have already determined, you would need to power the unit down, open it up and move the SD to another computer. The message log is /IoTaWatt/iotamsgs.txt. If you upload that, I will take a look.

Also, from what you describe, the unit is still monitoring and logging your power usage. So after copying the log file. You can replace it in the IoTaWatt and restart to keep logging until the access problem is resolved.

Hi overeasy,

Thanks for the prompt response.

Here are the last 3 resets. Seems like it doesn’t like it’s WIFI but pulled an IP?

** Restart **

SD initialized.
12/01/19 19:15:22z Real Time Clock is running. Unix time 1575227722
12/01/19 19:15:22z Reset reason: Software/System restart
12/01/19 19:15:22z Trace: 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1[5], 1:2[6], 9:0[6], 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[21], 21:0, 21:2
12/01/19 19:15:22z ESP8266 ChipID: 6147434
12/01/19 19:15:22z IoTaWatt 5.0, Firmware version 02_04_02
12/01/19 19:15:22z SPIFFS mounted.
12/01/19 15:15:23 Local time zone: -4:00
12/01/19 15:15:23 Using Daylight Saving Time (BST) when in effect.
12/01/19 15:15:23 device name: IotaWatt
12/01/19 15:15:23 MDNS responder started for hostname IotaWatt
12/01/19 15:15:23 LLMNR responder started for hostname IotaWatt
12/01/19 15:15:23 HTTP server started
12/01/19 15:15:23 timeSync: service started.
12/01/19 15:15:23 statService: started.
12/01/19 15:15:23 dataLog: service started.
12/01/19 15:15:23 dataLog: Last log entry 12/01/19 15:15:20
12/01/19 15:15:28 EmonService: started. url=172.25.3.225:80, node=IotaWatt, interval=10
12/01/19 15:16:23 historyLog: service started.
12/01/19 15:16:23 historyLog: Last log entry 12/01/19 15:15:00
12/01/19 15:16:23 PVoutput: started
12/01/19 16:15:24 WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
12/01/19 20:15:25z Real Time Clock is running. Unix time 1575231325
12/01/19 20:15:25z Reset reason: Software/System restart
12/01/19 20:15:25z Trace: 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1[4], 1:2[5], 9:0[5], 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[21], 21:0, 21:2
12/01/19 20:15:25z ESP8266 ChipID: 6147434
12/01/19 20:15:25z IoTaWatt 5.0, Firmware version 02_04_02
12/01/19 20:15:25z SPIFFS mounted.
12/01/19 16:15:26 Local time zone: -4:00
12/01/19 16:15:26 Using Daylight Saving Time (BST) when in effect.
12/01/19 16:15:26 device name: IotaWatt
12/01/19 16:15:26 MDNS responder started for hostname IotaWatt
12/01/19 16:15:26 LLMNR responder started for hostname IotaWatt
12/01/19 16:15:26 HTTP server started
12/01/19 16:15:26 timeSync: service started.
12/01/19 16:15:26 statService: started.
12/01/19 16:15:26 dataLog: service started.
12/01/19 16:15:26 dataLog: Last log entry 12/01/19 16:15:20
12/01/19 16:15:31 EmonService: started. url=172.25.3.225:80, node=IotaWatt, interval=10
12/01/19 16:16:26 historyLog: service started.
12/01/19 16:16:26 historyLog: Last log entry 12/01/19 16:15:00
12/01/19 16:16:26 PVoutput: started
12/01/19 16:29:14 WiFi connected. SSID=Jane, IP=172.25.3.122, channel=11, RSSI -74db
12/01/19 16:29:14 Updater: service started. Auto-update class is MINOR
12/01/19 16:29:14 PVoutput: System madcat, interval 5, freeload mode
12/01/19 16:29:14 PVoutput: Reload status beginning 11/14/19 00:05:00
12/01/19 16:29:16 Updater: Auto-update is current for class MINOR.
12/01/19 16:32:42 EmonService: get input list failing, code: -4
12/01/19 17:15:11 WiFi disconnected.
12/01/19 18:15:11 WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
12/01/19 22:15:12z Real Time Clock is running. Unix time 1575238512
12/01/19 22:15:12z Reset reason: Software/System restart
12/01/19 22:15:12z Trace: 1:2, 9:0, 9:0, 8:4, 8:6, 8:8, 8:9, 1:2, 1:3, 1:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:3, 1:6, 1:3, 1:4, 1:5[5], 5:0, 1:6, 1:3, 1:4, 1:5[21], 21:0, 21:2
12/01/19 22:15:12z ESP8266 ChipID: 6147434
12/01/19 22:15:12z IoTaWatt 5.0, Firmware version 02_04_02
12/01/19 22:15:12z SPIFFS mounted.
12/01/19 18:15:13 Local time zone: -4:00
12/01/19 18:15:13 Using Daylight Saving Time (BST) when in effect.
12/01/19 18:15:13 device name: IotaWatt
12/01/19 18:15:13 MDNS responder started for hostname IotaWatt
12/01/19 18:15:13 LLMNR responder started for hostname IotaWatt
12/01/19 18:15:13 HTTP server started
12/01/19 18:15:13 timeSync: service started.
12/01/19 18:15:13 statService: started.
12/01/19 18:15:13 dataLog: service started.
12/01/19 18:15:13 dataLog: Last log entry 12/01/19 18:15:10
12/01/19 18:15:18 EmonService: started. url=172.25.3.225:80, node=IotaWatt, interval=10
12/01/19 18:16:13 historyLog: service started.
12/01/19 18:16:13 historyLog: Last log entry 12/01/19 18:15:00
12/01/19 18:16:13 PVoutput: started

Sorry, that’s EmonCMS IP I am seeing in the log. Is the time set from the internet?

I’d like to see the whole message log for a larger context. Can you upload the whole file please?

There are definitely problems with the WiFi. During the second run, there was a connection, but nothing was accomplished and it disconnected after 45 minutes.

Yes, at some point it was set, but there is a battery RTC so it could have been days or weeks ago.

Has anything changed with yourWiFi?

IOTAMSGS.TXT (447.2 KB)

Good morning,

Here is the complete MSG text file.

Not included in this file though, is after pulling the file, I created a new 2.4GHz network and connected the IotaWatt to it. Same result.

OK, There’s a lot going on there.

It looks as if the power failure you refer to happened on 11/28 at about 4:25pm and came back on about 11:54. Then it came on for about 6 minutes and went out again for about 4 minutes.

When it came back on, the IoTaWatt came up before the WiFi router, and subsequently did not connect when the router came up. This happens sometimes. The IoTaWatt restarted about an hour later in an attempt to reacquire WiFi connection, which worked. This is where you start to see problems, but I’m not so sure everything was working OK before…

I’d like to simplify what’s going on in an effort to isolate the cause of the heap degradation:

I’ve looked at your PVoutput account and it appears it was working fine up until the power failure, yet you have it configured to reload history from 11/14 every time it starts up. The “upload history from” date must be cleared once the history is uploaded. That should be removed, and in fact I’d like to see the PVoutput service stopped if possible from the status display.

Your Emoncms also appears to be have had issues. I’d like to stop that as well.

Finally, it looks as though you might have set a password in the IoTaWatt. I’d like to remove that for now as well.

If you can’t get access to do these things, you can remove the SDcard and send me the /config/txt file via PM. I’ll stop the PVoutput and Emoncms and send the file back.

To remove the passwords, delete the file /iotawatt/auth.txt

I’ll also take a close look at the rest of the config.

Once these things are done, hopefully the unit will run stable, and we can start the services back up one at a time.

Hi overeasy,

I deleted the auth.txt and started back my unit up but there was no change.

I’ve replaced the config file you sent me, but so far it does the same. R-G-G followed by dull red. I’ll leave it on overnight and report back in the morning.

When you see RGG after startup, that means it’s not connecting to WiFi. The dull red means it’s monitoring and logging but not connected to WiFi. Have you tried looking for the AP SSID and specifying your WiFi credentials again to connect? You say you installed a new router, this could be as simple as not connecting to that router.

Good morning overeasy,

My wireless setup uses Ubiquiti gear so my router and access point are separate components. I created a new wireless network (Jane2 in the log) that was strictly 2.4GHz and had nothing except the IotaWatt on it as a diagnostic step - nothing changed.

The access point does see the IotaWatt and records its uptime, but the IotaWatt doesnt seem to pick up its IP. According to the access point it with a couple of minutes of uptime, 8KB of data went up, but 0KB down. It was on channel 11. Signal was only 50% though, even though it is only about 20 feet away from the AP with 1 drywall wall and a wood door in between.

I’ve uploaded the most recent MSG log. To my novice eye, the EMONCMS is gone, but the PVOUTPUT service is still starting.

IOTAMSGS.TXT (447.2 KB)

Oops. The log:

The IoTaWatt is not connecting, or disconnecting right away when it does. One significant difference is that prior to the power failure, it was on channel 6, and since it has been channel 11. Why is that?

Hi overeasy,

My best guess for the difference between channel 6 & 11, is that my access point automatically chooses the best channel. I have now manually set it to run on channel 6, rebooted the IotaWatt & let it sit with the dull red for a few hours and still no connection.

I have a spare wireless N router/access point at work which I’ll bring home with me tomorrow night to try.

If it doesn’t connect after an hour, it probably won’t. But you never answered my question

You would need to power cycle and look for the AP right after startup while it’s still RGG.

Overeasy,

Sorry. Yes I did retry network credentials.

Good morning overeasy,

I’ve set up a second router and all of my wifi troubles have disappeared. I’m not sure what happened to my WiFi during the power outage?! Ill clear and reload my entire system over the weekend.
At any rate, you mentioned according to the log there was trouble before my power outage. I’ve only restarted the EmonCMS webserver and everything has been stable for 12 hours. What in particular am I looking for in the message log?

After the power failure, Emoncms service starts with:

11/28/19 22:08:34 EmonService: Start posting at 11/13/19 18:09:35

Yet before the power failure, it started with:

11/18/19 19:37:30 EmonService: Start posting at 11/18/19 19:37

So something happened to your Emoncms to regress the input dates. It’s impossible to tell when this happened, or if it’s related to the WiFi issue. It could well be something that you were doing with Emoncms during that 10 day window.