Sorting out an Australian three-phase installation

Support
1

So. Finally got the iotawatt up and configured nicely.

I have noticed that it crashes after a few hours running. I can power cycle it and it comes back but only for 5-10 minutes before freezing again.

I have changed the USB power supply.

Its about 8 degrees celsius outside so I don’t think its heat.

It is monitoring on 14 inputs + the 5v AC

Any ideas on next steps for troubleshooting?

Logs below:
8/1/18 02:39:45 historyLog: service started.
8/1/18 02:39:45 historyLog: Last log entry:1532991720
8/1/18 02:42:24 Restart command received.

** Restart **

No clock yet: SD initialized.
8/1/18 02:42:26 Real Time Clock is running. Unix time: 1533091346
8/1/18 02:42:26 Version: 02_02_30
8/1/18 02:42:26 Reset reason: Software/System restart
8/1/18 02:42:26 Trace: 13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,14,13,108
8/1/18 02:42:26 ESP8266 ChipID:6910347
8/1/18 12:42:26 device name: Lilliput, version: 3
8/1/18 12:42:26 Local time zone: 10
8/1/18 12:42:29 Updater: Update from 02_02_30 to 02_03_10
8/1/18 12:43:09 Updater: Update downloaded and signature verified
8/1/18 12:43:15 Updater: firmware upgraded to version 02_03_10
8/1/18 12:43:15 Firmware updated, restarting

** Restart **

SD initialized.
8/01/18 02:43:21z Real Time Clock is running. Unix time 1533091401 
8/01/18 02:43:21z Version 02_03_10
8/01/18 02:43:21z Updater: Installing update files for version 02_03_10
8/01/18 02:43:21z Updater: Installing GRAPH.JS
8/01/18 02:43:21z Updater: Installing INDEX.HTM
8/01/18 02:43:23z Updater: Installing TABLES.TXT
8/01/18 02:43:23z Updater: Installing CNFSTYLE.CSS
8/01/18 02:43:23z Updater: Installing EDIT.HTM
8/01/18 02:43:23z Updater: Installing GRAPH.HTM
8/01/18 02:43:23z Updater: Installation complete.
8/01/18 02:43:24z Reset reason: Software/System restart
8/01/18 02:43:24z Trace:  0:34, 0:35, 0:36, 0:37, 0:38, 0:39, 0:40, 0:41, 0:42, 0:43, 0:44, 0:45, 0:46, 0:47, 0:48, 0:49, 0:50, 0:51, 0:52, 0:53, 0:54, 0:55, 0:56, 0:57, 0:58, 0:59, 0:60, 0:61, 0:62, 0:63, 0:64, 0:65
8/01/18 02:43:24z ESP8266 ChipID: 6910347
8/01/18 12:43:24 Local time zone: 10
8/01/18 12:43:24 device name: Lilliput, version: 3
8/01/18 12:43:24 MDNS responder started
8/01/18 12:43:24 You can now connect to http://Lilliput.local
8/01/18 12:43:24 HTTP server started
8/01/18 12:43:24 dataLog: service started.
8/01/18 12:43:24 dataLog: Last log entry 8/1/18 12:42:20 
8/01/18 12:43:25 statService: started.
8/01/18 12:43:25 timeSync: service started.
8/01/18 12:43:25 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 12:43:25 Updater: service started. Auto-update class is MINOR
8/01/18 12:43:25 historyLog: service started.
8/01/18 12:43:25 historyLog: Last log entry 8/1/18 12:42:00 
8/01/18 12:43:27 Updater: Auto-update is current for class MINOR.
8/01/18 13:05:36 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:05:38 EmonService: Node doesn't yet exist.
8/01/18 13:05:38 EmonService: Start posting at 8/1/18 13:05:45 
8/01/18 13:05:38 EmonService: Stopped.  Last post 8/1/18 13:05:35 
8/01/18 13:07:38 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:07:40 EmonService: Node doesn't yet exist.
8/01/18 13:07:40 EmonService: Start posting at 8/1/18 13:07:50 
8/01/18 13:35:10 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET

** Restart **

SD initialized.
8/01/18 03:35:11z Real Time Clock is running. Unix time 1533094511 
8/01/18 03:35:11z Version 02_03_10
8/01/18 03:35:11z Reset reason: Exception
8/01/18 03:35:11z Trace:  16:2, 16:3, 16:4, 16:5, 16:7, 11:8, 11:9, 1:4, 1:5[3], 3:0, 3:1, 3:2, 1:6, 1:1[5], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:4, 9:5, 9:9, 1:2, 1:2[6], 1:3, 1:4, 1:5[3], 3:0, 3:3, 3:3, 3:3
8/01/18 03:35:11z ESP8266 ChipID: 6910347
8/01/18 13:35:11 Local time zone: 10
8/01/18 13:35:11 device name: Lilliput, version: 3
8/01/18 13:35:11 MDNS responder started
8/01/18 13:35:11 You can now connect to http://Lilliput.local
8/01/18 13:35:11 HTTP server started
8/01/18 13:35:11 dataLog: service started.
8/01/18 13:35:11 dataLog: Last log entry 8/1/18 13:35:10 
8/01/18 13:35:11 statService: started.
8/01/18 13:35:11 timeSync: service started.
8/01/18 13:35:11 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:35:11 Updater: service started. Auto-update class is MINOR
8/01/18 13:35:11 historyLog: service started.
8/01/18 13:35:11 historyLog: Last log entry 8/1/18 13:35:00 
8/01/18 13:35:13 Updater: Auto-update is current for class MINOR.
8/01/18 13:35:16 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:35:17 EmonService: Start posting at 8/1/18 13:35:20 

** Restart **

SD initialized.
8/01/18 03:46:54z Real Time Clock is running. Unix time 1533095214 
8/01/18 03:46:54z Power failure detected.
8/01/18 03:46:54z Version 02_03_10
8/01/18 03:46:54z Reset reason: External System
8/01/18 03:46:54z Trace:  246:99[123], 181:229[184], 116:120[74], 71:99[21], 167:42[108], 94:120[177], 107:98[51], 170:4[25], 28:79[13], 9:144[226], 5:133[201], 60:49[57], 216:112[54], 6:22[89], 180:159[36], 251:238[50], 240:101[38], 133:124[113], 137:33[69], 31:22[179], 98:178[176], 18:15[144], 56:
** Restart **

SD initialized.
8/01/18 03:47:16z Real Time Clock is running. Unix time 1533095236 
8/01/18 03:47:16z Power failure detected.
8/01/18 03:47:16z Version 02_03_10
8/01/18 03:47:16z Reset reason: External System
8/01/18 03:47:16z Trace:  246:103[91], 181:229[186], 116:104[74], 67:115[21], 165:42[108], 86:112[177], 107:98[53], 170:20[25], 60:111[15], 9:144[242], 5:133[193], 52:49[57], 216:112[54], 6:22[89], 180:223[36], 251:238[50], 240:5[38], 197:252[121], 137:1[69], 25:22[179], 242:146[176], 86:15[144], 58:206[29], 30:235[247], 236:76[224], 52:63[151], 171:202[248], 225:57[47], 132:109[184], 74:168[174], 90:95[61], 87:172[215]
8/01/18 03:47:16z ESP8266 ChipID: 6910347
8/01/18 13:47:16 Local time zone: 10
8/01/18 13:47:16 device name: Lilliput, version: 3
8/01/18 13:47:19 MDNS responder started
8/01/18 13:47:19 You can now connect to http://Lilliput.local
8/01/18 13:47:19 HTTP server started
8/01/18 13:47:19 dataLog: service started.
8/01/18 13:47:19 dataLog: Last log entry 8/1/18 13:46:50 
8/01/18 13:47:19 statService: started.
8/01/18 13:47:19 timeSync: service started.
8/01/18 13:47:19 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:47:20 Updater: service started. Auto-update class is MINOR
8/01/18 13:47:20 historyLog: service started.
8/01/18 13:47:20 historyLog: Last log entry 8/1/18 13:46:00 
8/01/18 13:47:22 Updater: Auto-update is current for class MINOR.
8/01/18 13:47:24 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:47:25 EmonService: Start posting at 8/1/18 13:47:00 
8/01/18 13:48:28 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:48:33 EmonService: Start posting at 8/1/18 13:48:30 
8/01/18 17:10:24 timeSync: adjusting RTC by -3
8/01/18 18:10:27 timeSync: adjusting RTC by 3

** Restart **

