From: Charles S. <cws...@tr...> - 2004-04-03 09:35:16
|
> Message: 2 > Date: Fri, 2 Apr 2004 19:12:57 -0600 > From: "Tarah Hofmann" <ta...@am...> > To: <mis...@li...> > Subject: [misterhouse-users] CM11 consumes x10 signals > Reply-To: mis...@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 misterhouse. For instance, I'll see a outside_motion = dark or light signal in misterhouse, but never a motion/still signal if the x10 address for outside_motion is in the CM11's memory. > > Has anyone else seen this happen? Thanks in advance, > > Tarabyte This is a "feature" of the CM11A. An X10 power line signal which triggers a macro 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 preserved in a file, but a MH script would have to be written to do this. The latest alpha release of the program 'heyu2' (for Linux/Unix/OS X) does this when it uploads a schedule to the EEPROM. See: heyu2.alpha-5 at http://heyu.tanj.com/heyu2 Regards, Charles Sullivan |