Feature request: UPB Link trigger command "ANY"

[cornutt]

I have a request. I've got a few rooms where I want to use Web Mountain SW-7's with my OmniProII. I'm kind of anal about having the Omni do accurate status tracking for units. Having already installed a couple of these, I can see that I'm going to wind up writing a bunch of automation blocks of this sort:

WHEN Exterior All On/Off ON
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS
WHEN Exterior All On/Off OFF
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS
WHEN Exterior All On/Off FADE STOP
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS
WHEN Exterior All On/Off SET
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS

["Exterior All On/Off" is a name assigned to a UPB Link number]

It would be nice if I could do less typing, and save some lines of program memory, by writing:

WHEN Exterior All On/Off ANY
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS

where "ANY" refers to any occurrence of the four UPB Link command types.

 

[fcwilt]

Could you just poll all units at intervals, say every 5 minutes?

 

[cornutt]

Could you just poll all units at intervals, say every 5 minutes?

I thought about that. Besides the "I'm too OCD to settle for that" factor, I see two potential problems: (1) Any rules that are triggered by change of status on those units won't be triggered until the next polling interval. (2) It seems like it would create a lot of traffic on the UPB network. Given UPB's low data rate, I'd rather not clog it up with a bunch of status polling.

 

[HAI_fjh]

cornutt,

One thing that would reduce the programming significantly would be to combine the WHEN statements:

WHEN Exterior All On/Off ON
WHEN Exterior All On/Off OFF
WHEN Exterior All On/Off FADE STOP
WHEN Exterior All On/Off SET
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS

A block is executed when ANY trigger event occurs and ALL conditions are met.

In my example there are four triggers, and no conditions.

IMHO this is more flexible than the "ANY" link type because you could, for example, trigger on the ON, OFF and SET but not the FADE STOP.

 

[cornutt]

cornutt,

One thing that would reduce the programming significantly would be to combine the WHEN statements:

WHEN Exterior All On/Off ON
WHEN Exterior All On/Off OFF
WHEN Exterior All On/Off FADE STOP
WHEN Exterior All On/Off SET
THEN Front porch lights REQUEST STATUS
THEN Exterior floodlights REQUEST STATUS

Oh, I didn't realize you could combine triggers like that! I'll give that a try tonight. Thanks!

 

[ASIHome]

FYI, to combine triggers you have to have at least 3.0 firmware and PC Access 3.0.