SD initialized.
8/01/18 09:41:26z Real Time Clock is running. Unix time 1533116486 
8/01/18 09:41:26z Power failure detected.
8/01/18 09:41:26z Version 02_03_10
8/01/18 09:41:26z Reset reason: External System
8/01/18 09:41:26z Trace:  246:99[123], 181:229[186], 116:120[72], 71:99[85], 165:58[76], 22:120[241], 107:98[57], 170:20[25], 61:79[15], 9:144[226], 5:133[201], 52:53[57], 216:112[54], 6:23[89], 180:223[36], 251:238[34], 240:37[38], 213:252[49], 137:137[69], 29:22[179], 114:178[176], 86:15[144], 56:239[29], 30:99[247], 204:100[224], 52:63[151], 171:202[248], 225:61[39], 132:237[184], 74:168[46], 90:31[53], 87:172[87]
8/01/18 09:41:26z ESP8266 ChipID: 6910347
8/01/18 19:41:26 Local time zone: 10
8/01/18 19:41:26 device name: Lilliput, version: 3
8/01/18 19:41:29 MDNS responder started
8/01/18 19:41:29 You can now connect to http://Lilliput.local
8/01/18 19:41:29 HTTP server started
8/01/18 19:41:29 dataLog: service started.
8/01/18 19:41:29 dataLog: Last log entry 8/1/18 19:27:45 
8/01/18 19:41:29 statService: started.
8/01/18 19:41:29 timeSync: service started.
8/01/18 19:41:29 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 19:41:29 Updater: service started. Auto-update class is MINOR
8/01/18 19:41:29 historyLog: service started.
8/01/18 19:41:29 historyLog: Last log entry 8/1/18 19:26:00 
8/01/18 19:41:31 Updater: Auto-update is current for class MINOR.
8/01/18 19:41:34 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 19:41:35 EmonService: Start posting at 8/1/18 19:26:40 

** Restart **

SD initialized.
8/01/18 10:00:18z Real Time Clock is running. Unix time 1533117618 
8/01/18 10:00:18z Power failure detected.
8/01/18 10:00:18z Version 02_03_10
8/01/18 10:00:18z Reset reason: Power on
8/01/18 10:00:18z Trace:  246:66[91], 181:229[184], 116:124[74], 7:117[5], 133:42[76], 86:112[177], 91:98[63], 162:20[25], 60:79[15], 25:176[224], 5:165[201], 52:48[57], 216:112[54], 6:151[25], 180:223[36], 251:238[34], 248:33[38], 213:124[48], 139:129[85], 29:86[179], 106:146[176], 20:15[144], 56:207[29], 30:239[247], 204:68[192], 52:63[215], 171:202[242], 225:61[47], 132:252[184], 74:40[174], 90:95[61], 87:237[215]
8/01/18 10:00:18z ESP8266 ChipID: 6910347
8/01/18 20:00:18 Local time zone: 10
8/01/18 20:00:18 device name: Lilliput, version: 3
8/01/18 20:00:21 MDNS responder started
8/01/18 20:00:21 You can now connect to http://Lilliput.local
8/01/18 20:00:21 HTTP server started
8/01/18 20:00:21 dataLog: service started.
8/01/18 20:00:21 dataLog: Last log entry 8/1/18 19:50:25 
8/01/18 20:00:23 statService: started.
8/01/18 20:00:23 timeSync: service started.
8/01/18 20:00:24 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 20:00:24 Updater: service started. Auto-update class is MINOR
8/01/18 20:00:24 historyLog: service started.
8/01/18 20:00:24 historyLog: Last log entry 8/1/18 19:49:00 
8/01/18 20:00:27 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 20:00:27 Updater: Auto-update is current for class MINOR.
8/01/18 20:00:29 EmonService: Start posting at 8/1/18 19:45:00

UPDATE: Added Message LOGS

1 Like
2

What do you mean by crashes? I see one instance early on where there was an exception, then all of the subsequent restarts appear to be because of power failure. Are you deliberately cycling the power to restart it, or are you saying that those events appear to be spontaneous?

3

Br crashing I mean:
-device lights go from green flicker to solid
-device no longer responding to ping
-obviously IoTaWatt local status inaccessible
-no update to Emoncms

I had noticed this occurred at night and out Power voltage does dip a little (enough to flick the lights but not a recorded brownout with the data I have ) Eg down to 225 occasionally from daily of 236

I thought a better power supply for the USB input might help so swapped it.

Total manual power cycles = 2 (once from a forced reboot from me and then again when I changed the power supply)

I don’t 100% trust the wifi and have a better network (unifi) coming in the next few days.

However I did use the word crashing as it appeared it had hung.

4

This is the disconcerting part. Pings are handled by low level code in the ESP, not by the firmware.
I’m assuming you mean solid green on the LED.

Can you get it going and run the graph app to plot your voltage for the past day, and post that along with the latest message log?

Is this the system that you reloaded the SDcard for? If so, did you by any chance first reformat the card? This is the kind of weirdness I see when the SDcard is inconsistent.

If you can run the IoTaWatt with the cover off, you will see a small button labelled “rst” to the left of the usb connector. That is the reset button. If you press that when it is in the hung state with a solid green LED, the message log will include a meaningful trace that can help determine what it’s doing.

5

I could see the IoTaWatt Status page this morning first thing and it had an uptime of 11+ hours. Thats a good start. That is running with an Apple iPad Charger (10W vs 5W) that had been provided before from the power strip.

That said I cant see it now. I am going to try and remove the cover and reset the device.

Gut Instinct 1
Not sure if its a power voltage issue, more a dropout as we are at the end of a long run and there is both a training facility with big lighting and a supermarket within 500metres of us. You can see the lights flicker from abut 7pm as other things occur on the grid.

Gut Instinct 2
I think the WiFi is ok but averagebut don’t trust the router. Its running from the 2.4G network as it was stronger but my gut senses interference.
It seems to drop connections occasionally but isn’t consistent. Again, this is being replaced with decent kit when it arrives in the next day or so.
Is it possible the IotaWatt eventually loses the connection and doesnt recreate the Network connection and just keeps logging?

Ping samples below.

~/SourceControl/IoTaWatt [ (master) ] $ping -i 30 -A 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=1536 ttl=255 time=19.166 ms
64 bytes from 192.168.1.2: icmp_seq=1537 ttl=255 time=189.276 ms
64 bytes from 192.168.1.2: icmp_seq=1538 ttl=255 time=68.057 ms
Request timeout for icmp_seq 1539
64 bytes from 192.168.1.2: icmp_seq=1540 ttl=255 time=137.910 ms
64 bytes from 192.168.1.2: icmp_seq=1541 ttl=255 time=55.555 ms
64 bytes from 192.168.1.2: icmp_seq=1542 ttl=255 time=40.844 ms
Request timeout for icmp_seq 1543
Request timeout for icmp_seq 1544
Request timeout for icmp_seq 1545
Request timeout for icmp_seq 1546
ping: sendto: No route to host

After Opening Box and restarting

ping: sendto: No route to host
Request timeout for icmp_seq 1676
Request timeout for icmp_seq 1677
Request timeout for icmp_seq 1678
Request timeout for icmp_seq 1679
Request timeout for icmp_seq 1680
Request timeout for icmp_seq 1681
64 bytes from 192.168.1.2: icmp_seq=1682 ttl=255 time=163.503 ms
64 bytes from 192.168.1.2: icmp_seq=1683 ttl=255 time=25.185 ms
64 bytes from 192.168.1.2: icmp_seq=1684 ttl=255 time=16.148 ms
64 bytes from 192.168.1.2: icmp_seq=1685 ttl=255 time=5.904 ms
64 bytes from 192.168.1.2: icmp_seq=1686 ttl=255 time=34.863 ms
64 bytes from 192.168.1.2: icmp_seq=1687 ttl=255 time=24.161 ms
64 bytes from 192.168.1.2: icmp_seq=1688 ttl=255 time=26.920 ms
64 bytes from 192.168.1.2: icmp_seq=1689 ttl=255 time=23.903 ms
64 bytes from 192.168.1.2: icmp_seq=1690 ttl=255 time=14.025 ms
64 bytes from 192.168.1.2: icmp_seq=1691 ttl=255 time=132.961 ms

Responding to comments
This is indeed the system I reloaded the SD card for.
I didn’t reformat the card as I could see other “IotaWatt” stuff on the card and didn’t want to risk bricking the device. Its an easy job to reformat and start again.

I am now running it with the top lid off and can see the device and reset button.

If it helps I am running Mac stuff but have access to a Windows 7 laptop.
Background is 30 years IT/Telco Infrastructure with last few years in development so competent to work as needed but was trying to be relatively vanilla as this ecosystem is new to me.

Do you want me to format the SD card and start from scratch. If so anything specific I need to know/refer to? eg should I backup my CT /output/web settings or do it from scratch.

Log attached

8/01/18 12:43:24 HTTP server started
8/01/18 12:43:24 dataLog: service started.
8/01/18 12:43:24 dataLog: Last log entry 8/1/18 12:42:20 
8/01/18 12:43:25 statService: started.
8/01/18 12:43:25 timeSync: service started.
8/01/18 12:43:25 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 12:43:25 Updater: service started. Auto-update class is MINOR
8/01/18 12:43:25 historyLog: service started.
8/01/18 12:43:25 historyLog: Last log entry 8/1/18 12:42:00 
8/01/18 12:43:27 Updater: Auto-update is current for class MINOR.
8/01/18 13:05:36 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:05:38 EmonService: Node doesn't yet exist.
8/01/18 13:05:38 EmonService: Start posting at 8/1/18 13:05:45 
8/01/18 13:05:38 EmonService: Stopped.  Last post 8/1/18 13:05:35 
8/01/18 13:07:38 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:07:40 EmonService: Node doesn't yet exist.
8/01/18 13:07:40 EmonService: Start posting at 8/1/18 13:07:50 
8/01/18 13:35:10 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET

