The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: "Toggle" command




Hi Mark,

mark_harrison_uk2 wrote:

>I realise that I should already know the answer, but blame this
>message on sleep deprivation for obvious reasons :-)
>
>
First of many such nights I fear..

>Does BSC 1.3 contain a "toggle" command?
>

Yep - in fact it was your suggestion I think ...

> If so, does the CM12U
>connector support it?
>
>
Yes - not sure in which beta release this was implemented  but certainly
the version I have here supports it and this is from a few weeks back
... just checked it. You obviously need the BSC13 version of the X10
connector.  Actually the xAP Desktop faders send a 'toggle' command if
you click on the bulb icon  (although bulb 3 is setup differently by
default to hide the faders).

NB:  From with our experience of using BSC13 that in a xAPBSC.cmd
message to a LEVEL or TEXT device all parameters are optional although
at least one should be present or the command serves no purpose.  In
responses from devices ie xAPBSC.info or xAPBSC.event then all
paramaters are mandatory.  The specification is vague on this issue and
I need to add a clarification statement to the published version.

The reason for this is that you may not for example know in advance the
current LEVEL of a device when you wish to TOGGLE  its STATE - you
simply wish to turn it from ON to OFF or vv, so the requirement to
include LEVEL= is flawed, hence it is now optional. In a simple transmit
only device eg an on/off  lightswitch the switch could never know the
level anyway.

Kevin




xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.