No data to emonPi emoncms since update to 02_02_26

[Jon (Jon Murphy)]

I think i broke it. I updated the IoTaWatt from 02_02_24 to 02_02_26 (alpha). And then about 10 minutes later the data flow stopped. Help?!?

** Restart **

No clock yet: SD initialized.
11/16/17 02:49:25 Real Time Clock is running. Unix time: 1510800565
11/16/17 02:49:25 Version: 02_02_24
11/16/17 02:49:25 Reset reason: Software/System restart
11/16/17 02:49:25 Trace: 14,17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,102,103
11/16/17 02:49:25 ESP8266 ChipID:451998
11/15/17 20:49:25 device name: IotaWatt, version: 3
11/15/17 20:49:25 Local time zone: -6
11/15/17 20:49:26 Updater: Update from 02_02_24 to 02_02_26
11/15/17 20:49:38 Updater: Update downloaded and signature verified
11/15/17 20:49:45 Updater: firmware upgraded to version 02_02_26
11/15/17 20:49:45 Firmware updated, restarting

** Restart **

No clock yet: SD initialized.
11/16/17 02:49:52 Real Time Clock is running. Unix time: 1510800592
11/16/17 02:49:52 Version: 02_02_26
11/16/17 02:49:52 Updater: Installing update files for version 02_02_26
11/16/17 02:49:52 Updater: Installing GRAPH.HTM
11/16/17 02:49:52 Updater: Installing GRAPH.JS
11/16/17 02:49:52 Updater: Installing INDEX.HTM
11/16/17 02:49:53 Updater: Installing TABLES.TXT
11/16/17 02:49:53 Updater: Installing CNFSTYLE.CSS
11/16/17 02:49:53 Updater: Installing EDIT.HTM
11/16/17 02:49:53 Updater: Installation complete.
11/16/17 02:49:53 Reset reason: Software/System restart
11/16/17 02:49:53 Trace: 130,131,132,133,134,135,136,137,138,139,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,102,103,14,17,18,13,14
11/16/17 02:49:53 ESP8266 ChipID:451998
11/15/17 20:49:54 device name: IotaWatt, version: 3
11/15/17 20:49:54 Local time zone: -6
11/15/17 20:49:54 MDNS responder started
11/15/17 20:49:54 You can now connect to http://IotaWatt.local
11/15/17 20:49:54 HTTP server started
11/15/17 20:49:54 dataLog: service started.
11/15/17 20:49:54 dataLog: Last log entry:1510800560
11/15/17 20:49:54 statService: started.
11/15/17 20:49:54 timeSync: service started.
11/15/17 20:49:55 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/15/17 20:49:55 historyLog: service started.
11/15/17 20:49:55 historyLog: first entry:1509570000
11/15/17 20:49:59 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/15/17 20:49:59 EmonService: Start posting from 1510800560
11/15/17 21:29:55 EmonService: Resending EmonCMS data:2
11/15/17 21:31:55 EmonService: Resending EmonCMS data:3
11/15/17 21:34:55 EmonService: Resending EmonCMS data:4
11/15/17 21:38:55 EmonService: Resending EmonCMS data:5
11/15/17 21:43:55 EmonService: Resending EmonCMS data:6
11/15/17 21:46:24 Restart command received.

** Restart **

No clock yet: SD initialized.
11/16/17 03:46:26 Real Time Clock is running. Unix time: 1510803986
11/16/17 03:46:26 Version: 02_02_26
11/16/17 03:46:26 Reset reason: Software/System restart
11/16/17 03:46:26 Trace: 17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,17,18,11,90,91,84,86,88,93,94,95,99,12,13,102,103
11/16/17 03:46:26 ESP8266 ChipID:451998
11/15/17 21:46:26 device name: IotaWatt, version: 3
11/15/17 21:46:26 Local time zone: -6
11/15/17 21:46:27 Updater: Update from 02_02_26 to 02_02_24
11/15/17 21:46:40 Updater: Update downloaded and signature verified
11/15/17 21:46:47 Updater: firmware upgraded to version 02_02_24
11/15/17 21:46:47 Firmware updated, restarting

