Hunter Douglas shade plugin version 0.1.0

[sjenkins]

I think this plug-in is pretty stable at this point.  I am using it in my home now.

Removed the need for the user to know which gateway is primary & added automatic switching between the gateways if primary changes, which I am told can happen.   Updated configuration instructions & added link to this forum.

Feedback is welcome.

 

VERSION = '0.1.0'
"""
0.1.0
DONE handle multiple gateways automatically, picking primary & switching if required
DONE updated configuration instructions as well as link to the forums

add to future version:
TODO tap into gateway events
TODO remove parameters based on shade capability (primary, secondary, tilt)

past versions:
0.0.9
DONE fix uom for positions(100) & ids(107)
DONE more notices clean-up
DONE shade naming to include room as scenes
DONE remove status based on shade capability (primary, secondary, tilt)

0.0.8:
DONE handling of notices individually
DONE polling 5s short-poll 30s long-poll
DONE status for programs (positions etc)

0.0.7:
DONE faster status updates when command is given
DONE bug fix
DONE re-order of parameters displayed

0.0.6:
DONE move shade by specific amounts
DONE bug fix scenes not activating

0.0.5:
DONE change shortpoll to 30s
DONE update shades on shortpoll
DONE clear start notice at shortpoll
DONE clean up error proofing in get
DONE fix updating variables with shortpoll
DONE limit device ping to 5s

0.0.4:
DONE discover when new gatewayip is entered
DONE poll status regularly using shortpoll
DONE update required after nodes added to get status
DONE notice when gateway get error
"""
 

[Michel Kohanim]

@sjenkins,

When ready, please let me know and we'll include it in our email blash (Plugin Spotlight). 

With kind regards,
Michel

[sjenkins]

@Michel Kohanim,

very cool.  Let me attempt the next two Todo's.  Is there timing for the next 'blash'?

TODO tap into gateway events - this, I believe, works like a push for updates when the move starts and is completed for scenes and shade moves.

 
TODO remove parameters based on shade capability (primary, secondary, tilt) - this I don't know how to do without creating a separate node for each shade type.  Effectively I want to have inputs for only the parameters the shade has capability for.  It means the profile nodedef is different.  Can the controller if/then which nodedef is picked using the same python code?  I have not asked the crew on discord this question yet as up until now I didn't know how to word the question

[Michel Kohanim]

@sjenkins,

In couple of weeks.

With kind regards,
Michel