Release of build 250 - important read the notes on this build

Major update

• BSC compliance changes to xap-livebox and xap-currentcost.
• Setting LCD message via web interface now generates a BSC event.
• 1-wire data value change generates a BSC event.

NOTE: This firmware update will break your existing xap-pachube web setting for monitoring the temperature values from 1-wires devices and the xap-currentcost.

Here is how a 1-wire temperate event now looks:

xAP-header
{
v=12
hop=1
uid=FF00DB0A
class=xAPBSC.event
source=dbzoo.livebox.Controller:1wire.1
}
input.state
{
state=on
text=21.0
displaytext=Inside 21.0
}

Previously, that is pre build 250, the temperature value was only emitted as an BSC INFO message using an invalid state= tag.  When it should have been an event when a change is detected as well as the periodic INFO message. Here's how it use to look:

xAP-header
{
v=12
hop=1
uid=FF00DB0A
class=xAPBSC.info
source=dbzoo.livebox.Controller:1wire.1
}
input.state
{
state=21.0
}

This is in violation of the BSC specification.  A state= tag should only contain on/off or ?.  As a result the value has been moved into a text= tag.  In addition if a label has been assignedto the 1wire device, via the webserver interface, this will be shown in the displaytext= tag.

The xap-pachube wiki section has been updated to reflect this change.

Firmware update Instructions

Build 250 is svn release r40