...It keeps wanting to switch my monitered house code, to a set that is rarely used. I have more codes listed under this one setting, so the software keeps wanting to make it monitered code, even though it recieves more signals from a house code with fewer addresses.
AHP could be a little smarter,Yeah I don't think X10 has addressed that bug yet.
It keeps wanting to switch my monitered house code, to a set that is rarely used. I have more codes listed under this one setting, so the software keeps wanting to make it monitered code, even though it recieves more signals from a house code with fewer addresses.
...As TaketheActive put it while I was typing my reply...
Create a DUMMY ROOM and add enough DUMMY MODULES on your DESIRED HOUSECODE (I use devices that I don't have, such as HD245) to overcome the number of other modules and it will STOP complaining. :)
It would be great if you could check the status of any address. Unfortunately, the interface only has the capacity to track the one house code, and my guess is that it's pretty unlikely that will change.
I mean, it could not be all that much memory. The interface only stores 'on' and 'off' status. So, all 256 possible house/unit codes would be only 256 bits or just 32 bytes of memory.
Problem is the CM15A's microcontroller only has 256 Bits of RAM. This contains the monitored house code's status, program variables, registers, stack, program counter... etc.