** Restart **

No clock yet: SD initialized.
11/16/17 03:46:54 Real Time Clock is running. Unix time: 1510804014
11/16/17 03:46:54 Version: 02_02_24
11/16/17 03:46:54 Updater: Installing update files for version 02_02_24
11/16/17 03:46:54 Updater: Installing EDIT.HTM
11/16/17 03:46:54 Updater: Installing GRAPH~1.JS
11/16/17 03:46:54 Updater: Installing GRAPH.HTM
11/16/17 03:46:55 Updater: Installing INDEX.HTM
11/16/17 03:46:55 Updater: Installing TABLES.TXT
11/16/17 03:46:55 Updater: Installing CNFSTYLE.CSS
11/16/17 03:46:55 Updater: Installation complete.
11/16/17 03:46:56 Reset reason: Software/System restart
11/16/17 03:46:56 Trace: 130,131,132,133,134,135,136,137,138,139,90,91,84,86,88,93,94,95,99,12,13,102,103,17,18,13,14,17,18,13,14,17
11/16/17 03:46:56 ESP8266 ChipID:451998
11/15/17 21:46:56 device name: IotaWatt, version: 3
11/15/17 21:46:56 Local time zone: -6
11/15/17 21:46:57 MDNS responder started
11/15/17 21:46:57 You can now connect to http://IotaWatt.local
11/15/17 21:46:57 HTTP server started
11/15/17 21:46:57 dataLog: service started.
11/15/17 21:46:57 dataLog: Last log entry:1510803980
11/15/17 21:46:57 statService: started.
11/15/17 21:46:57 timeSync: service started.
11/15/17 21:46:57 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/15/17 21:47:02 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/15/17 21:47:02 EmonService: Start posting from 1510802870
11/15/17 21:48:07 EmonService: Resending EmonCMS data:2
11/15/17 21:50:07 EmonService: Resending EmonCMS data:3
11/15/17 21:53:07 EmonService: Resending EmonCMS data:4
11/15/17 21:57:07 EmonService: Resending EmonCMS data:5
11/15/17 22:02:07 EmonService: Resending EmonCMS data:6 

[overeasy (Inactive)]

@Jon

I think i broke it. I updated the IoTaWatt from 02_02_24 to 02_02_26 (alpha). And then about 10 minutes later the data flow stopped. Help?!?

OK, You decided to become an ALPHA, welcome to the messy world. This release is a development release that contains a huge change to the data log system. I’ve had mostly success with it, but it continues to burn in on four IoTaWatt here and a couple of others.

It looks like it started OK and ran for about 39 minutes before the Emonservice ran into problems sending to Emoncms. After about 15 minutes, it looks like you switched back to 02_02_24 and forced a restart. Interestingly, 02_02_24 has the same problem.

Can you restart it again and post the log from that?

UPDATE: I’ll look at it in the morning. From the trace, it looks like the IoTaWatt is sampling OK and should be recording to the datalog. So hopefully, when this is resolved, it will update the backlog.

Also, can you verify that the IP address of your EmonPi didn’t change?

[Jon (Jon Murphy)]

@overeasy

Can you restart it again and post the log from that?

It looks like it took care of itself! Excellent! After 10 tries the iotawatt reset. And then got back on track:

11/15/17 22:32:18 EmonService: Start posting from 1510802870
11/15/17 22:34:12 EmonService: GET failed. HTTP code:read Timeout
11/15/17 22:35:12 EmonService: Resending EmonCMS data:2
11/15/17 22:35:12 EmonService: Retry successful.

 

@overeasy

Also, can you verify that the IP address of your EmonPi didn’t change?

it is the same.
 

Here is the log:

** Restart **

