The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Strange Behavior(?) : Minitimer


  • To: ukha_d@xxxxxxx
  • Subject: Strange Behavior(?) : Minitimer
  • From: Robin Edwards <robin@xxxxxxx>
  • Date: Sun, 18 Nov 2001 18:13:20 -0500
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

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



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.