emonPi with IoTaWatt

@overeasy, @promy, @glyn.hudson - I am curious how you got the iotawatt and the emonPi working together?

emoncms.org works mostly A-OK. Sometimes it sends data to emoncms.org as expected. And sometimes I do get this below:

11/1/17 18:51:08 EmonService: started.url: emoncms.org, node: IotaWatt, post interval: 10, encrypted POST
11/1/17 18:51:08 EmonService: Start posting from 1509573920
11/1/17 19:08:50 EmonService: POST failed. HTTP code: read Timeout
11/1/17 19:09:20 Resending EmonCMS data.
11/1/17 19:25:10 EmonService: POST failed. HTTP code: read Timeout
11/1/17 19:25:40 Resending EmonCMS data.

from what I see in the above thread this is being worked on (LOTS to digest in one big thread!)
 

But I don’t plan to use the iotawatt connected to emoncms.org. I plan to use it via emonpi. But when I connect to the emonpi I get this:

No clock yet: SD initialized.
11/2/17 16:37:52 Real Time Clock is running. Unix time: 1509640672
11/2/17 16:37:52 Power failure detected.
11/2/17 16:37:52 Version: 02_02_21
11/2/17 16:37:52 Reset reason: External System
11/2/17 16:37:52 Trace: 20505,5269,12243,32968,36637,5400,26315,28396,15967,9497,60259,34319,24101,9750,19261,29367,55283,37432,56191,23425,33267,22473,49067,20558,32582,22873,47312,45445,24397,25098,44240,47272
11/2/17 16:37:52 ESP8266 ChipID:123456
11/2/17 11:37:52 device name: IotaWatt, version: 3
11/2/17 11:37:52 Local time zone: -5
11/2/17 11:37:55 Connecting with WiFiManager.
11/2/17 11:38:00 MDNS responder started
11/2/17 11:38:00 You can now connect to http://IotaWatt.local
11/2/17 11:38:00 HTTP server started
11/2/17 11:38:00 dataLog: service started.
11/2/17 11:38:00 dataLog: Last log entry:1509599900
11/2/17 11:38:00 statService: started.
11/2/17 11:38:00 timeSync: service started.
11/2/17 11:38:00 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/2/17 11:38:05 EmonService: started.url: emonpi.localdomain/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/2/17 11:38:05 EmonService: Start posting from 1509590580
11/2/17 11:38:05 EmonService: GET failed. HTTP code: read Timeout
11/2/17 11:38:35 Resending EmonCMS data.
11/2/17 11:38:35 EmonService: GET failed. HTTP code: read Timeout
11/2/17 11:39:35 Resending EmonCMS data.

 

This is the Setup Web Server:


 

I looked the the ALPHA updates but I may have missed the fix. I am currently running 02_02_21.

So how do I talk to the emonPi?

That’s normal for 02_02_21. There are some communication timeouts (more on that later) but it is resending successfully. You should see 100% of the data

delivered to Emoncms. Newer versions will not log single comm events that are successfully retried.

The read Timeout seems to be a catchall for anything that causes the communication to fail. So it could be any number of things. In addition, it could be that your Pi just doesn’t respond within 500ms. Glyn assures me that won’t be the case, as the Pi is faster than Emoncms at handling these post transactions.

So one of the first things you might try, is seeing if you can send a post to your Pi using the URL provided.

http://emonpi.localdomain/emoncms/feed/list?apikey=<your-api-key>

and also the same transaction substituting the local IP address of your Pi for emonpi.localdomain

You should get the familiar feed list page.
If that works, you may want to wait until this is resolved.

I have a Pi coming so I can test it directly. You can also accept the update I will be pushing out later today or tomorrow on update-class ALPHA. That will increase the timeout on retries and I’d be curious if it solves your problem.

Seems to work OK. The only odd part is I must be logged in to the emonPi to see the correct Feed list. Same results when sent to IP address.

