02_03_20 ALPHA PVoutput development

Incorporate changes in PVoutput support from first round ALPHA.
Support now uploads only live data, eliminating issues with separate daily output uploads. Daily outputs are automatic with live data uploads.

Fantastic work.

I am having problem with my unit sending to pvoutput.
The settings are set and the key and systemid is correct.
I have Voltage as chan 1 and Generatation as chan 2

However i get “PVoutput: Fatal response” Any ideas? Any way to get more info in the logs?

Thanks

SD initialized.
12/16/18 03:06:31z Real Time Clock is running. Unix time 1544929591 
12/16/18 03:06:31z Version 02_03_20
12/16/18 03:06:31z Reset reason: Software/System restart
12/16/18 03:06:31z Trace:  1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1[8], 1:2[9], 9:0[9], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 10:2, 10:3
12/16/18 03:06:31z ESP8266 ChipID: 7592809
12/16/18 03:06:31z SPIFFS mounted.
12/16/18 14:06:32 Local time zone: +11:00
12/16/18 14:06:32 device name: IotaWatt
12/16/18 14:06:32 MDNS responder started for hostname IotaWatt
12/16/18 14:06:32 LLMNR responder started for hostname IotaWatt
12/16/18 14:06:32 HTTP server started
12/16/18 14:06:32 timeSync: service started.
12/16/18 14:06:33 statService: started.
12/16/18 14:06:33 dataLog: service started.
12/16/18 14:06:33 dataLog: Last log entry 12/16/18 14:27:25
12/16/18 14:06:33 historyLog: service started.
12/16/18 14:06:33 historyLog: Last log entry 12/16/18 14:27:00
12/16/18 14:06:39 Updater: service started. Auto-update class is NONE
12/16/18 14:06:39 WiFi connected. SSID=HWireless, IP=192.168.30.110, channel=1, RSSI -69db
12/16/18 14:06:42 PVoutput: started
12/16/18 14:06:42 PVoutput: Fatal response 
12/16/18 14:06:42 PVoutput: Stopped.
12/16/18 14:29:28 timeSync: adjusting RTC by 1376
12/16/18 15:29:28 timeSync: adjusting RTC by 3600

First impression is this looks like a communications failure of some sort. I’m looking at the two time corrections. That’s should not happen and indicates a problem communicating with the network time servers.

I looked at that error code and there is a potential problem with the message content. I’ll fix that but for now, you would get an additional diagnostic line if the IoTaWatt were connected to a serial monitor (115,200 baud) through the USB port. I typically use putty to do that.

I’m not following the “Chan 1” and “Chan 2” that you describe. Could you post the PVoutput configuration display?

Hi Bob,

User error…

12/17/18 18:19:57 PVoutput: started
12/17/18 18:19:57 PVoutput: Fatal response
Unauthorized 401: Disabled API Key
12/17/18 18:19:57 PVoutput: Stopped.

Enabled API access but must have forgot to hit save.
And I meant Input not Chan.

Now uploading data and all working well.
:smiley:

Thanks,
I’ll fix the error handling for that case.

I’ve created a team in PVOutput called Iotawatt.com

For those of us using iotawatt and uploading to PVOutput, feel free to join this team and help promote this fantastic product

2 Likes