** Restart **

SD initialized.
8/01/18 03:35:11z Real Time Clock is running. Unix time 1533094511 
8/01/18 03:35:11z Version 02_03_10
8/01/18 03:35:11z Reset reason: Exception
8/01/18 03:35:11z Trace:  16:2, 16:3, 16:4, 16:5, 16:7, 11:8, 11:9, 1:4, 1:5[3], 3:0, 3:1, 3:2, 1:6, 1:1[5], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:4, 9:5, 9:9, 1:2, 1:2[6], 1:3, 1:4, 1:5[3], 3:0, 3:3, 3:3, 3:3
8/01/18 03:35:11z ESP8266 ChipID: 6910347
8/01/18 13:35:11 Local time zone: 10
8/01/18 13:35:11 device name: Lilliput, version: 3
8/01/18 13:35:11 MDNS responder started
8/01/18 13:35:11 You can now connect to http://Lilliput.local
8/01/18 13:35:11 HTTP server started
8/01/18 13:35:11 dataLog: service started.
8/01/18 13:35:11 dataLog: Last log entry 8/1/18 13:35:10 
8/01/18 13:35:11 statService: started.
8/01/18 13:35:11 timeSync: service started.
8/01/18 13:35:11 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:35:11 Updater: service started. Auto-update class is MINOR
8/01/18 13:35:11 historyLog: service started.
8/01/18 13:35:11 historyLog: Last log entry 8/1/18 13:35:00 
8/01/18 13:35:13 Updater: Auto-update is current for class MINOR.
8/01/18 13:35:16 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:35:17 EmonService: Start posting at 8/1/18 13:35:20 

** Restart **

SD initialized.
8/01/18 03:46:54z Real Time Clock is running. Unix time 1533095214 
8/01/18 03:46:54z Power failure detected.
8/01/18 03:46:54z Version 02_03_10
8/01/18 03:46:54z Reset reason: External System
8/01/18 03:46:54z Trace:  246:99[123], 181:229[184], 116:120[74], 71:99[21], 167:42[108], 94:120[177], 107:98[51], 170:4[25], 28:79[13], 9:144[226], 5:133[201], 60:49[57], 216:112[54], 6:22[89], 180:159[36], 251:238[50], 240:101[38], 133:124[113], 137:33[69], 31:22[179], 98:178[176], 18:15[144], 56:
** Restart **

SD initialized.
8/01/18 03:47:16z Real Time Clock is running. Unix time 1533095236 
8/01/18 03:47:16z Power failure detected.
8/01/18 03:47:16z Version 02_03_10
8/01/18 03:47:16z Reset reason: External System
8/01/18 03:47:16z Trace:  246:103[91], 181:229[186], 116:104[74], 67:115[21], 165:42[108], 86:112[177], 107:98[53], 170:20[25], 60:111[15], 9:144[242], 5:133[193], 52:49[57], 216:112[54], 6:22[89], 180:223[36], 251:238[50], 240:5[38], 197:252[121], 137:1[69], 25:22[179], 242:146[176], 86:15[144], 58:206[29], 30:235[247], 236:76[224], 52:63[151], 171:202[248], 225:57[47], 132:109[184], 74:168[174], 90:95[61], 87:172[215]
8/01/18 03:47:16z ESP8266 ChipID: 6910347
8/01/18 13:47:16 Local time zone: 10
8/01/18 13:47:16 device name: Lilliput, version: 3
8/01/18 13:47:19 MDNS responder started
8/01/18 13:47:19 You can now connect to http://Lilliput.local
8/01/18 13:47:19 HTTP server started
8/01/18 13:47:19 dataLog: service started.
8/01/18 13:47:19 dataLog: Last log entry 8/1/18 13:46:50 
8/01/18 13:47:19 statService: started.
8/01/18 13:47:19 timeSync: service started.
8/01/18 13:47:19 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:47:20 Updater: service started. Auto-update class is MINOR
8/01/18 13:47:20 historyLog: service started.
8/01/18 13:47:20 historyLog: Last log entry 8/1/18 13:46:00 
8/01/18 13:47:22 Updater: Auto-update is current for class MINOR.
8/01/18 13:47:24 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:47:25 EmonService: Start posting at 8/1/18 13:47:00 
8/01/18 13:48:28 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:48:33 EmonService: Start posting at 8/1/18 13:48:30 
8/01/18 17:10:24 timeSync: adjusting RTC by -3
8/01/18 18:10:27 timeSync: adjusting RTC by 3

** Restart **

SD initialized.
8/01/18 09:41:26z Real Time Clock is running. Unix time 1533116486 
8/01/18 09:41:26z Power failure detected.
8/01/18 09:41:26z Version 02_03_10
8/01/18 09:41:26z Reset reason: External System
8/01/18 09:41:26z Trace:  246:99[123], 181:229[186], 116:120[72], 71:99[85], 165:58[76], 22:120[241], 107:98[57], 170:20[25], 61:79[15], 9:144[226], 5:133[201], 52:53[57], 216:112[54], 6:23[89], 180:223[36], 251:238[34], 240:37[38], 213:252[49], 137:137[69], 29:22[179], 114:178[176], 86:15[144], 56:239[29], 30:99[247], 204:100[224], 52:63[151], 171:202[248], 225:61[39], 132:237[184], 74:168[46], 90:31[53], 87:172[87]
8/01/18 09:41:26z ESP8266 ChipID: 6910347
8/01/18 19:41:26 Local time zone: 10
8/01/18 19:41:26 device name: Lilliput, version: 3
8/01/18 19:41:29 MDNS responder started
8/01/18 19:41:29 You can now connect to http://Lilliput.local
8/01/18 19:41:29 HTTP server started
8/01/18 19:41:29 dataLog: service started.
8/01/18 19:41:29 dataLog: Last log entry 8/1/18 19:27:45 
8/01/18 19:41:29 statService: started.
8/01/18 19:41:29 timeSync: service started.
8/01/18 19:41:29 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 19:41:29 Updater: service started. Auto-update class is MINOR
8/01/18 19:41:29 historyLog: service started.
8/01/18 19:41:29 historyLog: Last log entry 8/1/18 19:26:00 
8/01/18 19:41:31 Updater: Auto-update is current for class MINOR.
8/01/18 19:41:34 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 19:41:35 EmonService: Start posting at 8/1/18 19:26:40 

** Restart **

SD initialized.
8/01/18 10:00:18z Real Time Clock is running. Unix time 1533117618 
8/01/18 10:00:18z Power failure detected.
8/01/18 10:00:18z Version 02_03_10
8/01/18 10:00:18z Reset reason: Power on
8/01/18 10:00:18z Trace:  246:66[91], 181:229[184], 116:124[74], 7:117[5], 133:42[76], 86:112[177], 91:98[63], 162:20[25], 60:79[15], 25:176[224], 5:165[201], 52:48[57], 216:112[54], 6:151[25], 180:223[36], 251:238[34], 248:33[38], 213:124[48], 139:129[85], 29:86[179], 106:146[176], 20:15[144], 56:207[29], 30:239[247], 204:68[192], 52:63[215], 171:202[242], 225:61[47], 132:252[184], 74:40[174], 90:95[61], 87:237[215]
8/01/18 10:00:18z ESP8266 ChipID: 6910347
8/01/18 20:00:18 Local time zone: 10
8/01/18 20:00:18 device name: Lilliput, version: 3
8/01/18 20:00:21 MDNS responder started
8/01/18 20:00:21 You can now connect to http://Lilliput.local
8/01/18 20:00:21 HTTP server started
8/01/18 20:00:21 dataLog: service started.
8/01/18 20:00:21 dataLog: Last log entry 8/1/18 19:50:25 
8/01/18 20:00:23 statService: started.
8/01/18 20:00:23 timeSync: service started.
8/01/18 20:00:24 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 20:00:24 Updater: service started. Auto-update class is MINOR
8/01/18 20:00:24 historyLog: service started.
8/01/18 20:00:24 historyLog: Last log entry 8/1/18 19:49:00 
8/01/18 20:00:27 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 20:00:27 Updater: Auto-update is current for class MINOR.
8/01/18 20:00:29 EmonService: Start posting at 8/1/18 19:45:00 
8/01/18 22:21:21 WiFi disconnected.
8/01/18 22:34:26 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 22:21:22 timeSync: adjusting RTC by -784
8/01/18 23:40:17 timeSync: adjusting RTC by 783
8/01/18 23:49:03 Updater: Invalid response from server. HTTPcode: -11
8/02/18 04:41:05 timeSync: adjusting RTC by 2

** Restart **

