Fw: Fw: Comfort plugin

[Gareth Cook <g@xxxxxxx>]

How about 1 more option - loggin as is now, but witout x10 rsponses coming
back from comfort - i already know the x10 responses as the x10 computer
interface on the same pc grabs them

G.

Gareth Cook 
Technical Consultant 
IBM Early Deployment
Lotus Park, Staines, TW18 3AG
Office:  +44 (0) 1784 445 166
Mobile:  +44 (0) 7980 445 166
Fax:      +44 (0) 1784 499 166
Work: g@xxxxxxx 
Personal: g@xxxxxxx 
AIM Chat : TheBoyG 
MSN Chat : chat@xxxxxxx 

----- Forwarded by Gareth Cook/UK/IBM on 24/01/2003 15:04 -----

Discussion
Main Topic

"Paul Gordon" <paul_gordon@xxxxxxx>
Today 14:58

.
Subject:
.
RE: [ukha_d] Fw: Comfort plugin
.
Category:




>
>Any teasers on what to expect? Need any help?
>I hope you are going to offer an option to reduce the amount of
logging
>to the the Homeseer Event log ;-)
>
>Michael
>


Michael,

I have already implemented, and mostly tested the following:

1- a multi-level logging option. - a registry entry can be set to control
the level of logging to the Homeseer log. The levels are as follows:

   0 - none, totally silent (Except for a couple at startup)
   1 - normal, standard event logging - same as the current
plugin
   2 - protocol, Serial protocol logging - logs raw serial I/O
details
   3 - maximum, program operation logging - logs internal program
flow

Each level includes the levels below it (so level 3 logs a heck of a
lot!)

2- An option to have the plugin sync the Comfort clock to the PC clock at
every startup.

3- a button on the plugin config dialog to sync the Comfort clock to the
PC 
clock

4- Fixed the error that stopped the "About" box from
displaying.



My remaing item list is as follows:

1- Query the state of the panel on startup & set the Homeseer virtual
devices to the correct arm state, and zone states.

2- Expose a set time device and method to Homeseer so a homeseer event may

set the Comfort RTC. (so you can schedule it to run at whatever frequency
you want...)

3- Retrieve the device strings from Homeseer so that the log shows device
names as well as zone numbers for zone activations.

4- Have the Comfort and UCM firmware levels reported to the Homeseer log
on 
startup.

5- Have the plugin report the phone ring event to Homeseer.

6- Have input zone activations set the Homeseer device STATUS as well as
the 
device VALUE - so that Homeseer events can by trigerred by a "Device
status 
change" condition as well as by a "Device value change"
condition.


That's all I plan to attempt for the time being.... (I'm open to any other

suggestions though...).  After that Patrick (or me if I feel brave!)
will 
fit the xAP component to it...




_________________________________________________________________
Worried what your kids see online? Protect them better with MSN 8 
http://join.msn.com/?page=features/parental&pgmarket=en-gb&XAPID=186&DI=1059



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
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




[Non-text portions of this message have been removed]

Yahoo! Groups Sponsor

ADVERTISEMENT

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
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.