OK .. so is there still an on/off issue with xAPBSC.cmd's ?
The button visibility is controllable externally (it presents as an output meaning it can be controlled) but the button state can't be controlled yet as it is presenting as in input.
So you can't currently 'press' a button via xAP. If the button is linked to a xAP device however then you can change that devices state and the button will change it's displayed state.
The level= that is sent inside the state message from a button actually contains the current state out of the 11 currently supported.
TBH There wasn't a real purpose in allowing buttons to be pressed via xAP in beta 5 - but the next beta has a new feature that could make this useful. You are able to add several <xAP><on>/<off> elements within one button so you can create a sequence of commands that control any xAP device - rather like a macro - and being able to trigger this via xAP would be useful.
There are one or two aspects with the BSC messaging in pre beta 5 that can cause large volumes of messages to get sent - this has been honed down a bit in beta 6.