Even though I’m using mControl for home automation I re-installed ActiveHome Pro to tinker with accessing particular modules that are not yet supported by mControl. What I did not know was that during the re-install the X10 software updated the CM15A interface and changed the monitored house code. This effectively disabled all remotes in the house.

After figuring out the problem I tried to update the hardware interface but ActiveHome Pro kept crashing. I updated the software to the latest version, which added Windows 7 support. At that point I was then able to set the CM15A back to the previous configuration.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

I’m Mike

Welcome to my blog, which I have maintained for several years, off and on, to share things that I’ve learned from numerous projects and various problem solving escapades. This is my way of giving something back to the online communities that have helped me learn more about a wide variety of topics.