Note: I'm a newbie and this is my first post -- and it's a long one! Sorry in advance. This "stuff" is quite infuriating and details count (I hope) Although this post is about my particular issue with the above combination, I know that this problem -- or something similar has been discussed before. However, I chatted with several very helpful people at the Home Automation Chat (
http://bdshost.com/ac/) last night and I promised them (including Bill- (of wgjohns.com) and Knightrider among others) that I'd report back on what I found out as I troubleshot my issue. So, trying to make this as short (but as complete as possible), here we go....
BackgroundI've recently started with my X10 project at home and it now consists of Active Home Pro & CM15A, several Socket rockets (LM15A), several Appliance Modules (AM466), several Lamp Modules (LM465), a Palm Pad (HR12A), a Mini Timer (MT13A) - used pre-AHP/CM15A - and an Infrared Command Center (IR543) for controlling my A/V lighting with my Harmony One remote. I
DID have a Transceiver Module (TM751) too but removed it when I installed the Active Home Pro & CM15A. Before I continue, let me point out that all of this stuff is pretty new since I've only been doing this for a little over a month. Since it's all new, the LM465's all have the soft start/stop. This all worked well
except not all of my modules were accessible because I didn't have a Phase Coupler. So I ordered one -- the Leviton 2-Phase X10 Amplified Coupler/Repeater (HCA02) (
http://www.smarthome.com/4823/Leviton-2-Phase-X10-Coupler-Repeater-HCA02-10E/p.aspx).
YesterdaySo, with the above in mind, I did two things yesterday that started my issue: I wrote two macros that did nothing more than check to see if it was night and then dim a pair of lights controlled by two LM465's with the same address by 50% and 25% respectively. The two macros worked well when testing from the AHP screen. The second thing I did was install my newly arrived Levitron HCA02. This upgrade successfully made all of my modules in the house accessable/controllable (on/off/dim/bright) via my AHP screen, my Palm Pad, my Harmony One/IR543 and my Mini Timer. Great! Not so fast........
Signal Firestorm?After installing the HCA02, I sat back and waited for my first timer events to happen around dusk. Nothing happened. Having missed the dusk timer events, I assumed there was an issue with the CM15A memory due to turning the power off to install the HCA02. I cleared the CM15A memory and reloaded all timers and macros. After the next event passed without activity, I thought about the only two changes I made to the system since it was last working properly -- adding the macros and the HCA02. I also thought about comments about the buggy AHP software I was running (v 3.326). Picking the easiest thing first, I deleted the two macros, then re-cleared and reloaded the CM15A. Still no auto-activity from the CM15A. I should have looked at the log at this point but I didn't think of it until talking to the guys at the Home Automation Chat later last night. So anyway, I downgraded my AHP software to version 3.328 to see if that'd help. Although some timer-activity came through, it was inconsistent. Also, even manual dimming activities (via AHP % sliders) was very odd. Sometimes if I turned off a module via an on/off AHP switch, it would automajically turn the slider all the way to off -- and visa versa on other lights.
So, I talked to the guys at the Home Automation Chat last night (thanks again guys!) and they told me about using the "Issue an ON instead of a bright 100% " choice in Macro Preferrences (which I did), Signal Firestorms due to the repeater in the HCA02 vs the CM15A, Absolute vs Relative dimming, extended commands and other things. By now, it was time for the CM15A to turn off the various lights (which I'd turned on manualy) for the night -- which it did successfully! Although I know the Off commands are not extended commands, this at least was a step in the right direction. I believe it was a result of using the,"Issue an ON instead of a bright 100% " choice in Macro Preferences. The other things I did -- deleting the macros and downgrading the software -- were probably NOT the reason for success. But, who knows.
TodayToday I did some additional searching/reading and found some additional information in these two message threads:
It's fairly obvious now that the CM15A and HCA02 fight with each other at times -- probably about extended codes. After spending $80 on the HCA02 AND because I need it to allow proper communication with all of my modules, I'd rather not return it (if that's even possible). So, using all of this new information, I'll be testing for a while now to see what I find regarding work-around(s).
In no particular order, I'll try
- using Absolute vs Relative dimming
- adding pauses in the macros I write even though it doesn't appear to need them
- Other things I think -- or you all can suggest -- of for workarounds
- As a last resort, try a passive coupler (w/o repeater)
Thanks for listening. If anyone has any other ideas, please let me know.