A better test for CSV:
http://emonpi.localdomain/emoncms/input/post?node=myTestNode&csv=400,500,600&apikey=<your-api-key>

or a better test for JSON:
http://emonpi.localdomain/emoncms/input/post?node=myTestNode&fulljson={“power1”:100,“power2”:200,“power3”:300}&apikey=<your-api-key>

Both the CSV and JSON don’t care if I am logged in or not.

I didn’t know if you were using CSV or JSON to send from the IoTaWatt to the emonPi (or emoncms.org).

Is there a debug mode for the iotawatt to see more info in the logs? I’d like to see what IoTaWatt is sending and what the actual emonPi response is.

That’s not the transaction I’m using. It’s input/bulk. I just gave you that because it’s easy to enter and proves the same thing - that the host and path are correct.

No. But I bet there is something available on the Pi side. I’ll be looking for that when I get my test unit.

Test unit is on it’s way :slight_smile:

1 Like

Thanks Glyn,

These communications issues don’t seem to be epidemic, and I think are proving to be a testament to the IoTaWatt’s ability to persevere through trying times and recover completely. There are a couple of folks out there that are taking their unit apart and getting themselves into trouble, but it’s manageable. I’m learning. There are the users who want a toy to take apart and fool around with, and there are those that want a reliable instrument. Hopefully, the reliable instrument virtue will eventually win out.

1 Like

Indeed, that’s the beauty of open-source. It’s fantastic that users are able to customise the unit in whatever way they want. Obviously our support efforts and finite and should be focused on the later group who are using the unit ‘as is’.

I did an update and received 02_02_23.

From what I can tell, it seems like the iotawatt is sending the same string over & over again, and the data is being received by the emonPi but a timeout happens and I get errors:

11/3/17 15:43:59 EmonService: GET failed. HTTP code: read Timeout
11/3/17 15:44:59 Resending EmonCMS data.
11/3/17 15:44:59 EmonService: GET failed. HTTP code: read Timeout

** Restart **

No clock yet: SD initialized.
11/3/17 20:45:46 Real Time Clock is running. Unix time: 1509741946
11/3/17 20:45:46 Power failure detected.
11/3/17 20:45:46 Version: 02_02_21
11/3/17 20:45:46 Reset reason: Power on
11/3/17 20:45:46 Trace: 55577,5269,12275,32968,34589,21784,20171,28396,15965,8472,60259,33295,24357,10006,2365,25268,63483,37496,56191,6273,33267,30409,49035,53318,32606,23385,47312,45445,24397,16906,44248,47272
11/3/17 20:45:46 ESP8266 ChipID:451998
11/3/17 15:45:46 device name: IotaWatt, version: 3
11/3/17 15:45:46 Local time zone: -5
11/3/17 15:45:49 Connecting with WiFiManager.
11/3/17 15:45:53 Updater: Update from 02_02_21 to 02_02_23
11/3/17 15:46:04 Updater: Update downloaded and signature verified
11/3/17 15:46:08 Updater: firmware upgraded to version 02_02_23
11/3/17 15:46:08 Firmware updated, restarting

** Restart **

