chasers03 said:
The most convenient feature of my automation system [even more than HVAC, WiFi & security] is the turning on, dimming and turning off of my HLC lighting via motion detectors thruout the house.
Over recent years I have found that the time for the Omni Pro 2 to make light changes per the motions has increased, sometimes taking almost a minute it seems. Lighting change response to contacts is instantaneous in comparison.
Does anyone have ideas on how I can speed up the Omni Pro 2 lighting control response time?
Would my dealer settings have any effect on this problem? ie. UPB status time = 3 & UPB transmit count = 3
Has anyone ever sort UPB assistance from the Simply Automated folks
http://www.simply-automated.com/UPB_Technology.php ?
I've done a fair amount of research on this, and even spoke to HAI about this once.
First, I'm guessing that your lines of programming have increased over time. That is fine, but here is the thing. Programming, if not done a certain way can greatly slow the panel. Every action has a trigger (or multiple triggers), conditions and then actions. Your goal is to write your program in such a way to not slow the panel.
So lets look at triggers first. You want to stay away from triggers that trigger often, like the "every" with a short interval time. If you have to do a "every 5 seconds" then don't use more than the minimum needed.
Next, only triggers really slow the panel, so as a rule try to NEVER use the same trigger twice. Almost all your triggers should be unique. So how do you do that? Use buttons like macros. A button can have a condition or more and an action or more. More triggers equal slower panel. I have totally rewritten my code using unnamed buttons and its like night and day. If you do this, your programming will also be much more easier to understand as well. And your response will be quick. I use about 700 lines of code and have maybe a 3 or 4 second delay at most.
One other possibility is a loop and a programming error. It happens and the panel won't tell you otherwise there is a bug. Like maybe turning on a light turns on a second light, but turning on the second light turns on the first. Another reason to focus on your triggers carefully.
I haven't found conditions to be a problem unless it triggers so often that they are always being tested. You said you have wired motion detectors so they can trigger many times in a minute. If you have many conditions you can put the condition LEAST likely to be true first. Once the panel finds a false it stops evaluating.
1 minute is not normal and likely indicates something is not optimized. Good luck tracking it down. It can be tricky.