Information received in an email from Current Cost:

1) Yes, the data is sent from the transmitter every 6 seconds. It’s an instantaneous reading taken every six seconds.

\

2) The device doesn’t store at 6 second resolution:-

\

The daily sectors are

\

11pm-7am         night

7am-3pm          day

3pm-11pm        evening

\

The last 31 days Energy Usage is output as 2-hour aggregates of KWHr (3720

values covering 9 Appliances plus Whole House),

the data being aggregated starting at odd hours, eg 23:00 to 01:00, 01:00 to

03:00 etc. This accommodates industry requests

to view evening and night data segments distinguished at 23:00.

\

The last 90 days Energy Usage is output as daily aggregates of KWHr (900

values covering 9 Appliances plus Whole House).

\

For simplicity, this data overlaps the 2-hr history store in the present

version.

\

The last 84 months Energy Usage is output as monthly aggregates of KWHr (840

values covering 9 Appliances plus Whole House).

\

For simplicity, this data overlaps the 2-hr and Daily history stores in the

present version

\

So the day periods do not start at 00.00, but at 23.00

\

The monthly data is simplified into periods of 30 days regardless of the

month.

\

I hope this helps you.

Chris Dalby’s blog states that the Bridge only sends data every 5 minutes.

Current Cost uses Pachube for its backend data management{#internal-source-marker_0.491703259373784}

XML details:\ http://www.currentcost.com/cc128/xml.htm\ \ A Perl script for logging data to MySQL: http://www.brassedoff.net/wp/?p=752