Print

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

[SteveRF]

Why am I so confused about the "monitored
house code" ?  I thought the purpose of the
monitored house code was so that the
intelligent CM15A could "self determine" that
a given device on a monitored house code was
already turned on or off, thus relieving the
unit from sending additional ON or OFF
commands to that device even if the trigger
signal was being received.  i.e. motion
sensors continous triggers every 6 to 8
seconds... If this was not the intent then
what have I missed here... If this was the
intent then it is NOT working...

SteveRF

[Scott T]

Hmmm Great question.
I have been reading more and more about the
CM15A and the 1132CUP.  The first
interesting thing is my new perceived of
what of the “monitoring” function is to
either unit.  I read a posting on accessx10
explain some differences between the two
units.  The CM15A monitors one-house code
(16 unit statuses) plus 16 independent
flags.  The 1132 monitor all house codes,
but have no flag capabilities.

Hmmm.  I take this as meaning that each
keeps track of signals being send and
transmitted by each respected unit.  So, if
this is correct, then CM15A can track the
status of 16 units and 16 flags.  I image
that you could use the 16 internal flags
plus 16 virtual modules as flags too.

NOW to your question SteveRF…
I would guess that you would not want your
control unit only monitor change of status
of any given unit and holding back commands
that match the current controllers unit
status. If that doesn’t make sense, then
lets look at how that could be a problem.

If you had a one-way device (like most of
X10.com devices) that also had local
control, then commands could be held back
that should be sent based on the controllers
status and not the true current local status
of that device.

I certainly don’t know if this is all
correct, because I’m just trying to
understand the whole monitoring deal with
the CM15A and the 1132.

Please review and comment.  I would like to
better understand.

Scott T

[SteveRF]

Scott, and others please chime in !
..hummmm
So what was the bottom line here...
IS the purpose of the "Monitored House Code"
to eliminate "redundant, repetitive and
unnecessary" transmission of PLC's ?  Seems
like a god idea to me and the "user" could
always use other unit codes for devices that
were NOT to be affected by the "Monitored
House Code" logic.  If this is the purpose of
the "MHC", then according to my monitoring,
it does NOT work.
SteveRF

[billy]

From the "HELP" menu :
Monitored House Code
The ActiveHome Pro interface keeps track of
the status of the modules on one House Code,
and reports this data to the computer when
it is re-connected. Choose which House Code
you want to monitor with this menu.

The CM15A keeps track of the events on the
MHC, when the CM15A is not connected with
AHP. This way if your PC was off or the
CM15A unplugged, the status on the units on
the MHC is stored in the CM15A. Then when
you start AHP or reconnect the CM15A the
Status of the MHC units will be updated in
AHP.

Simple? )

[SteveRF]

Billy,
Well that makes sense...
I guess I expected more but see now that I
really should have read the help menu... oops..
I don't use the on screen module status since
my CM15A runs disconnected from the PC 24/7
so that it can be mounted centrally in the
home.  In that senario, the MHC doesn't carry
much funtionality. I guess I was just hoping
there was more intelligence built into the
MHC logic.. o'well..
Thanks for the response,
SteveRF

[roger1818]

Steve:  I have heard people complain that AHP
will change the monitored house code, without
telling you, to the house code with the most
modules.  That may be the source of your
problems.

[SteveRF]

Roger,
I have noticed my monitored house code
changing on it own from time to time...
something unstable there !
SteveRF

[anonymous]

I have noticed that if you have more
devices on one particular house-code and
have the monitoring set to another; AHP
asked you (I believe when either
downloading timers of updating interface)
if you want to change your monitored house-
code.

As a long shot ...
I wonder if you have your Action Warnings
for "check monitored house code usage"
(under preferences) unchecked, if AHP
automatically changes it to the house-code
with the most devices attached.

Hmmm.  I didn't bother testing the theory.
I could be totally wrong.  Somewhat tried
of hunting problem with this thing

Scott T

[steven r]

...I have heard people complain that AHP will change the monitored house code, without telling you, to the house code with the most modules.  That may be the source of your problems.

Very true! I should of read this 1st. I could of saved some time solving my problem. I've created a room called "DUMMY FOR BUGS" and added 15 dummy modules to HC "C" so I could change to that HC for monitoring.

