Easier to program rules (M1 Gold vs OPII)?

[ano]

Actually the last code / variations of the code did get "caught" in somewhat of a loop (time) and the chime rang and rang last night during a pizza delivery. Somewhere have to insert some sort of delay in the code because it as written I can see that it would somewhat loop.

I currently don't use HS / HAI connection for anything super time sensitive/emergencies/life saftey because of the plugin polling issues/ time delays. HS uses the IR's but HS HAI plugin IR events are not critical. Actually mostly all critical / events that I care about are run from the HAI panel. IE: lights regular, lights bases on IR motion, thermostat, etc. I switched my lighting over to the panel many years ago. The trigger for said endeavor was a HW failure on the HA server the day before going out of town for a week or so. None critical and test HA events are run from HS. I still do get TTS events being triggered by some rogue HS/HAI legacy serial com issues - very annoying - alarm TTS on/off at irregular / non HAI driven times, etc. I'm glad I have no "life saftey" events set up in HA right now. What I do have and care about are 18 plus serial connections on HA box do screen scraps, 1-wire data input, controlling my sprinkler system, etc.

I have decided to go to a small footprint mini-itx dual core based HA box (just 2.5 " Raid-1 HD setup) (something like 8"X8" by 2" or so) using just the ethernet / USB ports and maybe attach this box to the basement catch all way adjacent to the HAI panel/ media panel.

I have time to play and will look at CQC set up on another 2003 box - what would the basics be right now for a pure CQC-HAI panel HA setup?

Just because the panel doesn't loop doesn't mean your code can't get caught in a loop. Those are really two different things. If one trigger causes an action which triggers a second action, and that second action causes a trigger of the first, you have problems, but its not the panel's fault.

The problems I had when I used HomeSeer serial polling with the HAI Omni Pro II was that HAI timers would suddenly quit out of the blue. For example, if I set a light to be on for 30 seconds, I might be viewing the timer in PC Access and see it count down as 30, 29, 28, 0 with the light never turning off. At first I thought it was a broken panel so I removed it and returned it to HAI. They sent me a new one and same problem. I later determined that if I stopped HomeSeer the problem didn't occur. Since I needed to use HomeSeer at the time I just lived with it, but with CQC, no problems at all.

 

[ano]

I have time to play and will look at CQC set up on another 2003 box - what would the basics be right now for a pure CQC-HAI panel HA setup?

Note that there are two "drivers" for HAI on CQC. The older one connects via Ethernet but polls like HomeSeer does, but Ethernet is much faster than serial, and I haven't had any problems using it. If your HAI panel has Ver 3.0 firmware or newer, you can use the HAI TCP/IP driver. That is Ethernet as well but rather than polling it is interrupt driven so doesn't load-down the panel, and is quicker than polling.

You need a panel Ethernet port for CQC, it doesn't support a serial interface to the panel.

 

[Brian Yokum]

pete_c,

You asked about a simple example of HAI programming to control a door bell chime. You want the door bell to chime once whenever either the door bell is pressed or motion is detected. I don't know the specifics about your chime, but for puposes of this example I'll assume it makes noise as long as it is turned on. So I'll turn it on for two seconds, but you can change this action to whatever works for you. The Chime Flag is used to allow only one chime during a one minute window.

WHEN Door Bell NOT READY
WHEN Motion NOT READY
AND IF Chime Flag OFF
THEN Chime Flag ON FOR 1 MINUTE
THEN Chime ON FOR 3 SECONDS

 

[taskman]

Hello,

A big difference is that the HAI offers an "IF" in their statement where the M1 does not.''


Basic programming 101 should contain
IF (this) THEN (that) ELSE

or

IF (this AND that > that and this THEN that ELSE = that

or (we can use the OR as well to really create a professional scenario...)
Example

IF LIGHT2_OUTSIDE => 76% THEN Turn Off LIGHT1_OUTSIDE = 76% ELSE {}


IF ((TEMP_OUTSIDE => 65) AND (TEMP_INSIDE <= 62)) OR OUTSIDE_MOTION = OFF THEN TURN HVAC OFF ELSE {}

I am half asleep so it is not written how I would normally do it but this should give you an idea.

***************************************

OK so I add a counter to the flag and break it up a bit ....will the follow ring the chime once based on whichever variable changes? And to do the same or similar with an M1?

1.	//	========================
	//		   DOORBELL
	//	========================
2.	WHEN Doorbell NOT READY
		AND IF Chime Counter CURRENT VALUE IS 0 
			THEN Doorbell Flag ON
			THEN INCREMENT Chime Counter
3.	WHEN Ex Frnt Door IR NOT READY
		AND IF Chime Counter CURRENT VALUE IS 0 
			THEN Doorbell Flag ON
			THEN INCREMENT Chime Counter
4.	WHEN Doorbell Flag ON
		AND IF Chime Counter CURRENT VALUE IS 1 
			THEN Door Chime TOGGLE
			THEN LOG Front Door Chime
			THEN DECREMENT Chime Counter
			THEN Doorbell Flag OFF

 

[pete_c]

Thanks guys - will give it a try. Currently had taken away the motion piece of the doorbell and went back to just a single variable (doorbell).

1.	//	========================
	//		   DOORBELL
	//	========================
2.	WHEN Doorbell NOT READY
	WHEN Ex Frnt Door IR NOT READY
		AND IF Chime Flag OFF
			THEN Chime Flag ON FOR 1 MINUTE
			THEN Door Chime ON FOR 3 SECONDS

 

[Lagerhead]

A big difference is that the HAI offers an "IF" in their statement where the M1 does not. . .

Is this really "true"?

While shopping for a replacement system a couple of years ago I looked at both the M1 and the OmniPro II, and I judged their programmability roughly equivalent, with a slight edge to the M1, which I ultimately bought. Has the OPII had significant upgrading in that time?

I took that the OPII allowed up to two IF conditionals per rule. In the M1, although it's not called IF, the AND serves the same purpose as IF. The M1 allows many AND conditionals per rule, limited apparently only by memory. I haven't tested the limit, but at one time I had a rule with seven ANDs. Also, AND can be made logically equivalent to OR with proper arrangement of the testing conditions.

I suppose you could construct rule scenarios which in the OPII implementation would be simple and straightforward while in the M1 they would be cumbersome. And vice versa, for sure. Which I think is more or less what the OP had asked originally.

 

[Brian Yokum]

The HAI automation scheduling was significantly enhanced in firmware 3.0. Now, each programming "block" may consist of an unlimited number of triggers, conditions, and actions. In addition to "AND" conditions, blocks of "AND" conditions can be combined with "OR" statements. Also, conditions can include tests of just about anything in the system. For example, one can now say something like "AND IF Upstairs Themostat CURRENT TEMPERATURE IS GREATER THAN Downstairs Thermostat COOL SETPOINT BY MORE THAN 5". PC Access allow longer descriptive names for zones, units, etc., and comments can be added to the automation programming. For more details, review some of the firmware updates starting at 3.0 in the following HAI Knowledge Base article.

http://kb.homeauto.com/default.asp?id=459&...Lang=1&SID=

 

[pete_c]

The above "doorbell' that Brian mentioned is working for me.