No clock yet: SD initialized.
11/3/17 20:46:15 Real Time Clock is running. Unix time: 1509741975
11/3/17 20:46:15 Version: 02_02_23
11/3/17 20:46:15 Updater: Installing update files for version 02_02_23
11/3/17 20:46:15 Updater: Installing CNFSTYLE.CSS
11/3/17 20:46:15 Updater: Installing GRAPH.HTM
11/3/17 20:46:15 Updater: Installing GRAPH.JS
11/3/17 20:46:15 Updater: Installing INDEX.HTM
11/3/17 20:46:16 Updater: Installing TABLES.TXT
11/3/17 20:46:16 Updater: Installing EDIT.HTM
11/3/17 20:46:16 Updater: Installation complete.
11/3/17 20:46:16 Reset reason: Software/System restart
11/3/17 20:46:16 Trace: 130,131,132,133,134,135,136,137,138,139,60259,33295,24357,10006,2365,25268,63483,37496,56191,6273,33267,30409,49035,53318,32606,23385,47312,45445,24397,16906,44248,47272
11/3/17 20:46:16 ESP8266 ChipID:451998
11/3/17 15:46:17 device name: IotaWatt, version: 3
11/3/17 15:46:17 Local time zone: -5
11/3/17 15:46:19 MDNS responder started
11/3/17 15:46:19 You can now connect to http://IotaWatt.local
11/3/17 15:46:19 HTTP server started
11/3/17 15:46:19 dataLog: service started.
11/3/17 15:46:19 dataLog: Last log entry:1509741930
11/3/17 15:46:19 statService: started.
11/3/17 15:46:19 timeSync: service started.
11/3/17 15:46:19 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/3/17 15:46:24 EmonService: started.url: 192.168.60.230/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/3/17 15:46:24 EmonService: Start posting from 1509666750
11/3/17 15:46:24 EmonService: GET failed. HTTP code: read Timeout
11/3/17 15:46:54 Resending EmonCMS data.
11/3/17 15:46:54 EmonService: GET failed. HTTP code: read Timeout
11/3/17 15:47:54 Resending EmonCMS data.
11/3/17 15:47:54 EmonService: GET failed. HTTP code: read Timeout
11/3/17 15:48:54 Resending EmonCMS data.

 

The same data string gets resent (maybe forever):

