UPB, UPStart and the Omni Pro 2

[BobS0327]

I've noticed some interesting OP2 behavior when executing scene (link) commands thru either UpStart or my Java app. It seems as though the OP2 doesn't update the status  on the individual devices involved in the scene whenever an external host executes the link command.  The only way I am aware of updating the OP2 based on the activating of a scene is to have my app execute a Get Status request on all the devices involved with the activated link.  Thus, the OP2 will "sniff" the returned status packet and update its UPB devices based on the received Get Status packets. 
 
I also noticed that the OP2, when executing an All Off or All On does use the assigned room scenes (links) to execute these commands in each room.  So, to some extent, the OP2 does use links.
 
I assumed that the OP2 built some sort of links database by querying the devices and would use this database to update the status of all the devices when a link command is executed.  I guess I'm wrong on this point.
 
Can anybody explain the workings of the OP2 when other hosts execute link commands?
 

 

[Desert_AIP]

Are you using HLC mode?

In HLC mode, when ANY of the room assigned links are executed, the Omni will query the status of all units in that particular room after the UPB delay.
That behavior occurs regardless of the source of the link. It can be the Omni, UPstart, a switch or other device or an app.

All On and Off work as you described.
The Omni uses the individual room links, updates the status of the room, then moves on to the next room.

 

[Desert_AIP]

http://cocoontech.com/forums/topic/26748-upb-configuration-into-ominpro/

 

[BobS0327]

I'm using HLC mode.  I've used PC Access to configure all of my Leviton UPB switches.
 
 

In HLC mode, when ANY of the room assigned links are executed, the Omni will query the status of all units in that particular room after the UPB delay.

 
Yes, that does work for all the default links, (the 80%, 60% etc dimming links) which I believe are initially set up when the room is first created.
 
The issue is when I create a custom link and execute that custom link  from UpStart or another source, the UPB units in the OP2 are not updated to reflect the change of status of all the devices in the link.  This is where I have to execute a Get Status request in order to update the OP2.
 
This custom link can control devices in one room or any combination of rooms.
 
 
 
 

 

[Desert_AIP]

You have to program the behavior you want for the custom links.
The Omni has no way of knowing which units are affected by the custom links, so you have to tell it.

WHEN UPB Link xxx ACTIVATED
THEN UPB ID xx get status
THEN UPB ID xx get status
Etc.


You have to program the behavior for each link and whether it's an activate or deactivate action.

The link I posted had some tricks and tips I use to maximize efficiency.
I change the default behavior of some HLC links.
That method doesn't work for everybody, but I have used it very effectively.

Also, make sure your devices are programmed to update their status when their local rockers are pressed.

 

[BobS0327]

OK.  Now it all makes sense to me.
 
So, I would have to recreate  all the custom links (scenes) using the OP2 scripting language.   It seems to me that would generate a lot of scripting code if there were a lot of custom, extensive links involved.
 
Thanx for the info.

 

[Desert_AIP]

It is a lot of programming.
That's why I modified the default behavior of HLC to address some of those short comings.
I exploited the automatic status tracking of the Omni by tricking it into thinking a link is an HLC link, or using the D link in each room as a room status update link.
I also group switches into logical rooms to maximize the status tracking efficiency.
So all the fans in the house are in one room, and the lights in the three bedrooms other than the master are in a single room. And each of the A, B and C links controls the devices in a room. When any one of the links is sent, the Omni updates the status of every unit, so I never have to tell it to update the status.
In links that affect multiple rooms, I use the D link of the other rooms to update their status with a single programming line rather than eight unit status request lines.

Read that linked thread, everything I learned about HLC is in there

The Omni is memory space limited, which is why there aren't provisions for creating a complete link/unit table internally.
HAI did some really great work creating the HLC protocol.
Ideally in the Omni Pro III, you would be able to upload the UPStart network file and have the Omni know the link and unit relationships and know when to update statuses based on it.

 

[BobS0327]

@Desert_AIP,
 
Finally got time to fully read the linked thread.  It does provide a lot of very useful information.  I've bookmarked that thread for future reference.
 
Thanx