Current Cost Support Forum

Looking on pachube account , channel 9 over a 30 day period, this is what I see.

Anyone else see similar that has registered theie free account at pachube?

https://pachube.com/devices/currentcost

My one is at https://pachube.com/feeds/38455

File comment: Meter Readings

Meter Readings.jpg [ 136.32 KiB | Viewed 56755 times ]


Of course the values should just go slowly up and NEVER down.

Automan.

Saving the XML output and with a few Powershell commands I have save the data for my PV OptiSmart during the hours when no power is generated.

As you will see the pulse count goes up by 6,760 pulses but the watt load on the meter is zero so IMHO the pulse count should have stayed the same?

My MK1 code for splitting the XML up into neat files is...

get-childitem cc_debug.txt | select-string -pattern "<sensor>0</sensor>" | foreach {$_.line} > "cc_debug.000"
get-childitem cc_debug.000 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 0.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>1</sensor>" | foreach {$_.line} > "cc_debug.001"
get-childitem cc_debug.001 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 1.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>2</sensor>" | foreach {$_.line} > "cc_debug.002"
get-childitem cc_debug.002 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 2.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>3</sensor>" | foreach {$_.line} > "cc_debug.003"
get-childitem cc_debug.003 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 3.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>4</sensor>" | foreach {$_.line} > "cc_debug.004"
get-childitem cc_debug.004 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 4.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>5</sensor>" | foreach {$_.line} > "cc_debug.005"
get-childitem cc_debug.005 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 5.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>6</sensor>" | foreach {$_.line} > "cc_debug.006"
get-childitem cc_debug.006 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 6.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>7</sensor>" | foreach {$_.line} > "cc_debug.007"
get-childitem cc_debug.007 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 7.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>8</sensor>" | foreach {$_.line} > "cc_debug.008"
get-childitem cc_debug.008 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 8.txt"

get-childitem cc_debug.txt | select-string -pattern "<sensor>9</sensor>" | foreach {$_.line} > "cc_debug.009"
get-childitem cc_debug.009 | select-string -pattern "<hist>" -NotMatch | foreach {$_.line} > "Sensor 9.txt"

Using http://currentcost.com/software-downloads.html C2 Terminal to save the XML from the USB cable.

Automan.

I should for comparison also shown the same files for my other OptiSmart which is on the house load.

This one for the same period only went up 2,129 pulses and if you look at Sensor 0 you may also spot 5 corruptions to the data format.

Automan.

Has anyone got the optismart meter reading to work on the CC dashboard?

Andy - I took a quick peak at your meter feed on pachube, and I can still see the sawtooth with steps (same as mine) for past 30 days, so I assume it is still not working for you?

CC have suggested changing the channel from 9 to some other channel for 'dAtA'. I will try this and report back.

I guess this still does not work for anyone?

Automan.