pbir

ANNOUNCING THE NEW KEYPAD LOAD SIMULATOR DRIVER BY DOMOSAPIENS.
This driver has two distinct functions:
The driver may be connected to a normal keypad binding and provide LED feedback to the keypad and to its own Experience Button based on which state is currently active. States are determined by contacts and/or programming.  It can be tied to a Page Button Passthrough connection of the Domosapiens Keypad Pages driver and duplicate all the available events but for the specific button (this may significantly simplify your programming). In addition to ‘OFF’ and ‘ON’ states, this driver may have up to 3 additional ‘ON’ states called ‘ON2’, ‘ON3’ and ‘ON4’. These may be used to send different colors to the keypad LED and to the Experience Button. These additional states may be activated via Action/programming Command and optionally by activating a Contact Sensor.
IMPORTANT NOTE: if you have purchased the Domosapiens Keypad Pages driver, this Keypad Load Simulator driver will automatically be licensed in the same project.

I’m not sure that is 100% fair.  I have got 10s of third party drivers (quite possibly over 100) and I’ve really never had any real issues with licence transfers (when changing controllers or with changes like this one - where I’ve very easily moved 5 or 6 drivers from Blackwire to DC (adding the new driver just worked - both in terms of licensing and programming)).  While I do recall some challenges a decade ago, even then my dealer was able to get everything sorted.  In recent years, licensing issues have simply been a non-issue for me.
I have also found virtually all third party developers to be extremely helpful…

Announcing the availabllity of V14.0.0 of our popular Advanced Blind Control driver:
⦁    Enhanced control of any motorized shade connected to a Bond Bridge.
⦁    Enhanced control of any motorized shade controlled by two or three relays (Up, Down, Stop).
⦁    Ability to ‘encapsulate’ and enhance any third-party blind driver which currently supports only Up/Down/Stop with no feedback.
⦁    Interface with Control4 using the blind slider control with simulated positioning of blinds.
⦁    Ability to cause a one-way blind to move to any position reasonably accurately.
⦁    **NEW** SPECIAL Toggle/Stop keypad connection which provides additional control (used instead of normal Toggle).
⦁    **NEW** Ability to define a smaller limited area where the blind can operate when disabled (by an open door or window contact, for example).
⦁    **NEW** Ability to forward blind commands to other blinds, as an alternative to using groups.
⦁    Ability to control blinds via programming Events (Up, Down and Stop events with another driver actually sending the commands).  
⦁    Support for dual motion blinds via a new ‘Blind with Tilt’ driver (Event control only for the tilting part). 
⦁    Blind Driver Scenes which can easily position controlled blinds at any position (individually selectable).
 
The driver is available on DriverCentral at Advanced Blind Control

Announcing the availabllity of V14.0.0 of our popular Advanced Blind Control driver:
⦁    Enhanced control of any motorized shade connected to a Bond Bridge.
⦁    Enhanced control of any motorized shade controlled by two or three relays (Up, Down, Stop).
⦁    Ability to ‘encapsulate’ and enhance any third-party blind driver which currently supports only Up/Down/Stop with no feedback.
⦁    Interface with Control4 using the blind slider control with simulated positioning of blinds.
⦁    Ability to cause a one-way blind to move to any position reasonably accurately.
⦁    **NEW** SPECIAL Toggle/Stop keypad connection which provides additional control (used instead of normal Toggle).
⦁    **NEW** Ability to define a smaller limited area where the blind can operate when disabled (by an open door or window contact, for example).
⦁    **NEW** Ability to forward blind commands to other blinds, as an alternative to using groups.
⦁    Ability to control blinds via programming Events (Up, Down and Stop events with another driver actually sending the commands).  
⦁    Support for dual motion blinds via a new ‘Blind with Tilt’ driver (Event control only for the tilting part). 
⦁    Blind Driver Scenes which can easily position controlled blinds at any position (individually selectable).
 
The driver is available on DriverCentral at Advanced Blind Control

