RE: Strange Behavior(?) : Minitimer

[Mike Griffiths <mike@xxxxxxx>]

Robin
The mini timers are notorious for sending out weak signals
I ended up putting in a power new ciruit to enable one timer to work in one
room
Rememner tou can also extend the the lead via cat5
Try to place the minitimer mains plug as close to your main control as
possible

I don't think anyone else has come up with a solution
Perhaps that's why they were sold off so cheap :(
Mike



-----Original Message-----
From: Robin Edwards [mailto:robin@xxxxxxx]
Sent: Sun 18 Nov 01 23:13
To: ukha_d@xxxxxxx
Subject: [ukha_d] Strange Behavior(?) : Minitimer


Can somebody with more experience than me please explain what I'm seeing.

I'm using Misterhouse under Mdk, to control a number of items.  I was doing
some tests this morning with an LM15 Bayonet Lamp Module, to set up a new
coding approach for house.   So each room has a seperate house code, and
the

LM15 is A1.

My minitimer (used as alarm clock) is set to housecode M, and an RF unit is
set to housecode N, so when something is triggered from one of these
Misterhouse captures it and does something with it.   Currently M1 and N1
turn A1 on or off. (Sounds overkill but other items go in as well and
Misterhouse logs all actions).

Anyway, the problem:  N1 from the HR10/TM13 turns A1 on and off, M1 is
totally ignored, it does not even spot the code.  So I moved the minitimer
to
another socket and it works fine.  Swapping back to the original socket and
setting minitimer to A it works fine !!  I'm not aware of doing anything
else
to impact what happens other that altering my macro in Misterhouse.  But
Misterhouse does not even see the M1, let alone actions it.

regards, robin



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 http://docs.yahoo.com/info/terms/