Jump to content


c4Forums Member
  • Content Count

  • Joined

  • Last visited

1 Follower

About pbir

  • Rank
    Control4 End User

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Montreal, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Our driver covers essentially all RTS controllers with motion simulation (%open/closed). It supports groups and offers a lot of flexibility in configurations. The main RTS controllers you could use are: myLink (the newest in the group), URTSI II and the RS485 RTS transmitter (popular in Europe). It has a 7-day free trial period.
  2. Our Somfy driver, available on driverCentral, fully supports the RS485 RTS transmitter and includes the new blind interface available since OS 2.9.
  3. All the Sinope thermostat drivers use the new Navigator interface, including presets and schedule.
  4. Yes, it does, for each button of the keypad. The driver has a property to specify if you are using double or triple taps anywhere. If so, the driver will ensure that the single tap event is not triggered if you do a double tap (there will be a small delay). Similarly, single and double will not be triggered if you do a triple tap.
  5. Have a look at our Keypad Enhancer driver on driverCentral (Domosapiens). It adds several capabilities to a C4 keypad, such as: MultiPress & Hold, 8th virtual button, mutually exclusive events, Keypad lockout, Up/Down Selector, LED Color and Blinking.
  6. The dealer cost has just been revised. MSRP is now $55 USD.
  7. My understanding is that io-homecontrol uses European-only frequencies and would possibly not be allowed in North America. Also, it is a closed protocol, limited only at this time to Somfy control units, not open to being controlled by a home automation system like Control4. This might change, but for now, RTS looks like it is still Somfy's wireless approach in North America.
  8. You will be able to control from Control4 by connecting the URTSI to a serial port and using an appropriate driver. No wires to the blinds other than power are required. Make sure first that you can operate your blinds using the Somfy remote, then program the URTSI and verify that it operates the blinds (it has buttons) and then Control4. You can try the Domosapiens driver on HouseLogix for free during 2 days.
  9. Let me see if I can help a bit (I wrote the Somfy driver referenced by blub). This driver supports Somfy RTS (one-way) blinds via the new Somfy myLink interface, which is an IP-connected device. It also supports Somfy SDN (two-way) blinds via the Somfy UAI interface, which is a serially-connected device (RS232). After adding the interface driver (capable of supporting myLink and UAI simultaneously), you add one blind driver for each blind in your project. Each blind can then be defined as an RTS blind or an SDN blind. The installation is quite straightforward. The other alternatives for controlling Somfy RTS blinds typically use the Somfy 16-channel URTSI II in North America or the Somfy 16-channel RT485 RTS Transmitter elsewhere. Free drivers exist with limited functions, but I have a driver on HouseLogix which supports virtually everything RTS, along with an elaborate timing model which interfaces nicely with the new blind interface available in OS 2.9.
  10. I learned Lua specifically to write C4 drivers and really love the language, especially tables. Ryan's perspective above makes a lot of sense.
  11. The Domosapiens driver also has zone names. The zone name having likely triggered the alarm is in the LAST_ZONE_NOTREADY_NAME variable. This was introduced about a year ago in driver version 2.1.2.
  12. The Domosapiens Somfy V3 driver on HouseLogix also supports the new myLink with a timing model. The free myLink driver has open/closed only. The Domosapiens driver extends its elaborate timing model to the myLink, allowing simulated visual feedback as well as reasonably accurate % open or % closed requests.
  13. Your dealer needs to add them to the project and connect them to zone bindings. Then, you can do all you want in programming.
  14. Sorry to contradict, but you DO NOT need a $ sign for zone names. I just double-checked on my test system and in the code itself (I wrote the driver). Also, to make sure, I just deleted and completely reinstalled the driver on my test system and it correctly read the zones from the panel, including the names, without a $ sign. To further test, I then changed a zone name with PCAccess and downloaded it to the panel. Used the driver's Action 'Update Zone Names' and the name was promptly and properly updated in Composer (Properties area). No $. There has to be another issue. Paul
  15. Look at the section on Managing Zones in the PDF documentation which comes with the driver. Starting on page 11. It should answer your questions.
  • Create New...