Announcing the availabllity of V14.0.0 of our popular Advanced Blind Control driver:
⦁    Enhanced control of any motorized shade connected to a Bond Bridge.
⦁    Enhanced control of any motorized shade controlled by two or three relays (Up, Down, Stop).
⦁    Ability to ‘encapsulate’ and enhance any third-party blind driver which currently supports only Up/Down/Stop with no feedback.
⦁    Interface with Control4 using the blind slider control with simulated positioning of blinds.
⦁    Ability to cause a one-way blind to move to any position reasonably accurately.
⦁    **NEW** SPECIAL Toggle/Stop keypad connection which provides additional control (used instead of normal Toggle).
⦁    **NEW** Ability to define a smaller limited area where the blind can operate when disabled (by an open door or window contact, for example).
⦁    **NEW** Ability to forward blind commands to other blinds, as an alternative to using groups.
⦁    Ability to control blinds via programming Events (Up, Down and Stop events with another driver actually sending the commands).  
⦁    Support for dual motion blinds via a new ‘Blind with Tilt’ driver (Event control only for the tilting part). 
⦁    Blind Driver Scenes which can easily position controlled blinds at any position (individually selectable).
 
The driver is available on DriverCentral at Advanced Blind Control

No, they are Zigbee devices.  They need to be identified.  I would add that the water valve has a very advanced Experience button which displays a lot of dynamic information.

No, they are Zigbee devices.  They need to be identified.  I would add that the water valve has a very advanced Experience button which displays a lot of dynamic information.

ANNOUNCING THE NEW DOMOSAPIENS KEYPAD MULTI CONNECTOR DRIVER
EVER WISH YOU COULD CONNECT SEVERAL DEVICES TO A SINGLE KEYPAD BUTTON ?
This Keypad Multi Connector (KMC) driver allows you to connect several BUTTON_LINK devices to a single keypad button, which is normally not possible.  The driver also has a flexible model for managing the colors and state of the real keypad button LED based on the controlled devices.  
Up to ten devices may thus be controlled by a single keypad button.  This approach may be more flexible than using Advanced Lighting Scenes or Blind Groups or even macros via programming, for example, as mix and match of device types with automatic LED feedback is now possible.
The driver is available on DriverCentral at Keypad Multi Connector

The Keypad Audio Control driver allows you to 'capture' audio from another room.  Up to three rooms may be designated for capture and the driver will capture the first room with its audio turned On.  This is actually the opposite of adding sessions using a T3/T4 screen (pull vs. push).

The Keypad Audio Control driver allows you to 'capture' audio from another room.  Up to three rooms may be designated for capture and the driver will capture the first room with its audio turned On.  This is actually the opposite of adding sessions using a T3/T4 screen (pull vs. push).

The driver disables the buttons of Configurable Keypads and Keypad Dimmers.  This is easily done as the driver sits between the keypad and the loads.  The loads themselves can still be controlled by a C4 app or touchscreen.

You could do this with one keypad (Menu plus 5 pages - not 6, unfortunately).  

Anywhere you would say "Gee, I wish I had some more buttons on this keypad !"
It is also a way to regroup functions: Lighting Scenes on one page,  individual Loads on another page, Shades/Blinds on their separate page, etc.

INTRODUCING OUR NEWEST DRIVER: KEYPAD PAGES 
This driver manages up to 5 ‘Virtual Pages’ (A to E) of keypad buttons for a single keypad, plus an optional Menu page.  This is easily managed by the user, and it allows a lot more power and flexibility in defining the usage of keypad buttons. 
The following functions are available: 
·       Ability to have up to 5 ‘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
·       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
·       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
This driver is available on DriverCentral at Keypad Pages

Easily allocate the 'next available source' from a pool of Watch or Listen sources
Powerful allocation schemes allow for exceptions
Several pools possible in a Project
This driver offers a way to share a limited pool of sources among a larger number of rooms.  You no longer need to design complex allocation schemes and the user no longer needs to wonder if a given source (a cable or satellite box, for example, or even an Apple TV or a Roku stick) is available. 
Instead of selecting a specific source under Watch or Listen, the user simply presses the new Experience Button (call it the ‘Pool Request’ button) available with this driver, thus asking the driver to determine the next available source from the pool and to activate it in the requesting room.  You would typically make this new button available under ‘Watch’ or ‘Listen’ in Participating Rooms.  You may install several instances of this driver in your Project, thus creating several Source Pools.
While sources are normally assigned in their specification order (‘A’, then ‘B’, then ‘C’, etc.), the driver allows for exceptions in specific rooms, which makes this process very flexible and customizable.  If the user in a given room requests a pooled source (by pressing this driver’s Experience Button) and all the sources are currently being used, the Button will provide feedback (Red) meaning that no sources are available.  The available feedbacks are:
-          Green: an available source has been assigned and activated
-          Red: no sources are currently available (as per the default sequence or this room’s Sequence Exception)
-          Orange: a source has been assigned, but it is not accessible in the given room (check your Sequence Exception for that room or specify one).
-          White: no source changes are being made (the room is already on a non-shared pool source – see the Property ‘Effect of Multiple Selects’)
Check out the driver at: DriverCentral

