Bug or don’t know how to: with Client side Driver for Global Cache GC-100

[rocker]

You can invoke test commands from the Client side to any of the zones but I didn’t see a way to assign a device to a port/zone from the driver other than port/zone 1 as a result no calls can be made from IV to other than zone 1

[Dean Roddey]

This is covered in the driver docs. You append a zone suffix to the command. So if you were sending the command Denon1601.Power, you'd do Denon1601.Power:2 to send it to zone 2.

You may want to set up in the main template a set of globals on load, which map to the zones, and use those anywhere you want to indicate a zone, so that you can change them easily later.

[rocker]

Is it possible to add a future enhancement to be able to specify it in the admin area - same way we do it for com ports? It makes the programming more portable (even so you offer to use globals).

[Dean Roddey]

The problem is that many people have more than one of the same device. So there's no way at the device model level to set a zone. They want to address individual instances of the same model via separate zones.

[rocker]

The problem is that many people have more than one of the same device. So there's no way at the device model level to set a zone. They want to address individual instances of the same model via separate zones.

Dean,

From the admin, we should be able to assign a model and give it alias (or a client moniker). This alias will be specify in the command's action.

Example
From the client side we specify:
GC-100 zone1, Denon1601, BedroomAVR
GC-100 zone2, Denon1601, LivingroomAVR
GC-100 zone3, DirecTV, BedroomSatBox
GC-100 zone4, DirecTV, LivingroomSatBox

On the actions we call the alias:
BedroomAVR.Power

This will address both requirements.


Rocker

[Dean Roddey]

I'll add it to the list. Probably it's not going to be an immediate priority though. The downside of it is that it means going to the server to get the aliases every time an IR command is invoked, in order to do the translation, whereas the zone number is much lighter weight. And it also requires special casing IR field writes and at the level where that would be best done it doesn't know what the device is. Just even figuring out it's an IR device would require another trip to the server.

[rocker]

I'll add it to the list. Probably it's not going to be an immediate priority though. The downside of it is that it means going to the server to get the aliases every time an IR command is invoked, in order to do the translation, whereas the zone number is much lighter weight. And it also requires special casing IR field writes and at the level where that would be best done it doesn't know what the device is. Just even figuring out it's an IR device would require another trip to the server.

Portability is important even if we have to pay the small price in speed (this is the reason, most of us use hi level languages and not choose to optimize using assembly language).

Thank you for adding it to the list