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: xAPFloorPlan - chaining X10 commands


  • Subject: Re: xAPFloorPlan - chaining X10 commands
  • From: "JamesTraynor" <james@xxxxxxx>
  • Date: Sat, 09 Sep 2006 23:06:21 -0000

Hi,

The main reason for send a seperate command per device is how the
internals of floorplan work.  Floorplan does have scenes, which are a
recorded preset of device levels, but when a scene is triggered it
does still send individual messages. It would still be upto the
receiver in how it processes a message that contains multiple commands
as some may just process the commands in order rathter than all
together. I am trying to add a process that causes all messages sent
in sequence to be buffered and then combined, but it's not exactly
trivial to do!


Message wise is you had these devices
a.b.c:lights.a   uid ff123401
a.b.c:lights.b   uid ff123402
a.b.c:lights.c   uid ff123403

then the single xAP message to set them all at 50% would be
..
class=xAPBSC.cmd
target=a.b.c:lights.>
}
output.state.1
{
id=01
state=on
level=50%
}
output.state.2
{
id=02
state=on
level=50%
}
output.state.3
{
id=03
state=on
level=50%
}

and in xAP Floorplan code

sub Main()
tmp="output.state.1" & chr(10)
tmp=tmp & "{" & chr(10)
tmp=tmp & "id=01" & chr(10)
tmp=tmp & "state=on" & chr(10)
tmp=tmp & "level=50%" & chr(10)
tmp=tmp & "}" & chr(10)
tmp=tmp & "output.state.2" & chr(10)
tmp=tmp & "{" & chr(10)
tmp=tmp & "id=02" & chr(10)
tmp=tmp & "state=on" & chr(10)
tmp=tmp & "level=50%" & chr(10)
tmp=tmp & "}" & chr(10)
tmp=tmp & "output.state.3" & chr(10)
tmp=tmp & "{" & chr(10)
tmp=tmp & "id=03" & chr(10)
tmp=tmp & "state=on" & chr(10)
tmp=tmp & "level=50%" & chr(10)
tmp=tmp & "}" & chr(10)
xap.sendxap tmp,"xAPBSC.cmd","a.b.c:lights.>"
end sub

hth

James


--- In xap_automation@xxxxxxx, "darrenp_lock"
<darrenlock@...>
wrote:
>
> Hi James,
>
> I should have thought this through a bit more before posting! The
> reason I noticed this behaviour was because prior to using FloorPlan
> I was constructing combined X10 schema messages. By sending an On
> command to a series of devices sharing the same House Code this also
> had the nice side efect that when the Dim/Bright button was pressed
> the lights on that HouseCode would change in unison. I was wondering
> if in FloorPlan we could create psuedo devices where a number are
> grouped together ( a bit like a scene). It might be easier then to
> either work out the logic or provide users with the means to
> determine the behaviour around a simple set of rules.
>
> Thankyou for the advice around scripting. I was going to try this. I
> wasn't sure how to construct a BSC message that would control
> multiple devices together as each device has its own address.
>
> Oh! BTW I use Edwards X10 Connector ( the latest version)
>
> Thanks, Darren.
>
> --- In xap_automation@xxxxxxx, "JamesTraynor" <james@>
> wrote:
> >
> > --- In xap_automation@xxxxxxx, "darrenp_lock"
<darrenlock@>
> > wrote:
> > >
> > > I am using xAPFloorplan and wanted to know how I can chain
> multiple
> > > BSC X10 addresses into a single command.
> > >
> > > I have a State Link that controls multiple lamps (diffrent
> X10/BSC
> > > addreses) but when the Link is triggered it turns each
device on
> in
> > > sequence (Floorplan is sending multiple BSC messages). I
would
> prefer
> > > to have Floorplan to turn these devices on
> > > together if possible. How can I achieve this?
> > >
> > Currently the built in processing of links does just what you've
> > found, sends a .cmd to each device. I'll see what i can do
> internally
> > to group things together.
> > For now you can trigger a script from the link and get that to
> control
> > the lights. Its a little more involved but ultimately flexible.
> >
> > James
> >
>








xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation 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.