Easily allocate the 'next available source' from a pool of Watch or Listen sources
Powerful allocation schemes allow for exceptions
Several pools possible in a Project
This driver offers a way to share a limited pool of sources among a larger number of rooms.  You no longer need to design complex allocation schemes and the user no longer needs to wonder if a given source (a cable or satellite box, for example, or even an Apple TV or a Roku stick) is available. 
Instead of selecting a specific source under Watch or Listen, the user simply presses the new Experience Button (call it the ‘Pool Request’ button) available with this driver, thus asking the driver to determine the next available source from the pool and to activate it in the requesting room.  You would typically make this new button available under ‘Watch’ or ‘Listen’ in Participating Rooms.  You may install several instances of this driver in your Project, thus creating several Source Pools.
While sources are normally assigned in their specification order (‘A’, then ‘B’, then ‘C’, etc.), the driver allows for exceptions in specific rooms, which makes this process very flexible and customizable.  If the user in a given room requests a pooled source (by pressing this driver’s Experience Button) and all the sources are currently being used, the Button will provide feedback (Red) meaning that no sources are available.  The available feedbacks are:
-          Green: an available source has been assigned and activated
-          Red: no sources are currently available (as per the default sequence or this room’s Sequence Exception)
-          Orange: a source has been assigned, but it is not accessible in the given room (check your Sequence Exception for that room or specify one).
-          White: no source changes are being made (the room is already on a non-shared pool source – see the Property ‘Effect of Multiple Selects’)
Check out the driver at: DriverCentral

Currently working on a driver which does precisely this.
Stay tuned.
Paul

Currently working on a driver which does precisely this.
Stay tuned.
Paul

Currently working on a driver which does precisely this.
Stay tuned.
Paul

Currently working on a driver which does precisely this.
Stay tuned.
Paul

This setting for Capture Selector (prioritized rooms) was added not long ago and exposes three new properties allowing you to specify up to three different rooms for capturing: the first one which is ON will be captured, starting with Room 1, then Room 2 and Room 3.  If none of the three rooms is ON, then of course capture will not occur.
This allows you some flexibility in capturing rooms, as the user may not always know which one of his/her favorite rooms is ON at a given time.
The documentation will be updated.
I hope this helps.
Paul
 

100% sure our IT-100 driver will not work with Neo.  Only the stock Control4 driver will.

You really do not need the if statement, as these are one-way blinds.  Control4 does not physically know if the blind is fully closed or not and all you want is to issue a close/down command.  So, simply inform then close.   Inform will not break anything.
Paul

The Domosapiens Generic Somfy driver has a feature which could help, but only if you use a programming command.
The driver has a Device Specific Command 'Inform Blind'.  This was originally intended to inform individual blind drivers when myLink scenes were used, but it may be useful in other circumstances such as this.
Let's say the last operation done with the driver was to close (down) the shade.  Then, the user opens the shade using a Somfy remote.  The driver (and the Control4 proxy) think the shade is still closed and will not allow you to close it via Navigator.
The workaround is to use the following in programming for a 'Down' button:
    Inform Blind ... of Up/Open Movement
    Set the blind target level on ... to Closed
Similarly, for an 'Up' button:
    Inform Blind ... of Down/Closed Movement
    Set the blind target level on ... to Open
Paul Biron
Domosapiens

The Domosapiens Generic Somfy driver has a feature which could help, but only if you use a programming command.
The driver has a Device Specific Command 'Inform Blind'.  This was originally intended to inform individual blind drivers when myLink scenes were used, but it may be useful in other circumstances such as this.
Let's say the last operation done with the driver was to close (down) the shade.  Then, the user opens the shade using a Somfy remote.  The driver (and the Control4 proxy) think the shade is still closed and will not allow you to close it via Navigator.
The workaround is to use the following in programming for a 'Down' button:
    Inform Blind ... of Up/Open Movement
    Set the blind target level on ... to Closed
Similarly, for an 'Up' button:
    Inform Blind ... of Down/Closed Movement
    Set the blind target level on ... to Open
Paul Biron
Domosapiens