SD initialized.
8/01/18 23:53:51z Real Time Clock is running. Unix time 1533167631 
8/01/18 23:53:51z Power failure detected.
8/01/18 23:53:51z Version 02_03_10
8/01/18 23:53:51z Reset reason: External System
8/01/18 23:53:51z Trace:  254:103[91], 181:229[184], 116:108[74], 71:97[53], 165:43[76], 94:120[181], 127:66[57], 170:4[25], 28:79[15], 25:217[246], 5:165[201], 52:53[57], 216:240[54], 70:22[89], 164:95[36], 251:238[34], 240:5[38], 197:252[113], 137:137[69], 29:87[179], 122:240[176], 86:15[145], 56:239[29], 30:99[247], 140:100[224], 52:63[215], 171:202[248], 225:57[167], 132:108[184], 74:42[174], 90:23[125], 87:108[87]
8/01/18 23:53:51z ESP8266 ChipID: 6910347
8/02/18 09:53:51 Local time zone: 10
8/02/18 09:53:51 device name: Lilliput, version: 3
8/02/18 09:53:54 MDNS responder started
8/02/18 09:53:54 You can now connect to http://Lilliput.local
8/02/18 09:53:54 HTTP server started
8/02/18 09:53:54 dataLog: service started.
8/02/18 09:53:54 dataLog: Last log entry 8/2/18 08:59:20 
8/02/18 09:53:54 statService: started.
8/02/18 09:53:54 timeSync: service started.
8/02/18 09:53:54 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/02/18 09:53:54 Updater: service started. Auto-update class is MINOR
8/02/18 09:53:54 historyLog: service started.
8/02/18 09:53:54 historyLog: Last log entry 8/2/18 08:58:00 
8/02/18 09:53:57 Updater: Auto-update is current for class MINOR.
8/02/18 09:53:59 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/02/18 09:54:00 EmonService: Start posting at 8/2/18 08:51:00

Voltage Graph attached

Voltage
Voltage.jpg2244×1406 297 KB

Screenshot of Status (will start another thread to discuss)

Status
Status.png1206×1442 135 KB

6

I can see by the voltage plot that the device isn’t logging when it hangs. That’s very unusual. Logging is one of the three fundamental activities that is unavoidable unless something is monopolizing resources. For that reason, now that you have the thing opened up, doing a reset while it’s in that hung state may help to localize the problem.

So next hang, reset then post the message log if you would.

Phone chargers do not make particularly good power supplies. It’s more about clean power than a lot of power. IoTaWatt draw less than 500ma when operating the radio, and much less in general. Raspberry Pi power supplies seem to work pretty well for IoTaWatt.

If you get one of the power supplies that works from 80V to 270V, you are pretty much insulated from any utility power issues short of complete failure.

7

Thanks for the advice.

I am guessing it might be network. Either way we can see after a reset and the logs.

I have a new power supply coming
1x ET-RPI-3-POWER Raspberry Pi Power Supply (5V 2.5 Amp)

8

This is still with the other power supply as the Rasperry was only ordered today.

Log File (after reset). Light was solid green and immediately went to flickering green on reset.

8/01/18 03:35:11z ESP8266 ChipID: 6910347
8/01/18 13:35:11 Local time zone: 10
8/01/18 13:35:11 device name: Lilliput, version: 3
8/01/18 13:35:11 MDNS responder started
8/01/18 13:35:11 You can now connect to http://Lilliput.local
8/01/18 13:35:11 HTTP server started
8/01/18 13:35:11 dataLog: service started.
8/01/18 13:35:11 dataLog: Last log entry 8/1/18 13:35:10 
8/01/18 13:35:11 statService: started.
8/01/18 13:35:11 timeSync: service started.
8/01/18 13:35:11 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:35:11 Updater: service started. Auto-update class is MINOR
8/01/18 13:35:11 historyLog: service started.
8/01/18 13:35:11 historyLog: Last log entry 8/1/18 13:35:00 
8/01/18 13:35:13 Updater: Auto-update is current for class MINOR.
8/01/18 13:35:16 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:35:17 EmonService: Start posting at 8/1/18 13:35:20 

** Restart **

SD initialized.
8/01/18 03:46:54z Real Time Clock is running. Unix time 1533095214 
8/01/18 03:46:54z Power failure detected.
8/01/18 03:46:54z Version 02_03_10
8/01/18 03:46:54z Reset reason: External System
8/01/18 03:46:54z Trace:  246:99[123], 181:229[184], 116:120[74], 71:99[21], 167:42[108], 94:120[177], 107:98[51], 170:4[25], 28:79[13], 9:144[226], 5:133[201], 60:49[57], 216:112[54], 6:22[89], 180:159[36], 251:238[50], 240:101[38], 133:124[113], 137:33[69], 31:22[179], 98:178[176], 18:15[144], 56:
** Restart **

SD initialized.
8/01/18 03:47:16z Real Time Clock is running. Unix time 1533095236 
8/01/18 03:47:16z Power failure detected.
8/01/18 03:47:16z Version 02_03_10
8/01/18 03:47:16z Reset reason: External System
8/01/18 03:47:16z Trace:  246:103[91], 181:229[186], 116:104[74], 67:115[21], 165:42[108], 86:112[177], 107:98[53], 170:20[25], 60:111[15], 9:144[242], 5:133[193], 52:49[57], 216:112[54], 6:22[89], 180:223[36], 251:238[50], 240:5[38], 197:252[121], 137:1[69], 25:22[179], 242:146[176], 86:15[144], 58:206[29], 30:235[247], 236:76[224], 52:63[151], 171:202[248], 225:57[47], 132:109[184], 74:168[174], 90:95[61], 87:172[215]
8/01/18 03:47:16z ESP8266 ChipID: 6910347
8/01/18 13:47:16 Local time zone: 10
8/01/18 13:47:16 device name: Lilliput, version: 3
8/01/18 13:47:19 MDNS responder started
8/01/18 13:47:19 You can now connect to http://Lilliput.local
8/01/18 13:47:19 HTTP server started
8/01/18 13:47:19 dataLog: service started.
8/01/18 13:47:19 dataLog: Last log entry 8/1/18 13:46:50 
8/01/18 13:47:19 statService: started.
8/01/18 13:47:19 timeSync: service started.
8/01/18 13:47:19 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 13:47:20 Updater: service started. Auto-update class is MINOR
8/01/18 13:47:20 historyLog: service started.
8/01/18 13:47:20 historyLog: Last log entry 8/1/18 13:46:00 
8/01/18 13:47:22 Updater: Auto-update is current for class MINOR.
8/01/18 13:47:24 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:47:25 EmonService: Start posting at 8/1/18 13:47:00 
8/01/18 13:48:28 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 13:48:33 EmonService: Start posting at 8/1/18 13:48:30 
8/01/18 17:10:24 timeSync: adjusting RTC by -3
8/01/18 18:10:27 timeSync: adjusting RTC by 3

** Restart **

SD initialized.
8/01/18 09:41:26z Real Time Clock is running. Unix time 1533116486 
8/01/18 09:41:26z Power failure detected.
8/01/18 09:41:26z Version 02_03_10
8/01/18 09:41:26z Reset reason: External System
8/01/18 09:41:26z Trace:  246:99[123], 181:229[186], 116:120[72], 71:99[85], 165:58[76], 22:120[241], 107:98[57], 170:20[25], 61:79[15], 9:144[226], 5:133[201], 52:53[57], 216:112[54], 6:23[89], 180:223[36], 251:238[34], 240:37[38], 213:252[49], 137:137[69], 29:22[179], 114:178[176], 86:15[144], 56:239[29], 30:99[247], 204:100[224], 52:63[151], 171:202[248], 225:61[39], 132:237[184], 74:168[46], 90:31[53], 87:172[87]
8/01/18 09:41:26z ESP8266 ChipID: 6910347
8/01/18 19:41:26 Local time zone: 10
8/01/18 19:41:26 device name: Lilliput, version: 3
8/01/18 19:41:29 MDNS responder started
8/01/18 19:41:29 You can now connect to http://Lilliput.local
8/01/18 19:41:29 HTTP server started
8/01/18 19:41:29 dataLog: service started.
8/01/18 19:41:29 dataLog: Last log entry 8/1/18 19:27:45 
8/01/18 19:41:29 statService: started.
8/01/18 19:41:29 timeSync: service started.
8/01/18 19:41:29 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 19:41:29 Updater: service started. Auto-update class is MINOR
8/01/18 19:41:29 historyLog: service started.
8/01/18 19:41:29 historyLog: Last log entry 8/1/18 19:26:00 
8/01/18 19:41:31 Updater: Auto-update is current for class MINOR.
8/01/18 19:41:34 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 19:41:35 EmonService: Start posting at 8/1/18 19:26:40 

** Restart **

