Differences

This shows you the differences between two versions of the page.

--- livebox:pachube [2012/05/26 17:01]
brett
+++ livebox:pachube [2013/06/17 06:13] (current)
brett [xAP Xively]
@@ Line 1: / Line 1: @@
-====== xAP Pachube ======
+====== xAP Xively ======
-{{:livebox:pachube_logo.jpg }} So that the data being collected by the Livebox can be graphed, shared or used to trigger other real world events we use [[http://www.pachube.com|pachube]] - which people in the know pronounce 'pach-bay', but sound much cooler as 'pa-chu-be'. {{ :livebox:cosm.jpg|}}
+[[wp>Xively]] (formerly Cosm and before that Pachube (pronounced Patch bay)) is an online database service.\\  We use Xively to log data collected from the Sensors attached to the HAH system.
-The xap-pachube daemon has been designed to feed any xAP event that appears on the bus to pachube.  This means the Livebox hardware plus any other xAP compliant software/device that you may have running elsewhere on your network.
+{{:livebox:pachube_logo.jpg}} {{:livebox:cosm.jpg}} {{:livebox:xively.png}}
+The xap-xively daemon has been designed to feed any xAP event that appears on the bus to Xively.  This means the Livebox hardware plus any other xAP compliant software/device that you may have running elsewhere on your network.
 This daemon is configurable via the webserver interface\\
-{{:livebox:pachube-screen.jpg|}}
+{{:livebox:xively-screen.jpg}}
-Once you have a PACHUBE account you will get a unique KEY. This must entered into the interface so that trust is formed between the Livebox and the service.  You will then need to create a FEED ID.  Here is my data collected on Pachube: http://www.pachube.com/feeds/1892
+Once you have a XIVELY account you will get a unique KEY. This must entered into the interface so that trust is formed between the Livebox and the service.  You will then need to create a FEED ID.
-The Max and Min values are used by pachube to perform graph scaling along with the Unit field to annotate the datastream.
+The Max and Min values are used by xively to perform graph scaling along with the Unit field to annotate the datastream.
 ===== Sample mapping =====
-The pachube parameters
+The xively parameters
   * **source** - dbzoo.livebox.Controller:1wire.1
   * **class** - xAPBSC.event
@@ Line 37: / Line 39: @@
 </code>
-xap-pachube can also handle a ON/OFF value and this will be automatically convert to a 1/0 so the numeric value can be logged, this is handy for relays, rf, and other boolean input/output devices.
+xap-xively can also handle a ON/OFF value and this will be automatically convert to a 1/0 so the numeric value can be logged, this is handy for relays, rf, and other boolean input/output devices.
-The pachube parameters
+The xively parameters
   * **source** - dbzoo.livebox.Controller:relay.1
   * **class** - xAPBSC.event
@@ Line 63: / Line 65: @@
-The PACHUBE dsemon feeds data to the pachube service on a regular basis.
+The XIVELY daemon feeds data to the xively service on a regular basis.
-Its internal cache of data to push to PACHUBE can be updated by xAP messages being targeted at this service.
+Its internal cache of data to push to XIVELY can be updated by xAP messages being targeted at this service.
-Messages sent to it are not immediately forwarded to the PACHUBE service. They wait until the next update cycle.
+Messages sent to it are not immediately forwarded to the XIVELY service. They wait until the next update cycle.
-A Pachube update message looks like this:
+A Xively update message looks like this:
 <code>
 xap-header
@@ Line 76: / Line 78: @@
 hop=1
 uid=FFAADA01
-class=pachube.update
+class=xively.update
-target=dbzoo.livebox.pachube
+target=dbzoo.livebox.xively
 source=dbzoo.acme.test:1
 }
@@ Line 93: / Line 95: @@
 * The value updates the value of the datastream identified by the ID key/field
-The configuration page on the HAH Pachube tab is unaffected
+The configuration page on the HAH xively tab is unaffected
-Note that the UID and source in the message above must either both have subaddresses or neither have sub addresses
+Note that the UID and source in the message above must either both have sub-addresses or neither have sub addresses
 ===== Graphing =====
-With all this data being aggregated we can now graph it\\
+With all this data being aggregated we can now graph it
 {{pachube-temp.PNG}}
-As this data resides on an external server we can ask it to produce a graph for us too.  It can take up to 5 minutes before you have enough history data logged to allow the graphs on the HAH to display.
-<code><img src="http://www.pachube.com/feeds/1892/datastreams/0/history.png?w=320&h=200&t=HAH%20Temperature&b=true&g=true&r=3"/>
- </code>
-<html><img src="http://www.pachube.com/feeds/1892/datastreams/0/history.png?w=320&h=200&t=HAH%20Temperature&b=true&g=true&r=3"/><object width="160" height="210"><param name="allowScriptAccess" value="always" /><param name="movie" value="http://apps.pachube.com/media/pachublog.swf" /><param name="FlashVars" value="feedId=5386&dataId=1&tagName=HAH%20Temperature&unitName=Celcius&lineColour=FF0066" /><embed src="http://apps.pachube.com/media/pachublog.swf" width="160" height="210" allowScriptAccess="sameDomain" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" FlashVars="feedId=1892&dataId=0&tagName=HAH%20Temperature&unitName=Celcius&lineColour=FF0066" /></object></html>