It's a bandaid for a bug I hope they'll fix with the next release.

...I wonder if you have your Action Warnings
for "check monitored house code usage"
(under preferences) unchecked, if AHP
automatically changes it to the house-code
with the most devices attached....

It doesn't matter if you have that option checked or not. It still switches the HC with the most items.

My story... http://www.x10community.com/forums/index.php?topic=8709.msg52693#msg52693

[spud99]

I don't think this has to do with the CM15A switching house codes,  we can all easily figure that part out ourselves...   
I understand exactly where SteveRF is coming from, and I had wondered the exact same thing. 

I signed up to this site just to look for or post this exact question.

My monitored house code is 'A' (trust me).
When I physically turn light-switch A1 on, I expected the PC to know that 'A1' was on, and update my interface,  but it didn't.  'A1' remained in an off status on my computer screen.

I started to wonder what this monitored house code thing even for, or if mine just wasn't working for some reason.

[-Bill- (of wgjohns.com)]

I don't think this has to do with the CM15A switching house codes,  we can all easily figure that part out ourselves...   
I understand exactly where SteveRF is coming from, and I had wondered the exact same thing. 

I signed up to this site just to look for or post this exact question.

My monitored house code is 'A' (trust me).
When I physically turn light-switch A1 on, I expected the PC to know that 'A1' was on, and update my interface,  but it didn't.  'A1' remained in an off status on my computer screen.

I started to wonder what this monitored house code thing even for, or if mine just wasn't working for some reason.

Your problem is that most wired in X10 light switches do not transmit their status, they only receive X10 commands.

As far as the "monitored house code", the CM15A only has enough memory to remember the state of 16 modules (one house code worth).  The state it remembers is generally based on what command the CM15A last sent or "heard" sent to a particular module.  When connected to a running computer, the X10 interface software actually remembers the status of all 256 possible modules.  However, when disconnected, or when the computer is off, the CM15A has to rely on its own internal memory.

[bitman]

As far as the "monitored house code", the CM15A only has enough memory to remember the state of 16 modules (one house code worth).  The state it remembers is generally based on what command the CM15A last sent or "heard" sent to a particular module.  When connected to a running computer, the X10 interface software actually remembers the status of all 256 possible modules.  However, when disconnected, or when the computer is off, the CM15A has to rely on its own internal memory.

Ok that's why the cm15 only monitors 1 HC while addressing all of them.
Is everything from x10 limited?
What decade is this? Memory is cheap.

[HA Dave]

Ok that's why the cm15 only monitors 1 HC while addressing all of them.
Is everything from x10 crippled?
What decade is this? Memory is cheap.

I hear your frustration, I feel your pain. But this decade... I don't think we use the term crippled (let us BOTH edit these posts).

I still have my old AH (CM11A) it didn't have any RF abilities... only PLC and if I remember correctly 16MB of memory. The CM15A was a huge upgrade with a total 256 megs of memory (as much as most computers had RAM at the time) as well as the some limited RF capabilities.

Home Automation is by its nature... cutting edge. These HA devices and software are made and sold in such limited runs... things like fair prices, and current technology will always be in conflict. I think it is more productive to engineer our HA around the available technology. The technology itself... will never be able to keep up with our collective imaginations. The use of flags can help extend the "memory status" of devices. Some users are now using more than one CM15A.

[dave w]

 But this decade... I don't think we use the term crippled (let us BOTH edit these posts).

You are joking aren't you?

[HA Dave]

You are joking aren't you?

Well it can't be edited out now... The term crippled is generally OVERLY critical and is rarely used in an excepted manner. Having a disability... does not make an individual (or device) defective, or without abilities (disabled). The term [a noun] crippled itself... is derogatory.

The CM15A... is the MOST able Home Automation device on the market today. Although the device may have limitations (as many of us humans also do) it isn't defective or without abilities.. ether.

No one has to love every (or any) X10 device. But there isn't a need to be overly critical here at the forum.

The actual point I was trying to make was that the nature of home automation.. is cutting edge. There cannot be a product introduced that will meet expectations... as expectations are a dynamic requirement. As can be seen throughout the forum (and all other HA forums) the key to great HA isn't new products.. but creative uses of current technologies. Name calling.. is non-productive.