SD initialized.
8/01/18 10:00:18z Real Time Clock is running. Unix time 1533117618 
8/01/18 10:00:18z Power failure detected.
8/01/18 10:00:18z Version 02_03_10
8/01/18 10:00:18z Reset reason: Power on
8/01/18 10:00:18z Trace:  246:66[91], 181:229[184], 116:124[74], 7:117[5], 133:42[76], 86:112[177], 91:98[63], 162:20[25], 60:79[15], 25:176[224], 5:165[201], 52:48[57], 216:112[54], 6:151[25], 180:223[36], 251:238[34], 248:33[38], 213:124[48], 139:129[85], 29:86[179], 106:146[176], 20:15[144], 56:207[29], 30:239[247], 204:68[192], 52:63[215], 171:202[242], 225:61[47], 132:252[184], 74:40[174], 90:95[61], 87:237[215]
8/01/18 10:00:18z ESP8266 ChipID: 6910347
8/01/18 20:00:18 Local time zone: 10
8/01/18 20:00:18 device name: Lilliput, version: 3
8/01/18 20:00:21 MDNS responder started
8/01/18 20:00:21 You can now connect to http://Lilliput.local
8/01/18 20:00:21 HTTP server started
8/01/18 20:00:21 dataLog: service started.
8/01/18 20:00:21 dataLog: Last log entry 8/1/18 19:50:25 
8/01/18 20:00:23 statService: started.
8/01/18 20:00:23 timeSync: service started.
8/01/18 20:00:24 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 20:00:24 Updater: service started. Auto-update class is MINOR
8/01/18 20:00:24 historyLog: service started.
8/01/18 20:00:24 historyLog: Last log entry 8/1/18 19:49:00 
8/01/18 20:00:27 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/01/18 20:00:27 Updater: Auto-update is current for class MINOR.
8/01/18 20:00:29 EmonService: Start posting at 8/1/18 19:45:00 
8/01/18 22:21:21 WiFi disconnected.
8/01/18 22:34:26 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/01/18 22:21:22 timeSync: adjusting RTC by -784
8/01/18 23:40:17 timeSync: adjusting RTC by 783
8/01/18 23:49:03 Updater: Invalid response from server. HTTPcode: -11
8/02/18 04:41:05 timeSync: adjusting RTC by 2

** Restart **

SD initialized.
8/01/18 23:53:51z Real Time Clock is running. Unix time 1533167631 
8/01/18 23:53:51z Power failure detected.
8/01/18 23:53:51z Version 02_03_10
8/01/18 23:53:51z Reset reason: External System
8/01/18 23:53:51z Trace:  254:103[91], 181:229[184], 116:108[74], 71:97[53], 165:43[76], 94:120[181], 127:66[57], 170:4[25], 28:79[15], 25:217[246], 5:165[201], 52:53[57], 216:240[54], 70:22[89], 164:95[36], 251:238[34], 240:5[38], 197:252[113], 137:137[69], 29:87[179], 122:240[176], 86:15[145], 56:239[29], 30:99[247], 140:100[224], 52:63[215], 171:202[248], 225:57[167], 132:108[184], 74:42[174], 90:23[125], 87:108[87]
8/01/18 23:53:51z ESP8266 ChipID: 6910347
8/02/18 09:53:51 Local time zone: 10
8/02/18 09:53:51 device name: Lilliput, version: 3
8/02/18 09:53:54 MDNS responder started
8/02/18 09:53:54 You can now connect to http://Lilliput.local
8/02/18 09:53:54 HTTP server started
8/02/18 09:53:54 dataLog: service started.
8/02/18 09:53:54 dataLog: Last log entry 8/2/18 08:59:20 
8/02/18 09:53:54 statService: started.
8/02/18 09:53:54 timeSync: service started.
8/02/18 09:53:54 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/02/18 09:53:54 Updater: service started. Auto-update class is MINOR
8/02/18 09:53:54 historyLog: service started.
8/02/18 09:53:54 historyLog: Last log entry 8/2/18 08:58:00 
8/02/18 09:53:57 Updater: Auto-update is current for class MINOR.
8/02/18 09:53:59 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/02/18 09:54:00 EmonService: Start posting at 8/2/18 08:51:00 
8/02/18 15:55:19 timeSync: adjusting RTC by -381
8/02/18 17:09:25 timeSync: adjusting RTC by 379

** Restart **

SD initialized.
8/02/18 08:09:26z Real Time Clock is running. Unix time 1533197366 
8/02/18 08:09:26z Version 02_03_10
8/02/18 08:09:26z Reset reason: External System
8/02/18 08:09:26z Trace:  8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8
8/02/18 08:09:26z ESP8266 ChipID: 6910347
8/02/18 18:09:26 Local time zone: 10
8/02/18 18:09:26 device name: Lilliput, version: 3
8/02/18 18:09:26 MDNS responder started
8/02/18 18:09:26 You can now connect to http://Lilliput.local
8/02/18 18:09:26 HTTP server started
8/02/18 18:09:26 dataLog: service started.
8/02/18 18:09:26 dataLog: Last log entry 8/2/18 17:52:20 
8/02/18 18:09:26 statService: started.
8/02/18 18:09:26 timeSync: service started.
8/02/18 18:09:26 WiFi connected. SSID: Gallifrey2, IP: 192.168.1.2
8/02/18 18:09:26 Updater: service started. Auto-update class is MINOR
8/02/18 18:09:26 historyLog: service started.
8/02/18 18:09:26 historyLog: Last log entry 8/2/18 17:51:00 
8/02/18 18:09:28 Updater: Auto-update is current for class MINOR.
8/02/18 18:09:31 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/02/18 18:09:32 EmonService: Start posting at 8/2/18 17:50:10