No clock yet: SD initialized.
11/16/17 03:46:54 Real Time Clock is running. Unix time: 1510804014
11/16/17 03:46:54 Version: 02_02_24
11/16/17 03:46:54 Updater: Installing update files for version 02_02_24
11/16/17 03:46:54 Updater: Installing EDIT.HTM
11/16/17 03:46:54 Updater: Installing GRAPH~1.JS
11/16/17 03:46:54 Updater: Installing GRAPH.HTM
11/16/17 03:46:55 Updater: Installing INDEX.HTM
11/16/17 03:46:55 Updater: Installing TABLES.TXT
11/16/17 03:46:55 Updater: Installing CNFSTYLE.CSS
11/16/17 03:46:55 Updater: Installation complete.
11/16/17 03:46:56 Reset reason: Software/System restart
11/16/17 03:46:56 Trace: 130,131,132,133,134,135,136,137,138,139,90,91,84,86,88,93,94,95,99,12,13,102,103,17,18,13,14,17,18,13,14,17
11/16/17 03:46:56 ESP8266 ChipID:451998
11/15/17 21:46:56 device name: IotaWatt, version: 3
11/15/17 21:46:56 Local time zone: -6
11/15/17 21:46:57 MDNS responder started
11/15/17 21:46:57 You can now connect to http://IotaWatt.local
11/15/17 21:46:57 HTTP server started
11/15/17 21:46:57 dataLog: service started.
11/15/17 21:46:57 dataLog: Last log entry:1510803980
11/15/17 21:46:57 statService: started.
11/15/17 21:46:57 timeSync: service started.
11/15/17 21:46:57 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/15/17 21:47:02 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/15/17 21:47:02 EmonService: Start posting from 1510802870
11/15/17 21:48:07 EmonService: Resending EmonCMS data:2
11/15/17 21:50:07 EmonService: Resending EmonCMS data:3
11/15/17 21:53:07 EmonService: Resending EmonCMS data:4
11/15/17 21:57:07 EmonService: Resending EmonCMS data:5
11/15/17 22:02:07 EmonService: Resending EmonCMS data:6
11/15/17 22:08:07 EmonService: Resending EmonCMS data:7
11/15/17 22:15:07 EmonService: Resending EmonCMS data:8
11/15/17 22:23:07 EmonService: Resending EmonCMS data:9
11/15/17 22:32:07 EmonService: Resending EmonCMS data:10
11/15/17 22:32:07 EmonService: Unable to post to Emoncms after 10 retries.  Restarting ESP.

** Restart **

No clock yet: SD initialized.
11/16/17 04:32:07 Real Time Clock is running. Unix time: 1510806727
11/16/17 04:32:07 Version: 02_02_24
11/16/17 04:32:07 Reset reason: Software/System restart
11/16/17 04:32:07 Trace: 17,18,13,14,17,18,13,14,17,18,13,14,17,18,13,14,15,16,17,18,13,14,15,16,17,18,13,14,15,30,37,38
11/16/17 04:32:07 ESP8266 ChipID:451998
11/15/17 22:32:07 device name: IotaWatt, version: 3
11/15/17 22:32:07 Local time zone: -6
11/15/17 22:32:10 Connecting with WiFiManager.
11/15/17 22:32:13 MDNS responder started
11/15/17 22:32:13 You can now connect to http://IotaWatt.local
11/15/17 22:32:13 HTTP server started
11/15/17 22:32:13 dataLog: service started.
11/15/17 22:32:13 dataLog: Last log entry:1510806725
11/15/17 22:32:13 statService: started.
11/15/17 22:32:13 timeSync: service started.
11/15/17 22:32:13 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/15/17 22:32:18 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/15/17 22:32:18 EmonService: Start posting from 1510802870
11/15/17 22:34:12 EmonService: GET failed. HTTP code:read Timeout
11/15/17 22:35:12 EmonService: Resending EmonCMS data:2
11/15/17 22:35:12 EmonService: Retry successful.
11/16/17 01:32:13 checkUpdate: Invalid response from server.
11/16/17 04:32:13 checkUpdate: Invalid response from server.

[overeasy (Inactive)]

@Jon

It looks like it took care of itself! Excellent! After 10 tries the iotawatt reset. And then got back on track:

And uploaded all of the backlog?

It doesn’t appear that this is related to 02_02_26. If the data upload was seamless through that period, it appears to be a communication issue. I’d be interested in seeing what happens if you go back to ALPHA, and seeing the log after it starts, and then a screenshot of the status screen with the “Data Logs” tab expanded to show the coverage periods of the current and history logs.

