The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: cm12 trouble



There is also MisterHouse www.misterhouse.net It's open source/free and has
a very active developer community - a few others on this use it too.

I can sympathise about your CM12, I'm on my second...

Just as soon as I get a roundtuit, I'm going to dismantle the broken one
and
replace as many components as I can, one by one to see if I can find the
faulty part - that's about as far as my 'leet' electronic 'skillz' go, if
that doesn't fix it, I'll vent my anger with a lump hammer...

Lee

-----Original Message-----
From: Stephen [mailto:yahoo@xxxxxxx]
Sent: 01 September 2004 08:30
To: ukha_d@xxxxxxx
Subject: [ukha_d] cm12 trouble


Hello,

I think my cm12 has blown-up. This my third cm12. The other two went
very hot and smelly; this one has not, but nothing is switching
on/off so I guess it must have failed.

The retaining clip on the cm12 end of the serial cable has fallen off,
so I cannot communicate between pc and cm12 to test it. Can these
cables be bought separately?

I am getting fed-up with replacing these cm12s. I know people on this
list have used three or four, so it is a common failure. How are
Marmitek getting away with this, when so many fail? Why don't they
build them more robustly?

I was thinking of buying a combi-pack of Homeseer and new cm12 but the
proce is over £100. I didn't think it was that much. I was expecting
it to be about £80. Has the price gone up, if so why? Is Homeseer the
best bit of HA software to use; is it worth the price?

I am getting fed-up with x10; what are my other options? C-bus?

Thanks.




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.