Short answer: No
The zone selection is stored in a cookie so that your browser will default to the last selected zone. But there is no way to specify a zone with the URL.
The display name is not used as a unique identifier in the software because of the possibility of duplication and that spaces in display names can be a pain to work with in a URL. That friendly display name is completely meaningless to the software - it is only displayed for user convenience.
The unique identifier for most things in the Roon api is the zone id. The zone selection buttons in the software show the friendly display name, but set the zone by zone id. The zone id is a unique 36 character hexadecimal number that is generated by the Roon core. And the zone id can change if zones get grouped and un-grouped. As an example, this is one of the zone ids for one of my systems:
As you can see, that is not exactly easy to remember.
The only exception is the output id which is used with the volume controls. And that is a different 36 character hexadecimal number which looks very similar to a zone id.
I think you are asking about the amount of time until the screen goes blank if there is no activity. If so, then in the system configuration section of the document here, step 7 is the
kiosk.sh file. There is a line that says:
xset dpms 60 60 60 &
That is where you would change the time out. The numbers are in seconds. The first number is standby, the second is suspend, the third is off. You can change the
60 to any number of seconds that you choose and this should survive a reboot. If you change this line, make sure that the
& is at the end or the script will hang and the browser wont start.
Any input event will wake up the screen. A keyboard press, a mouse movement, or a touch event are all input events that will wake up the screen. The most common for most people would be a touch event since most people do not have a keyboard or mouse attached.
Theoretically you can hook buttons to the GPIO pins on the Raspberry Pi and program a piece of software to convert a GPIO event to an input event. Another option would be to use LIRC to convert IR events to input events. But both of these options are WAY beyond the scope of this software.