Generation data not uploading

[GoogleCodeExporter]

What steps will reproduce the problem?
Uninstalled old version installed new version

What is the expected output? What do you see instead?
Only see consumption data and temp data

What version of the product are you using (e.g. 1.4.1.9 32bit)?
Newest 1.4.2.1

What Operating system (XP, Vista, Windows 7 - 32bit or 64bit)?
Win7

Which Database Type (MySQL, MS Access, SQLite - If Access, 32bit or 
64bit)?SQLite

Attachments provided

Original issue reported on code.google.com by Joesan...@gmail.com on 29 May 2011 at 2:27

[GoogleCodeExporter]

This log shows that you started PVBC just after midday with an old empty 
database.

I say old as you can see PVBC trying to bring the empty database up to the 
latest revision.

PVBC will create an empty MS Access or SQLite database for you (using a recent 
version as the base) if you change settings or use the environment check 
facility while there is no database file present.

Why did you choose to start with an empty database?

I see form your pvoutput that you seem to have it working now. Do you know what 
you did to get it working?

A fault has been reported relating to stc-4002 meters in PVBC (issue 44). It 
will fail when it processes past midnight. A fix is in version 1.4.2.2 
available here:

http://code.google.com/p/pvbeancounter/downloads/list?can=1&q=&colspec=Filename+
Summary+Uploaded+ReleaseDate+Size+DownloadCount

Dennis M-F

Original comment by DennisMackayFisher on 29 May 2011 at 4:24

• Changed state: Started

[GoogleCodeExporter]

I had a play i havent worked out what i did but it seems to have started to 
upload generation but consumption data has now stopped.
Swiched to msaccess databases but same result here as well.

Original comment by Joesan...@gmail.com on 29 May 2011 at 7:16

[GoogleCodeExporter]

Some screen captures of how the gui is setup.

Original comment by Joesan...@gmail.com on 29 May 2011 at 7:37

[GoogleCodeExporter]

The log looks normal except for the pvoutput rejections:

29/05/2011 5:06:58 PM :T3 PVOutput :PVOutputUtilities: SendPVOutputBatch - 
postData: 
data=20110529,16:35,3965,60,22,1143,20.18;20110529,16:40,3968,36,192,3435,20.11 
29/05/2011 5:06:59 PM :T3 PVOutput :PVOutputUtilities: Protocol Error: 
data=20110529,16:35,3965,60,22,1143,20.18;20110529,16:40,3968,36,192,3435,20.11 
Error: Bad request 400: Energy value [192] lower than previously recorded 
value: [8253]  

192 is the new total watt hours number to 16:40

previously you recorded 8253 watt hours in the period up to 16:40

The consumption updates are being rejected by pvoutput because they are lower 
that the values already recorded for 29/05.

This is caused by switching databases. The new database has no record of 
consumption earlier in the day. The data sent to pvoutput is cumulative (total 
up to the data time). I would prefer to just send interval values but pvoutput 
does not support this. The result is that if you loose the data entries for the 
early part of the day, you end up sending consumption data with lower values 
than previously sent and pvoutput will reject it.

This will correct itself at when:
- consumption gets high enough, or 
- a new day starts, or 
- you delete the data at pvoutput for 29/05 and set "Force Live Upload" on and 
set "Live Upload Days" to 1.

Dennis M-F

Original comment by DennisMackayFisher on 29 May 2011 at 8:13

[GoogleCodeExporter]

I deleted the data from pvoutput performed the forced live upload.  It just 
populates what was there no further consumption data or temp data at this 
stage.  Looks like its hit its 60min request limit for now.  Will leave it and 
check it in the morning hopefully it sorts its self out.

Original comment by Joesan...@gmail.com on 29 May 2011 at 10:05

[GoogleCodeExporter]

Loks like its fine now i left it overnight and it seems to be doing the right 
things :)

http://pvoutput.org/intraday.jsp?id=1628&sid=1297&dt=20110530

Thanks again.

Original comment by Joesan...@gmail.com on 30 May 2011 at 12:08

[GoogleCodeExporter]

I saw your post about fixing the data at pvoutput. We seem to have the main 
data update working but I suspect the history update is not working. History 
update should have fixed your data at two hour intervals.

Can you please check "Meter Trace" and "Meter Message" and let it run across an 
odd hour boundary - e.g. 6:45 to 7:15

I would like to see the log file over this period. I want to see what is 
happening to the history data. I suspect further changes are required to get 
history update working.

Dennis M-F

Original comment by DennisMackayFisher on 30 May 2011 at 10:55

[GoogleCodeExporter]

How do you want me to do this just stop the service for a period of time then 
start it again?

Original comment by Joesan...@gmail.com on 30 May 2011 at 12:09

[GoogleCodeExporter]

Not necessary.

Changes to the log settings take effect immediately they are saved. You do not 
need to restart the service.

Dennis M-F

Original comment by DennisMackayFisher on 30 May 2011 at 8:07

[GoogleCodeExporter]

Original comment by DennisMackayFisher on 7 Jun 2011 at 10:45

• Changed state: Fixed

[GoogleCodeExporter]

My Generation data (18/06/2011) not uploading.  Has been working fine the last 
10 days.
Sunrich.

Original comment by richard....@gmail.com on 18 Jun 2011 at 4:04