It comes and goes a little. This is with a ping every 120 seconds:
(IotaWatt should be on 192.168.1.2

~/SourceControl/IoTaWatt [ (master) ] $arp -a
? (192.168.1.1) at 98:e7:f5:af:75:47 on en0 ifscope [ethernet]
? (192.168.1.2) at (incomplete) on en0 ifscope [ethernet]
? (192.168.1.5) at 38:ca:da:73:39:43 on en0 ifscope [ethernet]
? (192.168.1.6) at dc:a4:ca:b3:8d:be on en0 ifscope [ethernet]
? (192.168.1.7) at a4:5e:60:d8:aa:23 on en0 ifscope permanent [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]
? (239.255.255.250) at 1:0:5e:7f:ff:fa on en0 ifscope permanent [ethernet]

Ping record:

~/SourceControl/IoTaWatt [ (master) ] $ping -i 120 -A 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=22.713 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=113.354 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=22.983 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=53.104 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=21.996 ms
64 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=58.696 ms
64 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=42.504 ms
64 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=82.143 ms
64 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=100.732 ms
64 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=30.384 ms
64 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=120.917 ms
64 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=38.824 ms
64 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=53.827 ms
64 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=62.065 ms
64 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=97.881 ms
64 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=115.218 ms
64 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=14.490 ms
64 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=17.791 ms
64 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=3.605 ms
64 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=24.906 ms
64 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=40.448 ms
64 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=36.050 ms
64 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=22.865 ms
64 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=7.764 ms
64 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=55.051 ms
64 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=87.211 ms
64 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=128.626 ms
64 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=100.800 ms
64 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=89.178 ms
64 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=130.568 ms
64 bytes from 192.168.1.2: icmp_seq=30 ttl=255 time=8.294 ms
64 bytes from 192.168.1.2: icmp_seq=31 ttl=255 time=23.990 ms
64 bytes from 192.168.1.2: icmp_seq=32 ttl=255 time=30.565 ms
64 bytes from 192.168.1.2: icmp_seq=33 ttl=255 time=76.242 ms
64 bytes from 192.168.1.2: icmp_seq=34 ttl=255 time=13.811 ms
64 bytes from 192.168.1.2: icmp_seq=35 ttl=255 time=40.375 ms
64 bytes from 192.168.1.2: icmp_seq=36 ttl=255 time=18.994 ms
64 bytes from 192.168.1.2: icmp_seq=37 ttl=255 time=90.698 ms
64 bytes from 192.168.1.2: icmp_seq=38 ttl=255 time=139.658 ms
64 bytes from 192.168.1.2: icmp_seq=39 ttl=255 time=24.010 ms
64 bytes from 192.168.1.2: icmp_seq=40 ttl=255 time=54.035 ms
64 bytes from 192.168.1.2: icmp_seq=41 ttl=255 time=42.486 ms
64 bytes from 192.168.1.2: icmp_seq=42 ttl=255 time=20.508 ms
64 bytes from 192.168.1.2: icmp_seq=43 ttl=255 time=27.338 ms
64 bytes from 192.168.1.2: icmp_seq=44 ttl=255 time=112.011 ms
64 bytes from 192.168.1.2: icmp_seq=45 ttl=255 time=35.573 ms
64 bytes from 192.168.1.2: icmp_seq=46 ttl=255 time=63.130 ms
64 bytes from 192.168.1.2: icmp_seq=47 ttl=255 time=30.028 ms
64 bytes from 192.168.1.2: icmp_seq=48 ttl=255 time=18.519 ms
64 bytes from 192.168.1.2: icmp_seq=49 ttl=255 time=44.059 ms
64 bytes from 192.168.1.2: icmp_seq=50 ttl=255 time=81.646 ms
64 bytes from 192.168.1.2: icmp_seq=51 ttl=255 time=54.509 ms
64 bytes from 192.168.1.2: icmp_seq=52 ttl=255 time=113.278 ms
64 bytes from 192.168.1.2: icmp_seq=53 ttl=255 time=78.146 ms
64 bytes from 192.168.1.2: icmp_seq=54 ttl=255 time=97.822 ms
64 bytes from 192.168.1.2: icmp_seq=55 ttl=255 time=106.130 ms
64 bytes from 192.168.1.2: icmp_seq=56 ttl=255 time=100.956 ms
64 bytes from 192.168.1.2: icmp_seq=57 ttl=255 time=98.359 ms
64 bytes from 192.168.1.2: icmp_seq=58 ttl=255 time=151.558 ms
64 bytes from 192.168.1.2: icmp_seq=59 ttl=255 time=8.504 ms
64 bytes from 192.168.1.2: icmp_seq=60 ttl=255 time=28.403 ms
64 bytes from 192.168.1.2: icmp_seq=61 ttl=255 time=152.829 ms
64 bytes from 192.168.1.2: icmp_seq=62 ttl=255 time=106.992 ms
64 bytes from 192.168.1.2: icmp_seq=63 ttl=255 time=112.329 ms
64 bytes from 192.168.1.2: icmp_seq=64 ttl=255 time=77.523 ms
64 bytes from 192.168.1.2: icmp_seq=65 ttl=255 time=93.823 ms
64 bytes from 192.168.1.2: icmp_seq=66 ttl=255 time=99.319 ms
64 bytes from 192.168.1.2: icmp_seq=67 ttl=255 time=28.671 ms
64 bytes from 192.168.1.2: icmp_seq=68 ttl=255 time=16.960 ms
64 bytes from 192.168.1.2: icmp_seq=69 ttl=255 time=164.885 ms
64 bytes from 192.168.1.2: icmp_seq=70 ttl=255 time=20.571 ms
64 bytes from 192.168.1.2: icmp_seq=71 ttl=255 time=49.968 ms
64 bytes from 192.168.1.2: icmp_seq=72 ttl=255 time=41.060 ms
64 bytes from 192.168.1.2: icmp_seq=73 ttl=255 time=65.335 ms
64 bytes from 192.168.1.2: icmp_seq=74 ttl=255 time=79.652 ms
64 bytes from 192.168.1.2: icmp_seq=75 ttl=255 time=79.063 ms
64 bytes from 192.168.1.2: icmp_seq=76 ttl=255 time=37.917 ms
64 bytes from 192.168.1.2: icmp_seq=77 ttl=255 time=19.358 ms
64 bytes from 192.168.1.2: icmp_seq=78 ttl=255 time=89.094 ms
64 bytes from 192.168.1.2: icmp_seq=79 ttl=255 time=105.343 ms
64 bytes from 192.168.1.2: icmp_seq=80 ttl=255 time=141.717 ms
64 bytes from 192.168.1.2: icmp_seq=81 ttl=255 time=120.722 ms
64 bytes from 192.168.1.2: icmp_seq=82 ttl=255 time=14.959 ms
64 bytes from 192.168.1.2: icmp_seq=83 ttl=255 time=128.632 ms
64 bytes from 192.168.1.2: icmp_seq=84 ttl=255 time=190.669 ms
64 bytes from 192.168.1.2: icmp_seq=85 ttl=255 time=52.638 ms
64 bytes from 192.168.1.2: icmp_seq=86 ttl=255 time=5.386 ms
64 bytes from 192.168.1.2: icmp_seq=87 ttl=255 time=80.282 ms
64 bytes from 192.168.1.2: icmp_seq=88 ttl=255 time=56.340 ms
64 bytes from 192.168.1.2: icmp_seq=89 ttl=255 time=115.819 ms
64 bytes from 192.168.1.2: icmp_seq=90 ttl=255 time=36.871 ms
64 bytes from 192.168.1.2: icmp_seq=91 ttl=255 time=114.048 ms
64 bytes from 192.168.1.2: icmp_seq=92 ttl=255 time=151.866 ms
64 bytes from 192.168.1.2: icmp_seq=93 ttl=255 time=36.780 ms
64 bytes from 192.168.1.2: icmp_seq=94 ttl=255 time=47.370 ms
64 bytes from 192.168.1.2: icmp_seq=95 ttl=255 time=76.331 ms
64 bytes from 192.168.1.2: icmp_seq=96 ttl=255 time=29.281 ms
64 bytes from 192.168.1.2: icmp_seq=97 ttl=255 time=81.773 ms
64 bytes from 192.168.1.2: icmp_seq=98 ttl=255 time=70.811 ms
64 bytes from 192.168.1.2: icmp_seq=99 ttl=255 time=93.319 ms
64 bytes from 192.168.1.2: icmp_seq=100 ttl=255 time=97.264 ms
64 bytes from 192.168.1.2: icmp_seq=101 ttl=255 time=100.886 ms
64 bytes from 192.168.1.2: icmp_seq=102 ttl=255 time=29.029 ms
64 bytes from 192.168.1.2: icmp_seq=103 ttl=255 time=8.953 ms
64 bytes from 192.168.1.2: icmp_seq=104 ttl=255 time=24.663 ms
Request timeout for icmp_seq 105
Request timeout for icmp_seq 106
Request timeout for icmp_seq 107
Request timeout for icmp_seq 108
Request timeout for icmp_seq 109
Request timeout for icmp_seq 110
Request timeout for icmp_seq 111
Request timeout for icmp_seq 112
Request timeout for icmp_seq 113
Request timeout for icmp_seq 114
Request timeout for icmp_seq 115
Request timeout for icmp_seq 116
Request timeout for icmp_seq 117
Request timeout for icmp_seq 118
Request timeout for icmp_seq 119
Request timeout for icmp_seq 120
Request timeout for icmp_seq 121
Request timeout for icmp_seq 122
Request timeout for icmp_seq 123
Request timeout for icmp_seq 124
Request timeout for icmp_seq 125
Request timeout for icmp_seq 126
Request timeout for icmp_seq 127
Request timeout for icmp_seq 128
Request timeout for icmp_seq 129
Request timeout for icmp_seq 130
Request timeout for icmp_seq 131
Request timeout for icmp_seq 132
Request timeout for icmp_seq 133
Request timeout for icmp_seq 134
Request timeout for icmp_seq 135
Request timeout for icmp_seq 136
Request timeout for icmp_seq 137
Request timeout for icmp_seq 138
Request timeout for icmp_seq 139
Request timeout for icmp_seq 140
Request timeout for icmp_seq 141
Request timeout for icmp_seq 142
Request timeout for icmp_seq 143
Request timeout for icmp_seq 144
Request timeout for icmp_seq 145
Request timeout for icmp_seq 146
Request timeout for icmp_seq 147
Request timeout for icmp_seq 148
Request timeout for icmp_seq 149
Request timeout for icmp_seq 150
Request timeout for icmp_seq 151
Request timeout for icmp_seq 152
Request timeout for icmp_seq 153
Request timeout for icmp_seq 154
Request timeout for icmp_seq 155
Request timeout for icmp_seq 156
Request timeout for icmp_seq 157
64 bytes from 192.168.1.2: icmp_seq=158 ttl=255 time=59.203 ms
64 bytes from 192.168.1.2: icmp_seq=159 ttl=255 time=96.547 ms
64 bytes from 192.168.1.2: icmp_seq=160 ttl=255 time=26.292 ms
64 bytes from 192.168.1.2: icmp_seq=161 ttl=255 time=71.471 ms
64 bytes from 192.168.1.2: icmp_seq=162 ttl=255 time=68.240 ms
Request timeout for icmp_seq 163
64 bytes from 192.168.1.2: icmp_seq=164 ttl=255 time=170.836 ms
64 bytes from 192.168.1.2: icmp_seq=165 ttl=255 time=129.568 ms
64 bytes from 192.168.1.2: icmp_seq=166 ttl=255 time=51.476 ms
64 bytes from 192.168.1.2: icmp_seq=167 ttl=255 time=103.125 ms
64 bytes from 192.168.1.2: icmp_seq=168 ttl=255 time=54.204 ms
64 bytes from 192.168.1.2: icmp_seq=169 ttl=255 time=69.585 ms
64 bytes from 192.168.1.2: icmp_seq=170 ttl=255 time=23.302 ms
64 bytes from 192.168.1.2: icmp_seq=171 ttl=255 time=128.615 ms
64 bytes from 192.168.1.2: icmp_seq=172 ttl=255 time=94.230 ms
64 bytes from 192.168.1.2: icmp_seq=173 ttl=255 time=136.343 ms
64 bytes from 192.168.1.2: icmp_seq=174 ttl=255 time=20.130 ms
64 bytes from 192.168.1.2: icmp_seq=175 ttl=255 time=144.866 ms
64 bytes from 192.168.1.2: icmp_seq=176 ttl=255 time=68.985 ms
64 bytes from 192.168.1.2: icmp_seq=177 ttl=255 time=183.066 ms
Request timeout for icmp_seq 178
Request timeout for icmp_seq 179
Request timeout for icmp_seq 180
Request timeout for icmp_seq 181
Request timeout for icmp_seq 182
Request timeout for icmp_seq 183
Request timeout for icmp_seq 184
Request timeout for icmp_seq 185
9

That was what I needed. The device is stuck in a loop trying to get a decent set of samples from the VT. I’m not entirely sure why this is happening though. I can and will put a timeout on that loop, and that will solve the general problem, but I’d like to better understand why your particular installation is having this problem, and determine if it could possibly a problem with the hardware (though I doubt it).

So I’m wondering if you can connect a serial monitor to the IoTaWatt. This would involve connecting it to a USB port on a computer, and running a serial monitor program like Putty or equivalent. You would determine the USBn number and use a data rate of 115200 baud. The monitor will produce all that goes to the message log, plus more information in unusual circumstances. Here I’m looking for it squirting out “Low sample count nnn” over and over, and I’m interested in seeing a couple of dozen sequential instances of it.

It’s possible that you will be getting sporadic incidences, and while that is abnormal as well, I’m particularly interested in any continuous stream you might get when it hangs. There is also the possibility that it will hang without that message, which is also good information and takes me in another direction.

Where did you get your VT and does it seem to work OK otherwise?

Also, since you have three-phase, is it possible that your USB power supply is on a different phase from your VT? It shouldn’t matter if all is working properly, but it may be significant in one particular case.

10

if you can connect a serial monitor to the IoTaWatt

No problem - I will need to go borrow one from a mate as mine is all packed still but give me a few hours and I will have this running.

Where did you get your VT and does it seem to work OK otherwise

The VT is brand new and came from JayCar Electronics. Kind of equivalent to Tandy/RadioShack (they have everything handy but it costs you for it.) Its same as we have used for another IotaWatt and seems to be fine.

is it possible that your USB power supply is on a different phase from your VT?

Both items are plugged into the same surge protected power strip (6 ports) and fed from House circuit 4 (which we don’t have monitoring on).

11

In positive news the new power supply and internet kit just got delivered so I will be installing that while not troubleshooting the CTs.

1 Like
12

Hi Guys,
After some advice on next steps to take.

Background.

  • Just getting setup and have the CT/etc finally sorted but only running less than a week
  • Location in Sydney/Australia logging to emoncms.org
  • I have changed Web to: post interval = 10 and bulk send = 12
  • New Raspberry PI power which seems solid
  • New Unify Pro WiFi. ( Have validated channels are clear and strength is decent. I can do a lot more tuning if there is a particular channel/ it likes but it has a solid signal on a relatively clear channel. Unify is reporting that the client signal strength is -60db and channel is clear. I am going to move the Access Point to within a meter of it but I don’t think thats the reason.

Feeds/Draft DRAFT Dashboard.
Nothing secret here. Stats are really only good from last 48 hours or so as I needed to move/sort out my 3 phase.

The issue
The IotaWatt will run and then stop being responsive to the network, sometimes it runs for hours, sometimes minutes. When its unresponsive, it stops logging to emoncms and I cant access its local web server.
I have a ping running every 3 minutes and it never times out.

When it hangs the light is normally GREEN solid. This morning it was RED.

Questions:
1. IotaWatt Wifi Spec
I am assuming Iotawatt can only operate in 2.4G Wifi.
Is there a particular specification (A/B/G/N) it does/does not support and I can disable the others as all my other devices are 5G.

2. Http vs Https
When I placed in my user ID it switched to https this seemed to cause more errors/freezes.
I turned it back off for now but happy to take advice?

2. Backup/Restore/?
Is this the best approach?
I am happy to lose history but would rather retain site configuration/inputs/outputs etc.?
Fine to reformat the card and fire up python if thats needed.

3. More inputs for monitoring
Its still very early days - only just started getting data on the property. If we are indeed using 50kW a day then it makes sense for me to spend some more on monitoring and figure out where/what and any monitoring pays for itself quickly.

Something I can see is that the house is using a lot more power than expected (vs the other things eg AirCon/Garage). All my inputs are used and it would be nice to have another 7 (so I can see the house circuits + stove + lighting) and figure out based on real stats vs a calculated number for the entire house. From what I can see they are all on PhaseA.

Happy to directly purchase another IoTaWatt directly with even an extra SD card. I can get the CTs from you at the same time or more SCT-013 which is what I am using elsewhere. There may be a different option.
Please let me know

LOG File attached

8/07/18 15:16:17 Updater: Auto-update is current for class MINOR.
8/07/18 15:16:19 EmonService: Start posting at 8/7/18 15:12:40 

** Restart **

SD initialized.
8/07/18 05:31:42z Real Time Clock is running. Unix time 1533619902 
8/07/18 05:31:42z Version 02_03_10
8/07/18 05:31:42z Reset reason: External System
8/07/18 05:31:42z Trace:  8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8
8/07/18 05:31:42z ESP8266 ChipID: 6910347
8/07/18 15:31:42 Local time zone: 10
8/07/18 15:31:42 device name: lilliput, version: 3
8/07/18 15:31:44 MDNS responder started
8/07/18 15:31:44 You can now connect to http://lilliput.local
8/07/18 15:31:44 HTTP server started
8/07/18 15:31:44 dataLog: service started.
8/07/18 15:31:44 dataLog: Last log entry 8/7/18 15:19:10 
8/07/18 15:31:44 statService: started.
8/07/18 15:31:44 timeSync: service started.
8/07/18 15:31:44 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 15:31:45 Updater: service started. Auto-update class is MINOR
8/07/18 15:31:45 historyLog: service started.
8/07/18 15:31:45 historyLog: Last log entry 8/7/18 15:18:00 
8/07/18 15:31:47 Updater: Auto-update is current for class MINOR.
8/07/18 15:31:49 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, encrypted POST
8/07/18 15:31:50 EmonService: Start posting at 8/7/18 15:16:50 
8/07/18 15:32:09 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/07/18 15:32:11 EmonService: Start posting at 8/7/18 15:32:00 
8/07/18 16:10:15 WiFi disconnected.
8/07/18 16:10:27 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 16:19:14 WiFi disconnected.
8/07/18 16:33:12 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 16:33:22 WiFi disconnected.

** Restart **

SD initialized.
8/07/18 06:47:55z Real Time Clock is running. Unix time 1533624475 
8/07/18 06:47:55z Version 02_03_10
8/07/18 06:47:55z Reset reason: External System
8/07/18 06:47:55z Trace:  8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8
8/07/18 06:47:55z ESP8266 ChipID: 6910347
8/07/18 16:47:55 Local time zone: 10
8/07/18 16:47:55 device name: lilliput, version: 3
8/07/18 16:47:58 Connecting with WiFiManager.
8/07/18 16:48:02 MDNS responder started
8/07/18 16:48:02 You can now connect to http://lilliput.local
8/07/18 16:48:02 HTTP server started
8/07/18 16:48:02 dataLog: service started.
8/07/18 16:48:02 dataLog: Last log entry 8/7/18 16:21:05 
8/07/18 16:48:02 statService: started.
8/07/18 16:48:02 timeSync: service started.
8/07/18 16:48:02 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 16:48:03 Updater: service started. Auto-update class is MINOR
8/07/18 16:48:03 historyLog: service started.
8/07/18 16:48:03 historyLog: Last log entry 8/7/18 16:20:00 
8/07/18 16:48:04 Updater: Auto-update is current for class MINOR.
8/07/18 16:48:07 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/07/18 16:48:08 EmonService: Start posting at 8/7/18 16:15:50 
8/07/18 17:03:44 WiFi disconnected.
8/07/18 17:03:47 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 19:36:42 WiFi disconnected.
8/07/18 19:41:49 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 20:17:08 WiFi disconnected.
8/07/18 20:20:20 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 20:23:13 WiFi disconnected.
8/07/18 20:26:22 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 20:26:54 WiFi disconnected.
8/07/18 20:29:59 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10

** Restart **

SD initialized.
8/07/18 10:41:18z Real Time Clock is running. Unix time 1533638478 
8/07/18 10:41:18z Version 02_03_10
8/07/18 10:41:18z Reset reason: External System
8/07/18 10:41:18z Trace:  8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4
8/07/18 10:41:18z ESP8266 ChipID: 6910347
8/07/18 20:41:18 Local time zone: 10
8/07/18 20:41:18 device name: lilliput, version: 3
8/07/18 20:41:20 MDNS responder started
8/07/18 20:41:20 You can now connect to http://lilliput.local
8/07/18 20:41:20 HTTP server started
8/07/18 20:41:20 dataLog: service started.
8/07/18 20:41:20 dataLog: Last log entry 8/7/18 20:22:20 
8/07/18 20:41:20 statService: started.
8/07/18 20:41:20 timeSync: service started.
8/07/18 20:41:20 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 20:41:21 Updater: service started. Auto-update class is MINOR
8/07/18 20:41:21 historyLog: service started.
8/07/18 20:41:21 historyLog: Last log entry 8/7/18 20:21:00 
8/07/18 20:41:24 Updater: Auto-update is current for class MINOR.
8/07/18 20:41:25 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/07/18 20:41:26 EmonService: Start posting at 8/7/18 19:28:30 
8/07/18 21:24:51 WiFi disconnected.
8/07/18 22:25:54 WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
8/07/18 12:25:56z Real Time Clock is running. Unix time 1533644756 
8/07/18 12:25:56z Version 02_03_10
8/07/18 12:25:56z Reset reason: Software/System restart
8/07/18 12:25:56z Trace:  18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:2, 18:3, 18:4, 18:5, 1:6, 1:3, 1:4, 1:5[21]
8/07/18 12:25:56z ESP8266 ChipID: 6910347
8/07/18 22:25:56 Local time zone: 10
8/07/18 22:25:56 device name: lilliput, version: 3
8/07/18 22:25:59 Connecting with WiFiManager.
8/07/18 22:26:04 MDNS responder started
8/07/18 22:26:04 You can now connect to http://lilliput.local
8/07/18 22:26:04 HTTP server started
8/07/18 22:26:05 dataLog: service started.
8/07/18 22:26:05 dataLog: Last log entry 8/7/18 21:26:10 
8/07/18 22:26:05 statService: started.
8/07/18 22:26:05 timeSync: service started.
8/07/18 22:26:05 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/07/18 22:26:05 Updater: service started. Auto-update class is MINOR
8/07/18 22:26:05 historyLog: service started.
8/07/18 22:26:05 historyLog: Last log entry 8/7/18 21:25:00 
8/07/18 22:26:07 Updater: Auto-update is current for class MINOR.
8/07/18 22:26:10 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/07/18 22:26:11 EmonService: Start posting at 8/7/18 21:09:00 
8/08/18 02:13:13 EmonService: HTTP response -4, retrying.
8/08/18 02:13:38 EmonService: Retry successful after 4 attempts.
8/08/18 07:24:45 WiFi disconnected.

** Restart **

SD initialized.
8/07/18 21:25:43z Real Time Clock is running. Unix time 1533677143 
8/07/18 21:25:43z Version 02_03_10
8/07/18 21:25:43z Reset reason: External System
8/07/18 21:25:43z Trace:  8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8, 8:4, 8:6, 8:8
8/07/18 21:25:43z ESP8266 ChipID: 6910347
8/08/18 07:25:43 Local time zone: 10
8/08/18 07:25:43 device name: lilliput, version: 3
8/08/18 07:25:45 MDNS responder started
8/08/18 07:25:45 You can now connect to http://lilliput.local
8/08/18 07:25:45 HTTP server started
8/08/18 07:25:45 dataLog: service started.
8/08/18 07:25:45 dataLog: Last log entry 8/8/18 07:19:35 
8/08/18 07:25:46 statService: started.
8/08/18 07:25:46 timeSync: service started.
8/08/18 07:25:46 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/08/18 07:25:46 Updater: service started. Auto-update class is MINOR
8/08/18 07:25:46 historyLog: service started.
8/08/18 07:25:46 historyLog: Last log entry 8/8/18 07:18:00 
8/08/18 07:25:50 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/08/18 07:25:50 Updater: Auto-update is current for class MINOR.
8/08/18 07:25:52 EmonService: Start posting at 8/8/18 07:17:10 
8/08/18 07:48:01 Restart command received.

** Restart **

SD initialized.
8/07/18 21:48:02z Real Time Clock is running. Unix time 1533678482 
8/07/18 21:48:02z Version 02_03_10
8/07/18 21:48:02z Reset reason: Software/System restart
8/07/18 21:48:02z Trace:  9:9, 1:2, 1:2[2], 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[2], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:4, 9:5, 9:9, 1:2, 1:2[3], 1:3, 10:2, 10:3
8/07/18 21:48:02z ESP8266 ChipID: 6910347
8/08/18 07:48:02 Local time zone: 10
8/08/18 07:48:02 device name: lilliput, version: 3
8/08/18 07:48:05 Connecting with WiFiManager.
8/08/18 07:48:10 MDNS responder started
8/08/18 07:48:10 You can now connect to http://lilliput.local
8/08/18 07:48:10 HTTP server started
8/08/18 07:48:10 dataLog: service started.
8/08/18 07:48:11 dataLog: Last log entry 8/8/18 07:48:00 
8/08/18 07:48:12 statService: started.
8/08/18 07:48:12 timeSync: service started.
8/08/18 07:48:12 WiFi connected. SSID: Gallifrey, IP: 192.168.1.10
8/08/18 07:48:12 Updater: service started. Auto-update class is MINOR
8/08/18 07:48:12 historyLog: service started.
8/08/18 07:48:13 historyLog: Last log entry 8/8/18 07:48:00 
8/08/18 07:48:15 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/08/18 07:48:15 Updater: Auto-update is current for class MINOR.
8/08/18 07:48:17 EmonService: Start posting at 8/8/18 07:48:00 
8/08/18 07:52:14 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/08/18 07:52:15 EmonService: Start posting at 8/8/18 07:52:00 
8/08/18 07:53:03 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/08/18 07:53:04 EmonService: Start posting at 8/8/18 07:52:00 
8/08/18 07:53:30 EmonService: started. url:emoncms.org:80,node:Lilliput,interval:10, unsecure GET
8/08/18 07:53:31 EmonService: Start posting at 8/8/18 07:52:00

EDITS: Add link to dashboard and update additional circuits needed (Total of 7 additional)

13

[quote=“bluetardis, post:12, topic:248”]
The IotaWatt will run and then stop being responsive to the network, sometimes it runs for hours, sometimes minutes. When its unresponsive, it stops logging to emoncms and I cant access its local web server.
I have a ping running every 3 minutes and it never times out.
[/qu
ote]

Looking at the trace, this is the same problem that has caused this in the past. It appears to be related to the VT sampling. I questioned the VT a few days ago and would need to see additional diagnostic info from a serial monitor.

These are two separate issues. The hanging is in the sampling routines, and effectively suspends sampling until a viable VT signal is processed. The green/red LED is an indication of WiFi connection state. Green connected, Red disconnected.

correct.

It’s not HTTPS, it’s always HTTP but the data is encrypted by IoTaWatt and Emonmcms (as opposed to the socket or transport layer). I don’t see how that can cause it to hang more often. It’s possible that could cause more communication errors as there is more data and additional layers of error checking (HMAC, decryption).

I don’t see where anything is being lost. When the sampling hangs, there is no data going into the log, but it does pick up again, and it appears to be uploading what it has when WiFi is restored. Making the best of a bad situation.

You can verify that by reading the meter. I’m not confident you have the phase/CT orientation correct yet. Getting some corroboration with the meter would be nice

I don’t know if moving the WiFi that close would be better or worse. Some things to look into are whether you have other 2.4GHz devices that may be interfering, and whether the IoTaWatt icould be getting some EMI from other stuff in proximity to it and the panel.

14

Looking at the trace, this is the same problem that has caused this in the past. It appears to be related to the VT sampling. I questioned the VT a few days ago and would need to see additional diagnostic info from a serial monitor.

This is on my todo list but needs to wait a USB–Serial adapter that I haven’t unpacked yet. It will happen post weekend.

I’m not confident you have the phase/CT orientation correct yet

I agree but I think we are close. My plan is to get a second set of eyes/tools and shut down all power then test inputs and CT/Phase configuration by each group until we have consistent pf readings (ideally close to 1.0) for every load

You can verify that by reading the meter

Manually logging the meter with photos - give me a few days and I will have totals for MAINS and SOLAR and we can see how it lines up

I don’t know if moving the WiFi that close would be better or worse. Some things to look into are whether you have other 2.4GHz devices that may be interfering, and whether the IoTaWatt icould be getting some EMI from other stuff in proximity to it and the panel.

No other 2.4G I can find. There is some other Wifi around but I did a full Site Scan and have located clear channels etc. My thought was to turn off anything that wasn’t needed eg Disable B/G ?

UPDATE:
added a comment re phase setup but will post that elsewhere including final configs etc. after this weekend

15

The IoTaWatt already has a serial to usb converter, so it is sufficient to connect a normal micro usb cable where otherwise the power supply is connected and the other side into a computer.

16

Of course…I should have realised that but have been pretty busy.

Do you know if there are any recommendations for port setup or is it a virtual uart? Using a Mac if that helps

17

With a mac you can use the screen tool inside a terminal: Open a terminal window and type screen /dev/tty.SLAB_USBtoUART 115200 However, your serial port can be different. Before connecting the IotaWatt, check the output of ls /dev and afterwards.

Alternatively, you can install Platformio or the Arduino software and use their serial monitoring capabilities.

18

@overeasy - Other than logging the default console to a log file is there anything else you want to run. I will be using the USB to UART from tty (which is how I access most of my FC boards).

It still goes to “sleep” during the evening (around 8pm local) but has been automagically coming back about 9am local time with no intervention.

It does seem better with the IotaWatt Web Server bulk send of 12.

19

When you say goes to sleep, I’m thinking it stops logging to Emoncms but when it reconnects in the morning it uploads the backlog. So during the night, it is logging internally, just not sending the data because WiFi is stressed?

Sure, less sending, fewer errors.
In bulk upload when recovering a backlog, bulk send is ignored and each message contains about 40 frames. I think 6 is a good bulk upload on balance. If you get an error with six, any new measurements taken during recovery will be added to the recovery message anyway. So in a poor WiFi climate, better to start recovery earlier than later.

20

So during the night, it is logging internally, just not sending the data because WiFi is stressed?

I thought it was ok but on checking the graph from Iotawatt it clearly has some gaps.

18%20pm
18%20pm2326×1344 344 KB

That said it does resume and if it was just WiFi then I would be ok in the morning… just a backlog to update.

I think 6 is a good bulk upload on balance.
I will update this to 6

Logging:
When I patched in the Mac to the USB port, I couldn’t see /dev/tty.SLAB_USBtoUART
just my bluetooth. Thats odd as I do have drivers installed as its how I program my Quad Flight Controllers via that port. I will double check but cable is known working good and so is computer.

I think if we can get the logging and VT sorted that will resolve things.