- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
- Voice Control
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
- Voice Control
PowerView Motorization consists of a PowerView Hub plus a collection of motorized shades and other accessories, including remotes, repeaters, secondary hubs, and scene controllers. Shade resources are the central concept in the PowerView API eco-system. Hubs communicate with Shades over a radio interface while the REST API is terminated over an HTTP based interface.
Driver Developed By:
Control Concepts
Control Concepts Technical Support:
Phone: 201.797.7900
E-Mail: projects@controlconcepts.net
PowerView Gen3 Driver
Description
This driver is for control of PowerView Gen3 compatible devices. This driver communicates exclusively with the gateway device to signal actions on the endpoint devices.
The PowerView application can be downloaded from the Apple App Store and Google Play. This app will be required for setup and configuration of the Gateway and endpoint devices.
https://apps.apple.com/us/app/powerview-app/id1009384826 https://play.google.com/store/apps/details?id=com.hunterdouglas.powerview
A demo Integration Designer project has been created to demonstrate general usage of this driver.
Note: This document is not a replacement for understanding the equipment you’re controlling and the documentation that is distributed with the equipment. Please read and understand all documentation before attempting to use this driver.
Revision History
v1.0.0 : Initial Release
v1.1.0 : Compatibility update for FW version 3.1.398
v1.2.0 : Major bug fixes and improvements
Known Issues
No motion-start event for primary motor of shade capability type 9.
Current positions not always end on target position
Connection Settings
All communication between the Gateway and the driver will occur over a TCP connection via port 80. The IP address of the Gateway can be entered in the driver settings.
Initialization Sequence
Once driver communications have been started and a successful handshake has been completed, the driver will automatically start polling the Gateway for the current state of all registered endpoints. Once the driver has successfully acquired the state of all endpoints, it will be considered initialized. No commands should be sent for endpoint control until this process is complete.
Driver Configuration
Debug Settings
Only visible if "Show Driver Debug Options" has been set in TraceViewer.
Enable Debug Messages
Enables the driver debugging messages.
Debug Level
Determines which debug messages to show.
Identifier
Prefix for debug messages to distinguish debug messages from this driver.
Network Settings
IP Address
IP Address of the Gateway.
Auto Connect
If enabled, the driver will automatically attempt to connect to the gateway and initialize the state of all endpoints as soon as it is ready after processor startup and will maintain this connection. If disabled, the connection process will need to be started manually via driver connection functions.
Device Configuration
Shade Count
Determines the number of shade endpoint devices the driver will control. A single instance of the driver supports up to 1000 of these devices.
Scene Count
Determines the number of predefined scenes the driver will control. A single instance of the driver supports up to 1000 of these scenes.
Shade Settings
Shade Name [1-1000]
Defines a friendly name for the endpoint device.
Shade ID [1-1000]
Defines the unique ID of the endpoint device.
Scene Settings
Scene Name [1-1000]
Defines a friendly name for the scene.
Scene ID [1-1000]
Defines the unique ID of the scene.
Further Assistance
If you need more information or assistance, please contact us.
Developer Information
Company: Control Concepts, Inc.
Phone: (201) 797-7900
Email: projects@controlconcepts.net
Website: https://controlconcepts.net/
Developer: Jonathan Brenner