Fw: Re: Has ANYONE got the Comfort <> Homeseer plug in working ?

["Gareth Cook/UK/IBM" <gcook@xxxxxxx>]

Right - now that my meagre brain has
grasped the concept of the value channging to 1 and then 0 4 seconds later,
I can get that working.

BUT !

I'm using build 152 (build38) and it
works fine. I want to use some scripts that require build 39 or later.
Ive tried build 60 , but the Comfort plugin barfs totally (homeseer exits).
Another build just gives me runtime 13 errors and no more comfort plugin
action occurs (normal homeseer operations continue)

Now I know this isnt my fault !

G.

Gareth Cook Senior Engineering Specialist EMEA ED, IBM SWG 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 12/07/2002 21:59 -----

Discussion
Main Topic

"PatrickLidstone" <patrickl@xxxxxxx>
Today 11:13

.

Subject: .	[ukha_d] Re: Has ANYONE got the Comfort <> Homeseer plug in working ? .
Category:

I missed the start of this thread (hectic life etc). For those who
don't know, I wrote the comfort plug-in.

There have been one or two reports of weirdness - which usually turn
out to be comfort related (it seems very idiosyncratic) - but I know
there are many (tens of) happy users out there.

As I tried to explain to Gareth in e-mail previously, the following
is spot on the money, and is also covered in the docs IIRC.

>   > You do realise that the plugin reports the status of the Zones
as 0
>   > or 1, not as ON and OFF. The Homeseer events do NOT respond when
>   you
>   > are looking for a status of ON or OFF. You need to trigger
events
>   > using the option to check for a change in VALUE.

The reason for this is that sensors can report intermediate values
other than just on and off - although the UCM has limited support for
this at present. The Homeseer API is sufficiently brain dead to be
unable to support the concept of an "On"/"Off" threshold/value - so I
didn't have a choice.

>   > While this works nicely if you're just checking for a change in
>   > value, I can't get it to work if I want a conditional trigger.
e.g.
>   a
>   > change in value AND it's after sunset.
>   >
>   > I hope this helps with your problem. Perhaps someone can help
with
>   > mine?
>   >

If I've understood what you want to achieve, then this is possible
too, I think.

Within Homeseer:

>From Event Properties page, in Description pane, select event "Type"
as "By condition".

The should change the bottom pane to indicate "Trigger when all of
the given conditions are true".

Multiple conditions can then be added through the dialogue.

Gary, I will send you a screen shot when I have access to a decent
net connection.


Patrick