Using a just-purchased CM11A and just-downloaded
version of MisterHouse, all
seems to work well except X-10 commands issued by
CM11A from its internally-
stored timer events do not show up in the logs in
MisterHouse and do not show
indicated in the MH status of X-10 items.
(The controlled devices do however go on and off as
I have a suspicion this is a similar matter as discussed
below, but not sure.
Has anyone resolved this (either the item above or
I am running Windows 98 SE.
From: Charles Sullivan <cwsulliv@tr...>
Re: CM11 consumes x10 signals
> Message: 2
> Date: Fri, 2 Apr 2004 19:12:57 -0600
> From: "Tarah Hofmann" <tarah@am...>
> To: <misterhouse-users@li...>
> Subject: [misterhouse-users] CM11 consumes x10
> Reply-To: misterhouse-users@li...
> Hi All,
> Originally, I programmed my CM11 via activehome and
all of my macros
are "fast". This
serves as a backup plan for motion sensors (e.g. front
door) so the lights
will still come
on even if my linux box with misterhouse is down, which
happens when I "play"
with it. :)
> However, since I started using the OccupancyMonitor
in earnest, I notice
that the signals
for the motion sensors defined in the CM11"s memory
don"t get through to
instance, I"ll see a outside_motion = dark or light signal
in misterhouse, but
motion/still signal if the x10 address for outside_motion
is in the CM11"s
> Has anyone else seen this happen? Thanks in
This is a "feature" of the CM11A. An X10 power line
signal which triggers a
stored in the CM11A"s EEPROM is not reported back to
the system. The only
thing reported is that a macro at EEPROM address NNN
has been executed.
It is possible to reconstruct the signal if the EEPROM
memory image is
in a file, but a MH script would have to be written to do
The latest alpha release of the program "heyu2" (for
does this when it uploads a schedule to the EEPROM.
See: heyu2.alpha-5 at
Log in to post a comment.