[Jon (Jon Murphy)]

@overeasy

And uploaded all of the backlog?

On the emonPi side I grabbed the phpfina file and output to csv and found a few data points missing (not anything I am worried about):

 

@overeasy

I’d be interested in seeing what happens if you go back to ALPHA, and seeing the log after it starts

Will do!
 

@overeasy

and then a screenshot of the status screen with the “Data Logs” tab expanded to show the coverage periods of the current and history logs

I am not sure I know what this is… What does the Data Logs tab look like? And where are the History Logs located?

[Jon (Jon Murphy)]

Oops - just came across your recent post about Data Logs and History Logs!

New current and history logs

The current release of IoTaWatt has a capacity limitation of about 1.6 years of data that can be stored locally. This is governed by limitations in the Fat32 file system used in the internal SDcard. My home IoTaWatt has 10 months of data, so it was time to do something about that. The changes that are in test now will extend the datalog life to a maximum of about 15 years. I’ll explain and illustrate how it works. The original log remains in place, exactly as it was, but instead of just fil…

[overeasy (Inactive)]

@Jon

On the emonPi side I grabbed the phpfina file and output to csv and found a few data points missing (not anything I am worried about):

Those are the two restarts. There was a thirty second lapse in sampling for each. But that’s it, IoTaWatt landed on it’s feet and running. BTW/ easiest way I find to look for lapses is to just graph a day and turn on the “show missing data” button. Significant lapses are easy to spot.

@Jon

Oops - just came across your recent post about Data Logs and History Logs!

Yeah, I thought I’d get out ahead of that and explain what was coming. Took a couple of iterations but I think I got it right.

[Jon (Jon Murphy)]

@overeasy

I’d be interested in seeing what happens if you go back to ALPHA

I am back to ALPHA at Version: 02_02_26. All seems to be running A-OK this time. No communications issues.
 

@overeasy

and seeing the log after it starts

here is the log:

** Restart **

No clock yet: SD initialized.
11/16/17 23:09:26 Real Time Clock is running. Unix time: 1510873766
11/16/17 23:09:26 Version: 02_02_26
11/16/17 23:09:26 Updater: Installing update files for version 02_02_26
11/16/17 23:09:26 Updater: Installing GRAPH.HTM
11/16/17 23:09:26 Updater: Installing GRAPH.JS
11/16/17 23:09:26 Updater: Installing INDEX.HTM
11/16/17 23:09:27 Updater: Installing TABLES.TXT
11/16/17 23:09:27 Updater: Installing CNFSTYLE.CSS
11/16/17 23:09:27 Updater: Installing EDIT.HTM
11/16/17 23:09:27 Updater: Installation complete.
11/16/17 23:09:27 Reset reason: Software/System restart
11/16/17 23:09:27 Trace: 130,131,132,133,134,135,136,137,138,139,86,88,93,94,95,99,12,13,102,103,17,18,13,14,17,18,13,14,17,18,13,14
11/16/17 23:09:27 ESP8266 ChipID:451998
11/16/17 17:09:28 device name: IotaWatt, version: 3
11/16/17 17:09:28 Local time zone: -6
11/16/17 17:09:28 MDNS responder started
11/16/17 17:09:28 You can now connect to http://IotaWatt.local
11/16/17 17:09:28 HTTP server started
11/16/17 17:09:28 dataLog: service started.
11/16/17 17:09:28 dataLog: Last log entry:1510873730
11/16/17 17:09:28 statService: started.
11/16/17 17:09:28 timeSync: service started.
11/16/17 17:09:28 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/16/17 17:09:29 historyLog: service started.
11/16/17 17:09:29 historyLog: Last log entry:1510803960
11/16/17 17:09:33 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/16/17 17:09:33 EmonService: Start posting from 1510873720
11/16/17 18:00:00 timeSync: adjusting RTC by -2

 

@overeasy

and then a screenshot of the status screen with the “Data Logs” tab expanded to show the coverage periods of the current and history logs.

and a screenshot: