I have just pushed up a new version of QnetGateway that has a new feature if you are likely to be routing to your favorite group (or user) right after boot-up. Using this feature should prevent you from getting the "not in cache, please try again" message. The feature is controlled by a new configuration parameter, gateway_find_route. This parameter is a comma-separated list of routing callsigns that you would like to have in your cache when qngateway first boots up. You can put your favorite routing callsign that you are likely to use and as qngateway boots up, it will request from QuadNet the latest contact info for each of the callsigns in your list. For example, mine looks like:
gateway_find_route='dstar2,dstar3,qnet20 c, w1bsb'
You can set this parameter in the Gateway sub-menu of the ./qnconfig script. Note that you can also add user callsigns to this list as well, if you do Callsign Routing. (Colby, W1BSB, and I do this fairly regularly!)
This feature will greatly simplify the script I listed previously in this thread as you will only need to call qnremote once for each group you want to subscribe to, as long as the groups in that script are also in the gateway_find_route list.