HunterDouglas PowerView Interface

Universal Devices PG3

This plugin/nodeserver provides an interface between HunterDouglas Shades and Polyglot V3 server supporting Universal Devices EISY or Polisy controllers

Get your amazing EISY at Universal-Devices

Screenshots

Installation

You can install This node server from the PG3 NodeServer Store.
Read the Configuration file for instructions
The Forum is a great place to ask questions
And troubleshooting steps are also available, and updated from forum discussions

Requirements

IMPORTANT: There are differences for HunterDouglas G3 API versus G2 API

See the Configuration file for details

This node server will only run on Polyglot version 3. You will need to have an EISY/Polisy with PG3 installed to run this node server

See also Hunter Douglas PowerView for product details

For PowerView G3 hubs, the API can be self hosted by your hub:

• Enable Swagger on your hub: swagger_enable
• Get the Swagger results: swagger_results
• Disable Swagger on your hub: swagger_disable

For PowerView G2 hubs, the API can be found here

Polling

longPoll

• currently every 60s

controller longPoll

• update all data from Gateway, set event array flagging each shade, scene to update
• shades and scenes processed sequentially

shade longPoll

• G3: logged
• G2: logged

scene longPoll

• G3: logged
• G2: clear ST, Activated flag

shortPoll

• currently every 5s

controller shortPoll

• process general events, sse heartbeat check
• if no events (60min curently) reset sse client

shade shortPoll

• process shade events

scene shortPoll

• process scene events

Events: controller

homeDoc-updated

• G3 generated
• signals update of the G3 login to HunterDouglas
• ACTION: just logged

home

• plugin generated
• sequentially update all shades, scenes once per longPoll
• ACTION: each node checks once per shortPoll;updates then removes itself from array

Events: scene

scene-activated

• G3 generated
• sent on completion of movement to scene positions from any source
• ACTION:
  • G3 turn on ST, Activated
  • G2 turned on when plugin activates scene (does not get info from remote or app)

scene-deactivated

• G3 generated
• signal movement away from scene positions immediate from any source
• ACTION:
  • G3 turn off ST, Activated
  • G2 is turned off on next longPoll when plugin activates scene
  • G2 (does not get info from remote or app

Events: shade

shade-online

• G3 generated
• kind of a heartbeat which keeps the sse client-server connection alive
• ACTION: checked in shade device, logged as info
• not sure how often this is pushed from the G3 side

shade-offline

• G3 generated
• assume this is generated by G3 if it cannot communicate with shade
• ACTION: checked in shade device, logged as error

motion-started

• G3 generated
• any shade motion from any source by any command
• ACTION: currenly just set the ST, Motion flag
• MAYBE:
  • Motion timeout: reset or fire 'jog' command after timeout if plugin stopped in mid motion, or motion-stopped event missed

motion-stopped

• G3 generated
• shade motion from any source by any command
• ACTION: currenly just clear the ST, Motion flag
• MAYBE: Motion timeout: as above, happened once to me, but rare