How are you Tony,
So when you stated
As for scenes, you get to the ALC scenes in a different way. In your program select as a trigger "When ALC" and then choose on/off, 1,2,3, or 4. 1-4 are ALC scenes for that particular 4 button scene switch.
and
However, these type scenes are not learned by the Omni. If you want to run the same scenes from program flow, you must create lines of code that do the same thing.
So to be clear, one goes and programs their scenes via a ALC 4 button Scene switch, by placing the ALC 4 button Scene switch on a BRANCH (as it will not see or control switches on other branches correct?) they wish to create up to 4 scenes with any combination of 30 lights on this branch as the scene switch takes up one address itself (31 addresses on a branch)
YOU CAN ACTUALLY ADD ANY ALC SWITCH, NOT JUST THE ONES ON THE SAME BRANCH. THE 248 LIMIT ON THE OMNI PRO II IS 2 EACH 4 BRANCH CONTROLLERS FOR A TOTAL OF 248 TOTAL ALC DEVICES.
but when you go to the OPII programming and you have a line like "WHEN ALC SW1 PRESSED", the controller knows this becasue it polled that it was pressed (ON) and then you can have it do something additional like close curtains, but it will not set the lighting, it is the Scene Switch itself that set the lighting scene.
NOT EXACTLY. THE LOCAL PROGRAMMING OF SCENES DOES NOT REQUIRE ANY LINES OF PROGRAMMING IN THE OPII, BUT YOU CAN ALSO WRITE RULES THAT TRIGGER LIGHTS AND CLOSE CURTAINS. JUST BE CAUTIOUS OF CONFLICTS WITH LIGHTING WHEN DOING BOTH TYPES OF PROGRAMMING....
Also to run the same scene from program flow (if you programmed one to do the same at the scene button), it would be executed by a TRIGGER other than the scene switch correct? as if you applyed the programming as the SW1 pressed, it would be a waste of line code, because both the scene button and the program would call on the same lighting commands, is this correct?
TRUE. THE BEST USE OF LOCAL SCENE PROGRAMMING IS FOR USE BY THE HOMEOWNER TO PROGRAM SCENES WITHOUT ANY PC PROGRAMMING REQUIRED. AGAIN, IF BE CAUTIOUS OF CONFLICTS WITH RULES YOU WRITE.
And to add to this you must have a 1 or 4 ALC branch interface in order to be able to
You simply hold in the desrired button for 15 seconds and when it begins to flash it is ready to learn any ALC settings from any switch you set On/OFF/Dim/Bright). When done selecting light settings press the button again and that scene will run anytime you press that button. This is great for setting up a scene quickly and making changes on the fly. However, these type scenes are not learned by the Omni.
as it is not the scene switch itself that learns the scene, but the ALC branch interface and assigns the scene to that scene switch button. Is this statement correct?
TRUE. ALSO NOTE THAT THE ALC BRANCH INTERFACE WE MAKE IS CALLED THE "SCENE LEARNING INTERFACE" AND WILL BEHAVE AS DESCRIBED ABOVE. THERE IS ALSO ANOTHER ONE THAT WAS MADE BY HAI (AND OLDER ONES MADE BY OnQ) THAT DO NOT LEARN SCENES.
TO TELL THEM APART LOOK AT THE COLOR OF THE PRINTED CIRCUIT BOARD ITSELF. A BLACK BOARD IS A SCENE LEARNING INTERFACE A GREEN ONE IS NOT.
In the "Extended" House Code Format, you have the following Unit Commands:
Off
On
Toggle
Dim
Brighten
Light Level
Ramp
Are these all ALC compliant Commands? Some behave weird, for a lack of better words. Like if you send a control manually to set Light Level 40% you get 39% after exection. Via programming block you get 40%? Just wanted to know your experiences/knowledge.
YES THESE ARE ALL USED. AND WE ALSO HAVE A "RAMP" FEATURE THAT CAN BE USED TO LINEARLY AND VERY GRADUALLY RAISE OR LOWER THE DIMMING LEVEL.
I am learning HA, and knowledge is key, I want to make sure I am understanding ALC correctly as well. And ALC integration with HAI.
