Hunter Douglas PowerView

MSRP: $0.00
[Sign in for more info]
Cinegration LLC
Hunter Douglas PowerView Driver for Control4.  This driver is a scene selection driver only.  Support both Gen 1 and Gen 2 PowerView hubs.

Driver Download (Hunter_Douglas_PowerView_Driver.zip, 4,867 Kb) [Download]

No posts found

Write a review

Driver: Hunter Douglas PowerView Hub

Compatible Control4 Systems:  2.9.0+
Compatible Hardware: PowerView Shading System
Control Platform: IP (Requires Static IP or DHCP Reservation)
Developed by: Cinegration LLC.  www.cinegration.com/drivers
Change Log:

      Version 1001 (2.2017)

Release of Driver

  • Version 1004 (4.2017)
    • Fixed issue with downloading more than 40 scenes would not populate scene list
  • Version 1005 (4.2017)
    • Fixed issue where multi and room scenes would not be updated correctly because they were the same id.
    • Updated Documentation.
  • Version 1006 (7.2017)
    • Updated core to support driverCentral functions.
    • Updated to support Gen2 PowerView Hubs

Driver Overview:  Using this driver allows a Control4 dealer to trigger scenes on a PowerView system.  The driver sends Scene triggers to the PowerView hub. This driver DOES NOT control individual shades. 

Driver Features:

      IP Communication

      Relay Connection for each scene from PowerView

      Composer Programming actions (scene names or scene id’s)

      Device Connection online/offline reporting

      Drop down list in properties of all available scenes.

      Use scene name or scene id in composer programming.

Description of Items in Driver

  Property List (System Design)

      Driver Version

o      Current Driver version install on project

      Driver Persistence

o      Current saved state of driver data. (note: if this says ‘Not Saved’ and director reboots, the data will not be available on Load of driver).

      Driver Information

o      Driver Specific information

      Debug Mode (Default: Off)

o      Used to view the driver log.  Debug will turn off automatically after 15 minutes

      Device Connection

o      Current Device State (Online or Offline, Failed to Check in)

      Hub IP Address

o      The IP address of the PowerView Hub (note: must be configured for static ip)

      Scene List

o      Convenient scene list for reference only (includes sceneId and sceneName values)

      Polling Timer (Seconds)

o      Amount of time between polling checks.  If 0 then polling is disabled.

 

Actions Tab (System Design) – This is now located under Property: Driver Actions

      Request Scene List

o      Request scene data information from PowerView Hub

      Sync Scene Data

  • Takes current list of scenes from PowerView and updates the driver tables and connections automatically.
  • Create scenes for each ‘state’ you would like to have. Example, customer wants ‘All Up, All Down and Morning (shades open, blinds down).
  • Set IP Address to a static IP

Initial Setup/Installation of Driver

 

PowerView Hub Setup

            Setup Shades and Hub per standard setup practices on PowerView

 

            Setup Control4 Driver:

      Choose Driver Actions: Request Scene List

      Choose Driver Actions: Sync Scene Data

      Use Standard Control4 practices for Custom Buttons or bind a relay to the proper relay binding to trigger event

Example 1: Using Custom Buttons and scene names to trigger scenes:

 

In this example: 2 custom buttons have been created and when these buttons get pressed the Control4 programmer ‘triggers’ the specific blind scene names.

Note: The scene names must be entered the same as what’s in the app.

            Note: If the customer changes the scene names in the app AFTER deployment of System, the driver will continue to work as the driver references the ID name.  Note: If the dealer syncs the data on the driver, the scene names will be updated.  It is recommended to use sceneId if possible to avoid possible scene Name issues.

            Note: Scene names REQUIRE room name or multi: including the scene name.  Example: Dealer created All Up in room (bedroom).  The ‘sceneName’ would be bedroom:All Up  If this was a Multi-room scene the scene name would be multi:All Up  


 

Example 2: Relay Bindings and scene names to trigger scenes:
Select Shades on the screen.

 

 

Note: Up, Stop and Down commands for each Scene only ‘trigger’ the scene. They do not move the shades up/down unless that is what the ‘scene’ is supposed to do.

 

 

Special Notes/Tips:

                This driver does not control individual blinds.  Dealers will need to create specific scenes for open/close and trigger those scene names in either Composer Programming or create blind bindings to trigger the specific scenes.

 

Example of Properly Integrated Main Page:

 

About Driver Notes:

     This driver contains code written by Cinegration for Hunter Douglas.  Any modification to this driver without the express written permission by Hunter Douglas without the express consent will void all warranties, constitute a ban on all drivers released by Cinegration and potentially legal action.

     This driver has been designed to work with Control4 2.9.0 and higher Control4 systems.

 

Warranty:

      Cinegration strives to provide fully working drivers without defects.  However, changes and bugs may be found.  Because of this, any bug/maintenance update to this driver will be free of charge. However, due to the ever-changing nature of computer and audio/video systems, if a new version of the Control4® software creates issues with this driver, or feature enhancements, an upgrade version will be provided for an additional expense or free as determined by Hunter Douglas.

 

Change Log:

      Version 1001 (2.2017)

Release of Driver

  • Version 1004 (4.2017)
    • Fixed issue with downloading more than 40 scenes would not populate scene list
  • Version 1005 (4.2017)
    • Fixed issue where multi and room scenes would not be updated correctly because they were the same id.
    • Updated Documentation.
  • Version 1006 (7.2017)
    • Updated core to support driverCentral functions.
    • Updated to support Gen2 PowerView Hubs
  • Version 1008 (10.5.2017)
    • Fixed JSON error in 2.10 Control4 systems
    • Added scanning tool for easier hub integration