Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| livebox:pachube [2014/11/08 09:27] – [As a Service] brett | livebox:pachube [2014/11/08 09:28] – [As a Service] brett | ||
|---|---|---|---|
| Line 78: | Line 78: | ||
| Its internal cache of data to push to XIVELY 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 XIVELY service. They wait until the next update cycle unless the **now** attribute is supplied, more on that later. | + | Messages sent to it are not immediately forwarded to the XIVELY service. They wait until the next update cycle, unless the **now** attribute is supplied more on that later. |
| A Xively update message looks like this: | A Xively update message looks like this: | ||
| Line 100: | Line 100: | ||
| In the message above | In the message above | ||
| - | * The id= key matches that of the ID field in the datastream for the default Feed ID. | + | |
| - | * The tag=key updates the tag value of the datastream identified by the ID key/field | + | * The tag=key updates the tag value of the datastream identified by the ID key/field |
| - | * The value updates the value of the datastream identified by the ID key/field | + | * The value updates the value of the datastream identified by the ID key/field |
| The configuration page on the HAH xively tab is unaffected | The configuration page on the HAH xively tab is unaffected | ||