Uploading OptiSmart 'dAtA' channel to COSM help
I have an EnviR connected to a HAH. It has nothing paired except a single OptiSmart to Ch9. The problem is I cant seem to get this data to post to COSM. Can anyone give me any pointers?
The temp chnnel is updating OK, so I know the HAH can see the EnviR and get data from it.
If you use xfXViewer (or xap-snoop on the HAH), do you see the messages containing the info from your EnviR unit?
Derek
I've got a CC IAM configured as sensor 2.
using xap-snoop, I see:
xap-header
{
v=12
hop=1
uid=FF00DC0E
class=xAPBSC.info
source=dbzoo.livebox.CurrentCost:sensor.2
}
input.state
{
state=on
text=2
displaytext=2 Watts
}
Your CC sensor configuration on the HAH looks to be the same as mine, you really just need to make sure that it's an analogue channel.
Did you try following the troubleshooting notes at http://www.dbzoo.com/livebox/xap_currentcost#troubleshooting
Perhaps inspect the XML feed and see if the 'sensor' data is actuall being sent.
Derek.
I've found that my CC readings are not accurate as well I use the clamps and they really aren't that accurate I've fixed this (within a few percent) using custom rules applied to my PV Output account which adds or subtracts a percentage based on wattage bands and now my readings match my end of day meter generation totalas said within a few percent
I do think if you want accuracy to be within 1% you are not going to get it with current cost device.
you will get it with an item costing 10X the cost.
current cost is an excellent device for "indication" and it is pretty good but to expect it to be 99% accurate is being hopeful.
sorry if this sounds a rant its not meant to be but you get what you pay for.
Dean
Hi,
Without you pasting your pachube settings its a little hard to tell, but maybe the following can help:
xAP source for whole house should be: dbzoo.livebox.CurrentCost:ch.1
whereas a sensor (one of the other channels) would be dbzoo.livebox.CurrentCost:sensor.<n> where n is 1-? e.g dbzoo.livebox.CurrentCost:sensor.1
You are generally trapping latest value changes, so class should be xAPBSC.event, and its an input.state for xAP section and its the 'text' attribute to get the value.
You MUST have set the ID up in your feed already and it must be writeable.
You may not see data for a few mins, so wait a while before checking your graphs in cosm.
--andy