Re: X10 Connector and BSC

["hiller131" <hiller131@xxxxxxxxx>]

Edward and Kevin,

Thanks for the help. The connector apparently requires numbering the
blocks. The first thing I did when I got home last night was adding a
.1 to the block and the connector saw it...needless to say I was a
happy man. Thank you for the suggestion as I had been fighting this
issue for a few days.

The XLobby plugin works great. The way it was created makes it very
flexable, something the one I had started was not. I'm very glad that
Pierre was able to create a plugin that so many can enjoy.

Steve


--- In xap_automation@xxxxxxx, "Edward Pearson"
<edward.mailgroup@b...> wrote:
> Kevin may well be correct here but I'm not near my development
machine to
> check it out. In-house I always send the connector numbered output
blocks
> even if there's only one
>
> xap-header
> {
>     v=12
>     hop=1
>     uid=FFABCD00
>     class=xAPBSC.cmd
>     source=KCSoft.X10ControlPanel.baltic
>     target=ERSP.X10.pacific:workroom.desklights
> }
> output.state.1
> {
>     id=*
>     state=On
>     level=30%
> }
>
> I'll check the code tomorrow to see how this is dealt with. It
probably uses
> the xFx methods that deal with message block arrays so does whatever
that
> implements. Steve, could you try the numbered block please to see if
this is
> what is holding you up.
>
> Edward
>
>
> ________________________________
>
> From: xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
> On Behalf Of Kevin Hawkins
> Sent: 24 May 2005 14:18
> To: xap_automation@xxxxxxx
> Subject: Re: [xap_automation] Re: X10 Connector and BSC
>
>
> Just a quick thought - before I even try and see if it works..
>
> Try changing the boby section name to output.state.1  instead of
> output.state
>
> We don't allow multiple blocks of the same name so to allow multiple
> devices to be addressed in one message we use several blocks named
>
> output.state.1
> output.state.2
> output.state.3  etc
>
> most BSC implementations also allow a single block called output.state
> to work too but maybe Edwards' doesn't.  I think maybe Pierre in his
> XLobby implementation is sending output.state maybe (?)  ...
>
> I am assuming the television is on a binary ONOFF module eg an
> appliance module and also as the current state shows as ? it means no
> X10 commands have been sent to that module (so the state is
unknown). As
> the standard schema is working I think the CM11U/12U connection is
proven.
>
> Kevin
>
> hiller131 wrote:
>
> >Kevin,
> >
> >Thanks for the reply. Here is a BSC info message from the
Connector:
> >
> >xap-header
> >{
> >    v=12
> >    hop=1
> >    uid=FF182001
> >    class=xAPBSC.info
> >    source=ERSP.X10.STEVE:LivingRoom.Television
> >}
> >output.state
> >{
> >    state=?
> >    displaytext=Info: Living room television state unknown
> >}
> >
> >Here is an example of what I am trying to send. This may not be
exact,
> >as I am not on the same machine right now but it should give you
an
> >idea.
> >
> >xap-header
> >{
> >    v=12
> >    hop=1
> >    uid=FF987600
> >    class=xAPBSC.cmd
> >    source=Hiller.Send.Test
> >    Target=ERSP.X10.STEVE:LivingRoom.Television
> >}
> >output.state
> >{
> >    id=*
> >    state=on
> >}
> >
> >I have tried playing with the * and > wildcards in the target
and on
> >the id and can't seem to get the connector to respond. I'm sure
I'm
> >missing something very simple but I just can't find it at the
moment.
> >The actual source will end up being the XLobby xAP plugin but I
> >thought I would test with the Send Program and get the connector
> >working first.
> >
> >Thanks,
> >Steve
> >
> >
> >
> >--- In xap_automation@xxxxxxx, Kevin Hawkins <lists@u...>
> >wrote:
> >
> >
> >>Hi Steve,
> >>
> >>    It may be easier if you could post a copy of a BSC message
that
> >>
> >>
> >the
> >
> >
> >>connector sends and then I will construct a BSC message to
command
> >>
> >>
> >it to
> >
> >
> >>change state. If you are running the correct version you will
be
> >>
> >>
> >seeing
> >
> >
> >>messages of class xAPBSC being sent   (xAPBSC.info,
xAPBSC.event)
> >>    So...run the application and change the state of an X10
device
> >>
> >>
> >by
> >
> >
> >>sending it an X10 command from something.  In xAP Viewer you
will
> >>
> >>
> >see a
> >
> >
> >>corresponding xapBSC.event message coming from the application
each
> >>
> >>
> >time
> >
> >
> >>the device changes state. If you paste one of these to the
list
> >>
> >>
> >here I
> >
> >
> >>will use the address information in that to post the
appropriate
> >>
> >>
> >command
> >
> >
> >>message.
> >>
> >>    Kevin
> >>
> >>hiller131 wrote:
> >>
> >>
> >>
> >>>Hey everyone,
> >>>
> >>>I reciently downloaded the X10 connector again and tried
to send
> >>>
> >>>
> >BSC
> >
> >
> >>>messages to it but was unable to have the connector see
the
> >>>
> >>>
> >messages.
> >
> >
> >>>I downloaded the GUI connector from Edward's site so I'm
pretty
> >>>
> >>>
> >sure
> >
> >
> >>>it's the newest version. Could someone post a known
working message
> >>>that I could copy into a text file for testing with
> >>>
> >>>
> >xAPSendMessage? I
> >
> >
> >>>can send old schema style messages to the connector and it
works
> >>>
> >>>
> >fine...
> >
> >
> >>>Thanks,
> >>>Steve
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>Yahoo! Groups Links
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> ________________________________
>
> Yahoo! Groups Links
>
>
> *	To visit your group on the web, go to:
> 	http://groups.yahoo.com/group/xap_automation/
>
> *	To unsubscribe from this group, send an email to:
> 	xap_automation-unsubscribe@xxxxxxx
> <mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe>
>
> *	Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/>
.