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.

The equivalent thermostat with home automation and a driver is the Aprilaire 8840.

Thanks for the feedback. Glad this worked out for you.

In our Leviton/HAI driver, follow the process outlined for Somfy ILT blinds: 1. HAI manages the Somfy ILT blinds as lights. Name such units in PCAccess with a name starting with $ or > such as '>Guest BO W' and reload into the HAI panel. When you run the Action 'Update Unit/Lighting Names' in our driver, these will be imported and an HAI_LIGHTING connection will be created for each such Somfy ILT Blind. The alternative is to set our driver's Property 'Prefix for Unit Names' to 'Prefix not required...'. When you run the Action 'Update Unit/Lighting Names', a lot of new bindings will possibly be created (one for each unit specifically named in PCAccess, which should be OK for your installation), but it frees you from modifying your current unit names in PCAccess. 2. Instead of connecting one of our Lighting drivers to these blind-related HAI_LIGHTING connections, connect our Somfy ILT Blind driver which comes in the download package. 3. You should be able to control the ILT blinds this way.

https://www.c4forums.com/forums/topic/42004-leviton-rs485-somfy-ilt-blinds-and-cbus-with-control-4-solution-required/?do=findComment&comment=323551

See my response in the other thread.

If your Somfy ILT blinds are indeed controlled by the Leviton/HAI Omni security panel, then our Leviton/HAI IP driver, available on DriverCentral, could probably help you, as it has a Control4 driver to handle such Somfy ILT blinds (which Leviton/HAI actually treats as lights). The only important requirements are that your Leviton/HAI panel be IP capable (our driver only speaks IP, not RS232) and be running Leviton/HAI firmware V3.0 or higher. The driver has a 7-day free trial period for you to test it out and see if it will solve your issue. Otherwise, the new Somfy Digital Motor Interface (ZigBee) might be a solution. I do not know, however, if it will support your type of ILT motors. The driver itself is certified and free in the Control4 Online Driver Database, but you will need one such interface per motor.

If you already have the free URTSI driver, the Advanced Blind Control driver can encapsulate it and provide all the advanced features listed above. Otherwise, as Cyknight said, simply use our Somfy Generic RTS driver which supports the URTSI and has the timing model.

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.

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 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.

Our Keypad Enhancer driver allows you to disable all keypads in a group or even all keypads in the house with one programming command. Available on Drivercentral.io

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

I’m having this issue as well. Reported to C4 earlier this week.

@C4 User Since Somfy RTS motors provide no feedback, you need to understand that TaHoma will do its own thing, as well Control4. So if you, for example, open the patio screens with TaHoma, it will remember that its last operation was 'Open' and assume that the shades are now open. If you later close them with Control4, the TaHoma app will not know that the shades are closed and it will show them as open and assume they are open. Control4 would also be in a similar situation if you do the above, but with the opposite device. This is why it is never recommended to manage one-way blind motors from two different systems.

The TaHoma driver only supports the North American TaHoma device. There is no known support for the European TaHoma. In Europe, a good solution to control RTS motors is to use the Somfy RS485 RTS Transmitter. We have a driver supporting this on DriverCentral with simulated positioning to enhance user experience. Using Bond is also an option. Please note that if the user wishes to sometimes control the motors with TaHoma and sometimes with Control4, everything will likely get out of sync, which is not pretty. It is best to use only one system to control the Somfy RTS motors, as they do not provide feedback. Paul Biron

The driver updates the time in the thermostat every night at 3:01 am. If the time is still wrong tomorrow morning, please let me know.

Cyknight is right. Even if you were to connect one or a few EA-1s to an HDMI matrix (a very big one, if you have 20 TVs), Control4 handles OSD in a different way and this driver wouldn't help you with this specific need (OSD). If, however, you have video sources (cable, satellite, etc.) connected to a matrix, then this Source Pooling driver could definitely help.

Yes, as long as you have one separate mini app (Netflix, for example) connected to each box. You could define Netflix Roku 1, Netflix Roku 2 and Netflix Roku 3 as three separate sources and the driver would make all the necessary connections.

See the announcement of our new Source Pooling driver under Third Party Software. Paul

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