[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: xAP X10 BSC Connector v2.5.0 released
------=_NextPart_000_0000_01C51229.29883A80
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
The connector contains an implementation of BSCMapper which can map several
BSC devices to one 'actual' device. There's no UI for the mapper, it's all
driven by xAP messages and can be configured using a xAP Network
Configuration application that I have under development. Since the schema
definitions for mapper (and groups) are still being defined, I turned these
functions off in the release code.
Would such mapping functionality fit your security light setup?
_____
From: Kevin Hawkins [mailto:lists@xxxxxxx]
Sent: 08 February 2005 12:19
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] xAP X10 BSC Connector v2.5.0 released
Edward Pearson wrote:
>A major new version of the xAP Framework X10 Connector is now available
and
>a new xAP location on the web has come into being too
www.erspearson.com.
>
>
>
Hi Edward,
I am now using this new connector, very nice.
One thing I have come across. In your device configuration it isn't
possible to create two devices with the same X10 address and I have a
couple of devices set up this way. I have two external security floods
with different xAP names but both on say F4. Now I realise that I can't
individually address them either via X10 or even xAP if they had
different addresses but it would kind of be nice to have them both
independently sending .event and .info messages. That way if later I did
change one of their X10 address to something unique it would all still
work transparently from xAP. Maybe you could have a 'warn' with
duplicate addresses rather than being non allowable ?
Kevin
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|