Hi Matt,
Thanks for the prompt help. I though of duplicate pages, but I expect to have four or five browser locations. That's a lot of work to change each of five pages for every minor change I want to make. Besides, the idea of doing it that way, instead of programatically, bothers me!
There's one thing I don't understand. When I first fire up the browser, I can type the browserId into the URL. However, all subsequent URLs are generated from the _pageelem.html template through clicks on the page. I'm not sure how it figures out which browserId to insert.
I assume the template generates the page on-the-fly when the browser requests it. Does the template have access to cookies? If so, I could modify the 1015 type in _pageelem.html to check for page=local, then use if/thens to generate the appropriate target URL, depending upon the cookie value (bedroom, office, etc.). Indigo doesn't need to create the cookies--I can do that with a php page--only read them.
Does this make sense, or am I missing something?
Thanks,
Jeff
P.S. Here's a typical "local" control page. I'm planning to use an internet tablet with a 3.5" x 2" screen. All tabs on each browser go the the same control page except for LOCAL, which goes to bedroom, office, etc., depending upon which browser/tablet is doing the calling.