Print

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

[michael]

My SS13A has not worked well out of the box
with my CM15A.  However, when I changed
the "monitored housecode" on the CM15A to
something other than the one the SS13A, I
have noticed that the CM15A finally
registers the RF signals from the the SS13A
(although, I can't move too far away from
the CM15A).  When I changed the Monitored
Housecode back to the same code, the switch
worked for about 10-15 keypresses, then the
CM15A stopped registering it.  I changed
the Monitored Housecode again, and viola,
it works.  Has anyone else noticed this?
Could the monitored housecode be causing
the other lockups, too?

[paul mayfield]

I received 2 stick a switches with some of
my orders. They both came at the same time.
The first I tried to use had the same
symptoms, it worked for a while then quit,
If I changed the house code it would work
for a while again and then quit. The other
unit I recieved works flawlessly. I tried
the first unit again and it still does the
same thing, finally threw it on a shelf and
there it sits (by the way swapped batteries
with the other unit just in case but nothing
changed)

[Mike C]

I have had the same problem with the stick a
switches and the keychain remotes. The
problem is caused by poor battery
connections.  When the battery connection is
lost the unit reverts back to housecode A
unit 1. Try cleaning the battery and
connection terminals.

[michael]

I've checked to see if the switch is
resetting, and it is not.  When the switch
stops working, it is still set to the correct
Housecode and Device code.

[X10 Pro]

I don't see how the Monitored House Code
would affect RF reception. What do you have
set up as the Transceived House Codes in the
Hardware Configuration?

[solareclipse]

X10 Pro - I think Michael may be on to
something actually.  I believe that when
AHP is monitoring a housecode it will send
different commands for a device depending
on what state it thinks that device is in.

For example, if I have a macro that turns
A10 On, normally I'll see this (when
triggered via the PC):

Transmit A10
Transmit A On

Now, if I dim A10 via the PC, I'll see:
A Dim 50%

And now if I run the same macro again, I'll
see:
A Bright 48%

It performed two different actions to
achieve the "same" result.  Now if you are
triggering via a RF command, and AHP is
monitoring that housecode, it's going to
try and keep up with the current state of
things.  But what if it gets messed up,
misses a command, or something?  If it
sends A10 On when it's dimmed - it won't
dim.  It needs an A10 On, A Bright 100%.

I think this is why a lot of people are
having "sporadic" problems.  I'm not sure
the device is working sporadically, I think
it may just be out of date on the current
state of things and it's sending the wrong
commands, which appear they're not doing
anything.

[X10 Pro]

SolarEclipse: Is that macro you mention one
that runs from the PC? That's the only way I
can see the same macro resulting in two
different commands being sent. When a macro
is stored in the interface, the command set
is run as is -- no interpretation or
modification when it's triggered.

In the case Michael describes, he's not using
a macro -- just pressing buttons on the
SS13A. That should always be received
correctly, no matter what the monitored house
code is.

[michael]

Here is the deal.  I have my computer on and
I am watching the activity.  When I set the
Monitored housecode to "F" and the Switch to
"F1", my CM15A shows no RF signal received.
When I then change the monitored housecode to
something other than "F," the activity now
shows RF signals from the switch (on F).  I
can't more more than 5 or so feet away from
the receiver, but I think that is a different
issue.

[solareclipse]

In the macro I used in my example, it was
stored in the interface, but ran from the
PC in my tests.

[X10 Pro]

Michael: That's pretty odd. I'll try to
duplicate it here. Do you have any problems
with other RF remotes?

[michael]

I don't have the problem with my motion
sensor, large remote, or key remote.  Btw,
sometimes it will work when I switch it
back to the correct Monitored Housecode,
but then it stops after about 10 or so
commands.