pbir

Actually, with the Advanced Lighting Timer, you can do this with one Light On Level specification: D+45=0%,N-45=50%,N+60=95%
When using D/N ((Daytime and Nighttime) in the specification, view this as a continuous circular specification.  From 45 minutes after sunrise (D+45), the light will not come on (0%).  From 45 minutes before sunset (N-45) to 60 minutes after sunset (N+60), the light will come on at 50% (or whatever you want).  From 60 minutes after sunset, the light will come on at 95% until the next time specified in a circular way, which is D+45 (45 minutes after sunrise).  Using 95% instead of 100% is barely noticeable, but it allows the user to override the timer by turning the light ON manually, which is usually 100%.
Paul

It would be really nice if one could favourite a second residence to the Home Screen on the app.  This would make flipping between residences so much easier!

The driver supports this as tested by @BY96

When you have a single Selector button, multi taps are not supported, as it would defeat the purpose.  When you have several selector buttons, I believe each supports multiple taps and appropriate events are triggered.  Please verify, just in case.
Paul

@BY96  The Keypad Enhancer driver has events which are triggered when a Selector becomes active (1, 2, 3, ...).  These events are at the very bottom of the list in Programming.

@BY96The Keypad Audio Control driver does have the ability to associate the Up/Down keys to other buttons than the Selector button.  Look in the driver's documentation, in the section KEYPAD TRACKING.  This was introduced in V11.0.0.  The current version is 11.0.4.
Paul

Unfortunately not.  There is no way for the Keypad Enhancer driver to be notified of changes in the physical keypad.

If you set the button type to 'N', you may use the Single/Double/Triple taps (based on the 'MultiPress Used' property) as well as Press and Hold (and even Double and Triple Press and Hold).  The appropriate events will be triggered.  The 'H' button type is used when you want a different paradigm: two actions on a button (Single Tap or Press and Hold) to trigger two different events.  Folks coming to Control4 from Vantage are used to these two actions on a same button.

If you set the button type to 'N', you may use the Single/Double/Triple taps (based on the 'MultiPress Used' property) as well as Press and Hold (and even Double and Triple Press and Hold).  The appropriate events will be triggered.  The 'H' button type is used when you want a different paradigm: two actions on a button (Single Tap or Press and Hold) to trigger two different events.  Folks coming to Control4 from Vantage are used to these two actions on a same button.

Actually, you could trick this by connecting the driver’s button 5 to another button on the physical keypad…

If you set the button type to 'N', you may use the Single/Double/Triple taps (based on the 'MultiPress Used' property) as well as Press and Hold (and even Double and Triple Press and Hold).  The appropriate events will be triggered.  The 'H' button type is used when you want a different paradigm: two actions on a button (Single Tap or Press and Hold) to trigger two different events.  Folks coming to Control4 from Vantage are used to these two actions on a same button.

Actually, you could trick this by connecting the driver’s button 5 to another button on the physical keypad…

Actually, you could trick this by connecting the driver’s button 5 to another button on the physical keypad…

This driver has been designed as a front end to the Control4 Room Control driver.  It is therefore intended to manage a single room, but it may be connected to more than one keypad in that room.
There is also the possibility to 'capture' audio from another room and listen to it in the driver's designated room.
We do have another driver (Keypad Enhancer) which supports pressing both Up/Down buttons with related Events. This driver also has many other functions, such as a selector capability.
You could likely do what you want to do with a combination of the Keypad Enhancer driver, the Control4 Room Control driver and some programming.  

This driver has been designed as a front end to the Control4 Room Control driver.  It is therefore intended to manage a single room, but it may be connected to more than one keypad in that room.
There is also the possibility to 'capture' audio from another room and listen to it in the driver's designated room.
We do have another driver (Keypad Enhancer) which supports pressing both Up/Down buttons with related Events. This driver also has many other functions, such as a selector capability.
You could likely do what you want to do with a combination of the Keypad Enhancer driver, the Control4 Room Control driver and some programming.  

Announcing a new Version (V11) of our very powerful Advanced Lighting Selector driver.
New features: selectable Driver Capabilities with simpler startup point, new NUM and BOOL variables, new Room conditional
The driver is available on DriverCentral at Advanced Lighting Selector
Again, special thanks to @South Africa C4 user for his insightful suggestions and his testing.
Paul

I’ve got two main real world use cases at the moment (a few instances of each) and I am planning more.  
 
First use case is a double gang setup in the main open plan area of our house where the first keypad determines what area the second keypad controls (using 6 pages).  So the first keypad has the following 6 buttons:
1. Atrium
2. Dining Room
3. Lounge
4. Kitchen
5. Outside 
6. All areas
An LED on the above keypad shows which area is active. It defaults to All Areas after 30 seconds of no use.  The second keypad has the following 6 buttons:
1. Downlights
2. Rope Lights
3. Chandeliers
4. Floor Lights
5. Upstairs
6. Downstairs
The last 2 buttons are pass through buttons (so are not impacted by the first keypad) and simply turn off all upstairs / downstairs lights and have an LED to show if any upstairs / downstairs light is on.
The first 4 buttons is where the magic of the driver happens.  If one pushes kitchen on the first keypad then the LEDs on the first 4 buttons of the second keypad instantly update to show if the kitchen downlights, rope lights etc. are on / off.  One can then control (toggle) the various kitchen lights using the second keypad. Pressing the lounge button (for example) updates the LEDs on the first 4 buttons on the second keypad to show the state of the relevant lounge lights and the buttons now control the lounge lights.  My All Areas button is actually Lounge, Dining Room and Atrium (technically the inside areas) and pressing this gives feedback as to whether any downlight etc. is on in any of the areas (lounge, dining room, kitchen and atrium).  Pressing the relevant button (eg Chandeliers) turns on / off all of the chandeliers (kitchen, lounge and dining room). 
All of this is setup via the driver properties and connections so very easy for a dealer to implement quickly.
My second example uses a single keypad in my master bedroom suite and only 2 pages.  The 6 buttons are:
1. Downlights
2. Rope lights 
3. Chandelier
4. Passage Light
5. Suite off
6. Room / Suite
 Button 6 swaps the control for the top 3 buttons between the buttons controlling the room lights only or all the lights in the suite (Balcony, TV nook and bedroom itself).  Button 6 gives LED feedback on whether the keypad is controlling the Room (LED off) or the suite (LED on).  Control defaults back to room control after 30 seconds.
Pressing the Downlights button will normally turns on/off the downlights in the bedroom only.  Pressing Room / Suite and then the downlights button turns on/off the downlights in the TV area and the main bedroom (similarly for chandeliers and rope lights).  For instance, I often press the Room/suite button followed by Rope Lights no Chandeliers to turn on rope lights and chandeliers in the whole area.  
The Passage and Suite off buttons are pass through buttons which do the same thing irrespective of what page (room or suite) the keypad is on.  Again, all of this is achieved via properties and bindings.
My family have taken to the new setup and love it - particularly the first use case above.  I will be ordering new buttons for a number of the double gang keypads at both of my houses and getting a licence for the driver at my second house so that I can implement use case 1 in a number of places.  This has created a lot more flexibility for me using 2 keypads to control up to 36 loads / scenes in a fashion that my family find intuitive.!
Great driver!
Another use that I am playing around with is to use the up / down arrows to change what page of lights is controlled and use backlighting to give the relevant feedback as to what room is being controlled.

Announcing a new version of our Keypad Pages driver, now even more powerful:
⦁    Ability to have up to 7 ‘virtual’ pages for each keypad, thus significantly expanding the number of buttons available. 
⦁    An optional Menu page is also available for easier navigation
⦁    Pages can be selected by the user (navigation) or via Programming and Actions
⦁    Keypad LEDs are managed automatically based on the Page selected, Color properties and the state of connected devices
⦁    The keypad may automatically revert to the Menu page or to Page A after a selectable timeout
⦁    All keypad button actions and ‘clients’ are supported
⦁    (*NEW*) Slave keypads may be controlled by a master keypad so that they are synchronized 
⦁    Special normally hidden pages may be activated easily, such as Guests, Party or Support. 
⦁    An Up/Down Tracking facility is available to have the Up and Down buttons track to the last button pressed with optional LED feedback
⦁    When Tracking, an optional 8th button is available via simultaneously pressing the Up and Down buttons (Domosapiens exclusive)
⦁    A Special Double Tap facility is available to simplify Single Tap/Double Tap processing
⦁    (*NEW*) A Night Mode (activated by programming) allows the keypad to be dark until a key is pressed.
⦁    (*NEW*) The keypad’s Backlight may be managed by the driver and optionally used to indicate which page is currently active.
⦁    Page names may be specified for easier reference in Connections, Programming and Actions
⦁    An additional passthrough (ALL) Connection is always available, regardless of the Page selected
⦁    Supports the Domosapiens Keypad Load Simulator driver for simpler programming.
 
The driver is available on DriverCentral at: Keypad Pages
With special thanks to @South Africa C4 user for his many suggestions and his thorough testing.
Paul

Included and Free are nice for the budget, but we're much better off with the the current partnerships.
The ability for others to add key function to a system is huge. We're not tied to the corporate development path.
When Extra Vegetables got absorbed, there was a lot less ability to push the envelope, for a time.
The second wave of 3rd Party Developers have enhanced the platform so much, and strengthened it.
They get hired by vendors to develop free drivers, they add other platforms which Control4 would not bother to address (or are competition) and which the vendor wouldn't expense a driver or see the need to. They listen to dealers needs and create enhancements to the programming ability, saving time and adding more abilities quicker than Control4 could react. And Control4 appears to respect the work the developers do by not incorporating their solutions and cutting off their revenue and stifling creativity.
I don't feel Control4 is relying on them, rather sees them for what they are, an asset to work with, which was evident when the color 'module' was added to Control4 and the developers stepped right up for an almost day of update across multiple developers.
 

@RAV Your suggestion makes sense to help dealers better understand  the driver which is indeed complex (because it can do so many things).  However adding a second pared down driver would make things more difficult to synchronize in the future. I have therefore decided to take your example and add a QUICK START section at the very beginning of the documentation.  Can't be missed!
-----------------------------------------------------------
QUICK START – A SIMPLE EXAMPLE
Ask: the client wants to use one keypad button to activate/deactivate a Lighting Scene during the day and a different Lighting Scene at night.  The keypad button LED must show the state of the Scene.
Solution: 
⦁    Install the driver.  Do not modify any properties other than the ones outlined below.
⦁    In Agents/Advanced Lighting, create the Daytime and the Nighttime Lighting Scenes to turn on the required light(s) at the required level(s).  Also create the Default Toggle Scene for each.  As you have modified the Scenes setup, run the driver’s Action ‘Refresh Advanced Lighting Scenes’.
⦁    Use the properties Select Advanced Lighting Scene A to point to your Daytime Scene and Select Advanced Lighting Scene B to point to your Nighttime Scene.
⦁    Set the Control Logic When Activating/ON property to: d = A ; n = B   This means that the first program will activate Scene A during daytime (lowercase d) and the second program will activate Scene B during nighttime (lowercase n).
⦁    Connect the driver’s Toggle Button Link L to the desired keypad button.  You may modify the properties for Keypad LED Active/ON Color and Keypad LED Inactive/OFF Color if you wish.
You are done!  Now, read on…
-----------------------------------------------------------
I hope this will be helpful and point dealers in the right direction.
Paul
P.S. to ALL: Do have a look at the driver's Action to '** Print ALS Reports', especially the Cross Reference report which was asked for in these forums just a few weeks ago.

@RAV Your suggestion makes sense to help dealers better understand  the driver which is indeed complex (because it can do so many things).  However adding a second pared down driver would make things more difficult to synchronize in the future. I have therefore decided to take your example and add a QUICK START section at the very beginning of the documentation.  Can't be missed!
-----------------------------------------------------------
QUICK START – A SIMPLE EXAMPLE
Ask: the client wants to use one keypad button to activate/deactivate a Lighting Scene during the day and a different Lighting Scene at night.  The keypad button LED must show the state of the Scene.
Solution: 
⦁    Install the driver.  Do not modify any properties other than the ones outlined below.
⦁    In Agents/Advanced Lighting, create the Daytime and the Nighttime Lighting Scenes to turn on the required light(s) at the required level(s).  Also create the Default Toggle Scene for each.  As you have modified the Scenes setup, run the driver’s Action ‘Refresh Advanced Lighting Scenes’.
⦁    Use the properties Select Advanced Lighting Scene A to point to your Daytime Scene and Select Advanced Lighting Scene B to point to your Nighttime Scene.
⦁    Set the Control Logic When Activating/ON property to: d = A ; n = B   This means that the first program will activate Scene A during daytime (lowercase d) and the second program will activate Scene B during nighttime (lowercase n).
⦁    Connect the driver’s Toggle Button Link L to the desired keypad button.  You may modify the properties for Keypad LED Active/ON Color and Keypad LED Inactive/OFF Color if you wish.
You are done!  Now, read on…
-----------------------------------------------------------
I hope this will be helpful and point dealers in the right direction.
Paul
P.S. to ALL: Do have a look at the driver's Action to '** Print ALS Reports', especially the Cross Reference report which was asked for in these forums just a few weeks ago.

@RAV Your suggestion makes sense to help dealers better understand  the driver which is indeed complex (because it can do so many things).  However adding a second pared down driver would make things more difficult to synchronize in the future. I have therefore decided to take your example and add a QUICK START section at the very beginning of the documentation.  Can't be missed!
-----------------------------------------------------------
QUICK START – A SIMPLE EXAMPLE
Ask: the client wants to use one keypad button to activate/deactivate a Lighting Scene during the day and a different Lighting Scene at night.  The keypad button LED must show the state of the Scene.
Solution: 
⦁    Install the driver.  Do not modify any properties other than the ones outlined below.
⦁    In Agents/Advanced Lighting, create the Daytime and the Nighttime Lighting Scenes to turn on the required light(s) at the required level(s).  Also create the Default Toggle Scene for each.  As you have modified the Scenes setup, run the driver’s Action ‘Refresh Advanced Lighting Scenes’.
⦁    Use the properties Select Advanced Lighting Scene A to point to your Daytime Scene and Select Advanced Lighting Scene B to point to your Nighttime Scene.
⦁    Set the Control Logic When Activating/ON property to: d = A ; n = B   This means that the first program will activate Scene A during daytime (lowercase d) and the second program will activate Scene B during nighttime (lowercase n).
⦁    Connect the driver’s Toggle Button Link L to the desired keypad button.  You may modify the properties for Keypad LED Active/ON Color and Keypad LED Inactive/OFF Color if you wish.
You are done!  Now, read on…
-----------------------------------------------------------
I hope this will be helpful and point dealers in the right direction.
Paul
P.S. to ALL: Do have a look at the driver's Action to '** Print ALS Reports', especially the Cross Reference report which was asked for in these forums just a few weeks ago.

@RAV Your suggestion makes sense to help dealers better understand  the driver which is indeed complex (because it can do so many things).  However adding a second pared down driver would make things more difficult to synchronize in the future. I have therefore decided to take your example and add a QUICK START section at the very beginning of the documentation.  Can't be missed!
-----------------------------------------------------------
QUICK START – A SIMPLE EXAMPLE
Ask: the client wants to use one keypad button to activate/deactivate a Lighting Scene during the day and a different Lighting Scene at night.  The keypad button LED must show the state of the Scene.
Solution: 
⦁    Install the driver.  Do not modify any properties other than the ones outlined below.
⦁    In Agents/Advanced Lighting, create the Daytime and the Nighttime Lighting Scenes to turn on the required light(s) at the required level(s).  Also create the Default Toggle Scene for each.  As you have modified the Scenes setup, run the driver’s Action ‘Refresh Advanced Lighting Scenes’.
⦁    Use the properties Select Advanced Lighting Scene A to point to your Daytime Scene and Select Advanced Lighting Scene B to point to your Nighttime Scene.
⦁    Set the Control Logic When Activating/ON property to: d = A ; n = B   This means that the first program will activate Scene A during daytime (lowercase d) and the second program will activate Scene B during nighttime (lowercase n).
⦁    Connect the driver’s Toggle Button Link L to the desired keypad button.  You may modify the properties for Keypad LED Active/ON Color and Keypad LED Inactive/OFF Color if you wish.
You are done!  Now, read on…
-----------------------------------------------------------
I hope this will be helpful and point dealers in the right direction.
Paul
P.S. to ALL: Do have a look at the driver's Action to '** Print ALS Reports', especially the Cross Reference report which was asked for in these forums just a few weeks ago.

ANNOUNCING THE NEW DOMOSAPIENS ADVANCED LIGHTING SELECTOR DRIVER
This driver is used to dynamically select and activate/deactivate Advanced Lighting Scenes, based on simple or elaborate Control Logic you define in Properties.  When requested (triggered) by the user, Scene selection may be controlled by time of day as well as the state of several conditions: other lights or scenes, blinds, security partitions, contacts, day of week, ambient lighting, and programming variables.  This is intended to be very flexible and powerful, yet easy to specify.
In addition, with its extensive ALS Reports, this driver may be used to document all elements of Advanced Lighting Scenes in a Project (something that Composer does not yet provide), as well as produce a comprehensive Cross Reference list of Scenes, Lights and Rooms.
The driver can be found at Advanced Lighting Selector on Drivercentral

ANNOUNCING THE NEW DOMOSAPIENS ADVANCED LIGHTING SELECTOR DRIVER
This driver is used to dynamically select and activate/deactivate Advanced Lighting Scenes, based on simple or elaborate Control Logic you define in Properties.  When requested (triggered) by the user, Scene selection may be controlled by time of day as well as the state of several conditions: other lights or scenes, blinds, security partitions, contacts, day of week, ambient lighting, and programming variables.  This is intended to be very flexible and powerful, yet easy to specify.
In addition, with its extensive ALS Reports, this driver may be used to document all elements of Advanced Lighting Scenes in a Project (something that Composer does not yet provide), as well as produce a comprehensive Cross Reference list of Scenes, Lights and Rooms.
The driver can be found at Advanced Lighting Selector on Drivercentral