|
The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024
|
|
[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: xAP - The Proposed Architecture Explained - some sample input
components
- To: <ukha_d@xxxxxxx>
- Subject: RE: xAP - The Proposed Architecture Explained - some
sample input components
- From: "Kenneth Watt" <kennwatt@xxxxxxx>
- Date: Wed, 14 Aug 2002 10:55:28 +0100
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
> Plugin: HomeVision
> - X-10 trigger received
> - Input port triggered
> - Macro fired
> --- obviously, this would depend on HV schedule
Mark,
Would it not be easier to be able to read a variable in HV/HomeSeer as
well and ditch the temperature reading here?
The reasoning being that in almost all instances anyone would read the
value into their chosen HA controller anyway and this should allow it
to
be read from value that is already there for manipulation at any rate.
It would also be advantageous to see a flag setting, or the HomeSeer
equivalent IMO.
I don't know about you, or anyone else, but a great many things I do
are
dependant on a flag or variable setting and I just think that it would
be better to use those rather than double up info that is already in
HV.
Just a thought
K.
Yahoo! Groups
Sponsor |
ADVERTISEMENT
| |
For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe: ukha_d-subscribe@xxxxxxx
Unsubscribe: ukha_d-unsubscribe@xxxxxxx
List owner: ukha_d-owner@xxxxxxx
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Home |
Main Index |
Thread Index
|
|