Xymox
Member
I got a tad overboard in sophistication in doing some programming using a 1132CU and Smarthome Manager Pro and ran into a problem maybe someone can help me with.
First I cannot afford Homeseer and the Smarthome Manager does what I need.
I created a sequence with a number of timed events. In these timed events are conditionals based on the state of a "phantom" generic X-10 appliance module.
The Idea is I have a non existant appliance module that acts as a memory/flag that has a "home / away" status. IE if its ON then im home and if its off im not home. The idea is to do things differently when im home.
This seems to work and the status of the phantom module is kept in the 1132CU memory and I can use it as a conditional flag.
So my sequence goes like this.
If day = mon - fri
--if between midnight and 3:30am
-----If the phantom-a module shows im here
--------If phantom-b module is also on
----------Event
--If between 3:30am and 5:30am
------If the phantom module shows im here
---------If another phantom module is on
-----------event
.......
I have a number of these steps
I have another whole set for weekends
I then call this sequence from time triggered events like they were a subroutine and I call the sequence at various other times from extrenally triggered events.
Its essentially a subroutine with conditional steps based on time and on the phantom module state.
So all this works fine... Except....
I noticed something weird happens now. If I look at my logging and press buttons on a controller the 1132CU does not see the whole command set on the first press of a button.
I press a "D1 - OFF" the log and 1132CU only see "D1"
When I press it a second time the controller sees the whole D1-OFF command and acts on it.
This happens over and over.
First press the 1132CU only sees the D1
Second press it sees D1-OFF
third press D1
forth press D1-off
fifth press D1
sixth press D1-off
You can see this in the logging.
You can wait a long time between presses and it makes no difference.
VERY weird. Very consistent too. From every controller.
If I remove the conditionals from the sequence everything is OK again.
What are the limitations in branching and lengths of conditionals and depth of recurvise conditional checks ? Have I exceeded something.
I realize im asking a lot of a little 1132CU
I put the program in question up on my server for download if anyone wants to look it over or test it.
http://www.xymox1.com/powerlincprob.ZIP
First I cannot afford Homeseer and the Smarthome Manager does what I need.
I created a sequence with a number of timed events. In these timed events are conditionals based on the state of a "phantom" generic X-10 appliance module.
The Idea is I have a non existant appliance module that acts as a memory/flag that has a "home / away" status. IE if its ON then im home and if its off im not home. The idea is to do things differently when im home.
This seems to work and the status of the phantom module is kept in the 1132CU memory and I can use it as a conditional flag.
So my sequence goes like this.
If day = mon - fri
--if between midnight and 3:30am
-----If the phantom-a module shows im here
--------If phantom-b module is also on
----------Event
--If between 3:30am and 5:30am
------If the phantom module shows im here
---------If another phantom module is on
-----------event
.......
I have a number of these steps
I have another whole set for weekends
I then call this sequence from time triggered events like they were a subroutine and I call the sequence at various other times from extrenally triggered events.
Its essentially a subroutine with conditional steps based on time and on the phantom module state.
So all this works fine... Except....
I noticed something weird happens now. If I look at my logging and press buttons on a controller the 1132CU does not see the whole command set on the first press of a button.
I press a "D1 - OFF" the log and 1132CU only see "D1"
When I press it a second time the controller sees the whole D1-OFF command and acts on it.
This happens over and over.
First press the 1132CU only sees the D1
Second press it sees D1-OFF
third press D1
forth press D1-off
fifth press D1
sixth press D1-off
You can see this in the logging.
You can wait a long time between presses and it makes no difference.
VERY weird. Very consistent too. From every controller.
If I remove the conditionals from the sequence everything is OK again.
What are the limitations in branching and lengths of conditionals and depth of recurvise conditional checks ? Have I exceeded something.
I realize im asking a lot of a little 1132CU
I put the program in question up on my server for download if anyone wants to look it over or test it.
http://www.xymox1.com/powerlincprob.ZIP