Re: half-dead cm12

["david_dabs" <david_dabs@xxxxxxx>]

I'm having simular problems,  I havent had any dodgy smells though.

I find that when the CM12 has been used for about a week that it
loses its sensitivity, IE it no longer hears X10 commands that are
far away on the power line although stuff in the other half of a
double socket it does hear. It will also still control stuff in the
other socket but nothing else.  If I unplug the unit for a few hours
it will recover and be fine again (at least for a week).  Almost as
if its overheating?

For me I cant really live like this, as soon as my CM12 packs up all
the schedules and triggers go out the window, motion sensor no longer
do anything nor the keyfobs etc.

I'd really like some advice what to do next, do firmware updates
exist perhaps?, the unit is only about 6 months old, so I assume I
could also send it back to Letsautomate for a replacement or will I
have to deal direct with X10?

Some advice is geatly appreciated.
regards
David


--- In ukha_d@xxxxxxx, Stephen <mail@s...> wrote:
> This doesn't seem to have appeared so here it is again:
>
> Hello,
>
> Last night I smelt the characteristic smell of hot cm12. I unplugged
> it, thinking it was fried. However the active home software can
still
> communicate with it, it passes the test option. I also have an
> appliance module in the next socket and that responds to codes from
> the cm12, but all the other appliance modules do not. Could it be
that
> the cm12 is only outputting weak signals that travel to the local
> socket but not any further? I thought it would work or it would
not, I
> am surprised it half works!
>
> This happened once before (with a different cm12), although that
time
> it failed completely. I am clutching at straws here but all I can
> think is that I plugged the vaccuum into the same socket (not the
> cm12s built in socket). I imagine vacuums make a lot of electrical
> noise. Would this noise on the line have damaged the cm12? Should I
> put a filter on my vaccuum?
>
> Thanks.