11/3/17 16:13:54 Resending EmonCMS data.
time=1509666760&data=[[0,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[10,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[20,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[30,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[40,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[50,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[60,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[70,"IotaWatt",123.2,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[80,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[90,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[100,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[110,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[120,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[130,"IotaWatt",123.5,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[140,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[150,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[160,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[170,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[180,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[190,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0]]
11/3/17 16:13:54 EmonService: GET failed. HTTP code: read Timeout
11/3/17 16:14:54 Resending EmonCMS data.
time=1509666760&data=[[0,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[10,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[20,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[30,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[40,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[50,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[60,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[70,"IotaWatt",123.2,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[80,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[90,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[100,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[110,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[120,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[130,"IotaWatt",123.5,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[140,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[150,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[160,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[170,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[180,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[190,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0]]
11/3/17 16:14:54 EmonService: GET failed. HTTP code: read Timeout
11/3/17 16:15:54 Resending EmonCMS data.
time=1509666760&data=[[0,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[10,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[20,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[30,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[40,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[50,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[60,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[70,"IotaWatt",123.2,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[80,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[90,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[100,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[110,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[120,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[130,"IotaWatt",123.5,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[140,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[150,"IotaWatt",123.3,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[160,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[170,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[180,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[190,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0]]
11/3/17 16:15:54 EmonService: GET failed. HTTP code: read Timeout

and if I delete the Inputs from the emonPi Inputs web page, they get recreated during the next resend.

It almost seems like the timeout is being ignored and the iotawatt is missing the “ok” from the emonPi. The OK seems to be sent about 400 to 700 ms after the data string is sent (using the data string above).

A small bulk data string time=1509666760&data=[[0,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0],[10,"IotaWatt",123.4,0,0,0,0,0,0,0,0,0,0,0,0,0,0] takes 40 to 70 ms to respond with an “ok”.

I was publishing the release as you were posting.

That’s exactly what’s happening. IotaWatt is trying to recover from the communication problem. It is a synchronous data update procedure to insure everything gets sent and accepted. Hopefully, 24 will succeed and if it does, all of the backlogged data will be uploaded.

Right, that’s what Emoncms does. If you send input data and the input doesn’t exist, it creates it.

The timeout is 500ms.

That would be a new twist on the problem. I’m not ruling anything out.

UPDATE: You should receive 02_02_24 within an hour, or if you restart it will update right away.

got it! It seems like the same type of issue except the resend happens every 5 seconds.

11/3/17 16:43:49 Connecting with WiFiManager.
11/3/17 16:43:52 Updater: Update from 02_02_23 to 02_02_24
11/3/17 16:44:03 Updater: Update downloaded and signature verified
11/3/17 16:44:10 Updater: firmware upgraded to version 02_02_24
11/3/17 16:44:10 Firmware updated, restarting

 ets Jan  8 2013,rst cause:1, boot mode:(3,1)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v00000000
@cp:0
     ld

** Restart **

Serial Initialized
No clock yet: SPI started.
No clock yet: SD initialized.
11/3/17 21:44:18 Real Time Clock is running. Unix time: 1509745458
11/3/17 21:44:18 Version: 02_02_24
11/3/17 21:44:18 Updater: Installing update files for version 02_02_24
11/3/17 21:44:18 Updater: Installing EDIT.HTM
11/3/17 21:44:18 Updater: Installing GRAPH~1.JS
11/3/17 21:44:18 Updater: Installing GRAPH.HTM
11/3/17 21:44:19 Updater: Installing INDEX.HTM
11/3/17 21:44:19 Updater: Installing TABLES.TXT
11/3/17 21:44:19 Updater: Installing CNFSTYLE.CSS
11/3/17 21:44:19 Updater: Installation complete.
11/3/17 21:44:20 Reset reason: Software/System restart
11/3/17 21:44:20 Trace: 130,131,132,133,134,135,136,137,138,139,60259,33359,16167,10006,2365,25278,57339,37436,56191,4257,49651,30665,49051,55374,65374,6993,48336,45445,24397,16906,44248,47272
11/3/17 21:44:20 ESP8266 ChipID:451998
11/3/17 16:44:20 device name: IotaWatt, version: 3
11/3/17 16:44:20 Local time zone: -5
11/3/17 16:44:22 MDNS responder started
11/3/17 16:44:22 You can now connect to http://IotaWatt.local
11/3/17 16:44:22 HTTP server started
11/3/17 16:44:22 dataLog: service started.
11/3/17 16:44:22 dataLog: Last log entry:1509745415
11/3/17 16:44:22 statService: started.
11/3/17 16:44:22 timeSync: service started.
11/3/17 16:44:22 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/3/17 16:44:27 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/3/17 16:44:27 EmonService: Start posting from 1509666750
EmonService: GET failed. HTTP code: read Timeout
Zero sample voltage
EmonService: GET failed. HTTP code: read Timeout
EmonService: GET failed. HTTP code: read Timeout
EmonService: GET failed. HTTP code: read Timeout

 

The 40 to 70 ms was measured via Firefox Web Dev (Network > Timings) with me sending the small data string via the firefox browser. I was just curious how fast or slow the emonPi responded.

things just got odder more interesting…

after LOTS of timeout errors, I got a adjusting RTC message and data seems to be on the emonPi! :smiley:

and the GET failed. HTTP code: read Timeout errors stopped!

EmonService: GET failed. HTTP code: read Timeout
EmonService: GET failed. HTTP code: read Timeout
11/3/17 17:00:00 timeSync: adjusting RTC by -2

1 Like

I suspect 02_02_24 updated to your IotaWatt. Can you verify that all of the historical data has been uploaded?

This isn’t what I consider a permanent fix, but it’s success suggests I’m on the right track. There are probably still timeouts happening, but the first isn’t logged and the resend has a longer timeout.

If you are not using the data real-time, it would be good to set bulk send to 3 or more on the IotaWatt to aggregate updates into fewer longer transactions.

Sorry I cannot. I had not created a Log to Feed yet.
 

the resend has a very short timer in 02_02_24. It was resending every 5 seconds from 16:44:27 until 17:00:00. At 17:00 the iotawatt starting communicating with the emonPi (and then no more resends!).
 

I will give it a try!

I think you probably updated at 16:44 (that will be in the message log). The prior release would resend after 30 seconds, but with the same 500ms timeout. After the upgrade, the first resend is after 5 seconds, with a longer timeout so the large bulk update was processed successfully, which is what you were seeing. It apparently took 15 minutes to upload your backlog to current and appear on your dashboard. If you could post your log from the update to present it would be helpful in understanding the timing.

Here’s the log from the Web UI Message Log:
2017-11-03 - Web UI Message Log.txt (2.4 KB)
 

Here’s the serial.print output:
2017-11-03 - Serial.print output.txt (11.5 KB)

Thx. It appears to have uploaded almost 22 hours of data, and seems to be working OK now.

To restart I have been unplugging the power cord. This just seems like a bad way to do a restart. I feel like I could easily corrupt the SD card if I power down during a SD write.

Is there a reboot / restart / shutdown type command?!?

I plan to put a toolbox in the config app with a restart button, but in the meantime you can just send:

iotawatt.local/command?restart=yes

As it happened, your IotaWatt did it’s hourly update check a couple of minutes after I updated ALPHA=02_02_24, so it did the update then, before I even told you about it.

1 Like

Perfect! Thank you!

You really did an excellent job on the IoTaWatt. Very nice, well thought out package. I really like the calibration for the voltage section. I had to use a generic AC-AC transformer (still waiting for the real one to arrive). And the voltage side was very simple to set! Nice work overall! Thank you for your many months of effort!

2 Likes

02_02_24 seems to be working very well!
 

Bulk set to 6 now. I get a few more EmonService: GET failed. HTTP code: read Timeout, but the messages may be related to something else.
 

I am curious: what does Zero sample voltage mean?

 

here is the current serial.print output:

** Restart **

Serial Initialized
No clock yet: SPI started.
No clock yet: SD initialized.
11/4/17 22:02:08 Real Time Clock is running. Unix time: 1509832928
11/4/17 22:02:08 Version: 02_02_24
11/4/17 22:02:08 Reset reason: Software/System restart
11/4/17 22:02:08 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/4/17 22:02:08 ESP8266 ChipID:451998
11/4/17 17:02:08 device name: IotaWatt, version: 3
11/4/17 17:02:08 Local time zone: -5
11/4/17 17:02:11 Connecting with WiFiManager.
11/4/17 17:02:16 MDNS responder started
11/4/17 17:02:16 You can now connect to http://IotaWatt.local
11/4/17 17:02:16 HTTP server started
11/4/17 17:02:16 dataLog: service started.
11/4/17 17:02:16 dataLog: Last log entry:1509832925
11/4/17 17:02:16 statService: started.
11/4/17 17:02:16 timeSync: service started.
11/4/17 17:02:16 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/4/17 17:02:21 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/4/17 17:02:21 EmonService: Start posting from 1509832900
[Connected]
11/4/17 17:04:09 Connecting with WiFiManager.
11/4/17 17:04:14 MDNS responder started
11/4/17 17:04:14 You can now connect to http://IotaWatt.local
11/4/17 17:04:14 HTTP server started
11/4/17 17:04:14 dataLog: service started.
11/4/17 17:04:14 dataLog: Last log entry:1509832940
11/4/17 17:04:14 statService: started.
11/4/17 17:04:14 timeSync: service started.
11/4/17 17:04:14 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/4/17 17:04:19 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/4/17 17:04:19 EmonService: Start posting from 1509832940
Zero sample voltage
Zero sample voltage
Not found: GET, URI: /favicon.ico
Upload: START, filename: config.txt
Upload: WRITE, Bytes: 1946
Upload: END, Size: 1946
Zero sample voltage
Zero sample voltage
EmonService: GET failed. HTTP code: read Timeout
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
EmonService: GET failed. HTTP code: read Timeout
Zero sample voltage
11/5/17 01:00:00 timeSync: adjusting RTC by -2
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
EmonService: GET failed. HTTP code: read Timeout
EmonService: GET failed. HTTP code: read Timeout
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage
Zero sample voltage