goldband said:
I am planning to rent the GH about 9 months each year and use it for my own guests for the other months. I would like to use
the Elk to protect both-- but it needs to be able to be controlled centrally by me when my guests are there, and controlled by the renters when the GH is rented. Any ideas about the best way to do this?
JP, I'm sure you know this, but it's really not that difficult, the hardest part for the end user is not having 1 fully automatic system based based on 1 condition and 2 independent system based on another conditional event. I think you're confusing my stating the system master code will always work in all areas with a single entry of this code arming/disarming 2 areas at the same time based on certain criteria rather than requiring a couple more keypresses to get to different areas or view all of the system's areas.
Acually, I just went to verify how "difficult" it was to view and then log on to my partitions on my own system and it's really not that painful.
It boils down to user heirarchy, and in commercial system terms, a system master, partition master or manager and user. The system master can control the entire system, change codes, etc. Partition master can only do such in their assigned areas, and in the M1's case, can be further limited by not allowing certain menu items or options. A user can only arm/disarm (or even be further limited by options) in their assigned partitions. I haven't had to try it on an M1, most other equipment, you may have a "manager" in one area that can do everything, but is simply a user in another, I'd wager that you could reuse a code and just give it different attributes in different areas and it would work in this method.
In the OP's case, both areas always controllable by single end user, just variation of using the keypad to login to a second area IMHO, basic ELK key menu option, could be finessed using F-keys and rules, even arm modes (vacation, nite stay, etc.) The renters code only affects a single area, which I'm sure the OP is going to maintain good code hygiene and delete once the space is no longer rented. I can't see the OP giving a full on training for their guests other than arm/disarm, if at all. Most of the locations I deal with that have guest spaces, the end user is primarily concerned when nobody (or renters in this case) are there and not when guests are present, so as to not burden them...but the OP would need to further clarify their requirements.