pbir

c4Forums Member
  • Content count

    14
  • Joined

  • Last visited

About pbir

  • Rank
    Control4 End User

Contact Methods

  • Website URL
    www.domosapiens.ca

Profile Information

  • Gender
    Male
  • Location
    Montreal, Canada
  1. 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.
  2. 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.
  3. 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.
  4. I learned Lua specifically to write C4 drivers and really love the language, especially tables. Ryan's perspective above makes a lot of sense.
  5. 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.
  6. 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.
  7. Your dealer needs to add them to the project and connect them to zone bindings. Then, you can do all you want in programming.
  8. 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
  9. 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.
  10. Again, you do not need to have the $ signs in front of zone names. I suggest you remove them. Judging by this, the driver will define zones 1 to 80.
  11. Zones do not need any special character. What the driver does is read all the zone names from the panel. The panel sends only the zones with a name defined in PCAccess. This is why it is necessary to have at least the highest-numbered zone you need named properly. This way, the driver will set up zones starting at 1 up to the highest one you need and assign the names it has received from the panel. If a zone in the range does not have an HAI name, it will be called 'Zone nnn' in Control4. Support is provided by HouseLogix directly (now owned by SnapAV).
  12. I just saw these posts. If the zones are named in the HAI panel configuration (using PCAccess) and downloaded to the HAI panel, then the driver is able to re-read the zone names using the Action 'Update Zone Names' in Composer. There is no special naming requirement for Zone names, other than having the highest-numbered zone named. This was done to avoid creating unnecessary zones in Control4. I see that you do not need lighting or thermostats, but thermostat naming is similar to Zone naming. In the case of UPB lighting, there is a need to prefix the HAI name with a special character($ or >) to identify this unit as a lighting unit (the other alternative is a relay unit which uses a different prefix character - &). Paul Biron, Domosapiens
  13. If you use the Domosapiens IT-100 driver available on HouseLogix, you have access to variables containing the user number AND user name having armed/disarmed the system. These variables can then be used in a notification, for example. Paul
  14. Look at the HAI IP driver available from Extra Vegetables. It supports thermostats. Paul Biron