Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TAS 200]

I have just upgraded to a CM15A from an older version. When I programed a macro with appliance and lamp modules, the appliance modules operate properly but the lamp modules do not. If i shut the computer down and reboot, the lamp modules operate properly until I make a change in the program and then they quit.  They can still be operated manually from the computer. It does print a history error  "Extended Code d2 31" While i use mostly appliance modules, I would like for everything to work.  Any suggestions!

[PaulBennett]

Same here and I was about to post for help, saw your problem and found the solution. 

I desire to operate both a appliance module on B4 AND a lamp module on B6 with a sensor A1 in my driveway.  The appliance module worked in the macro which is used simply to translate from hourse code A to modules on B..  The lamp module did't.   I've tried separate macros and combined macros. 

Place a dummy AM14A appliance module in the room.  Use it for the Macro and your regular lamp module for timing/dimming.   Don't ask me to make it dim with the macro...I'm only interested in getting to to turn on  reliably.

My reason for using A1 in the driveway sensor is against the event it gets reset...A1 is the default.  This removes that reliability one concern.  This stuff is less reliable than kid's toys.

[X10 Pro]

Make sure you have selected the right module type in ActiveHome Pro for you lamps. If you are seeing Extended Code commands, you probably have your lamps configured as Two-Way Lamp Modules (LM14A) which don't use the same command set as regular lamp modules (model LM465).

[TAS 200]

The lamp module type was the problem.  I also had a problem with the macro not performing the first operation until I added a one second delay as the first step in the program. Thanks