Hunter Douglas shade plugin version 0.1.10

[sjenkins]

Thanks to @glarsen for pointing out that multi-room scenes broke discovery.  This update should fix that for both G2 & G3.  Also changed a timer on node throttling as I was getting the dreaded "red box" in the bottom right for the first time.

 

VERSION = '0.1.10'

"""
0.1.10
DEBUG multi-room scenes sending Discover into exception
FIX Throttling timer from 0.1s to 0.2s

past versions:
0.1.9
DONE Fix G3 Events stop working after some period of time

0.1.8
DEBUG branch

0.1.7
DONE rename nodes if changed in PowerView app

0.1.6
DONE parameters based on shade capabilities

0.1.5
DONE format for program setShadePosition
DONE set Shade Position change using False to define which parameters to change
DONE more debug on G2 so it acts as expected

0.1.4
DONE add node_queue & as result need pause updates while in discovery
DONE FIRST TRY G2 tilt feature

0.1.3
DONE node discover rewrite to allow add/remove
DONE add event 'homedoc-updated' currently no actions
DONE limit room label size to 15 as room - shade/scene < 30 for ISY
DONE clean up LOGGING.debug messages
DONE G2 bug fixes

0.1.2
DONE change icons to nicer ones
DONE docs with screenshots & description for udi spotlight
DONE add troubleshooting document
DONE add some support for G2 gateways (no gateway push, only polling)

0.1.1
DONE tap into gateway events, which allows longPoll update to move from 30s to 60s
DONE active scene indications from events
DONE shade motion indicator from events
DONE shade position update from start, stop, online events
DONE remove parameters based on shade capability (primary, secondary, tilt)
DONE update readme & config instructions to highlight G3 scope

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

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
"""
 

[apostolakisl]

Suggestion to change the name of the plugin from hunterdouglas to HunterDouglas.  The plugin store does not alphabetize the lower case letters where you would expect it to be.  I didn't realize the node existed until I saw this thread and used the ctrl-f "hunter"

[sjenkins]

@apostolakisl such a good idea that I have been trying to do it for the last 2 months

The latest PG3 update of last week allowed developers to change names and some other things.

But I am a bit confused because I changed it last week, so it should be updated in the store on your PG3, it is in my other users.

 

[GTench]

@sjenkins FYI... I had to delete the original "hunterdouglas" plugin and do a fresh install of the "HunterDouglas" plugin. Could not just do an Update to the "hunterdouglas" plugin. Everything working fine for G2 with the "HunterDouglas" plugin

[sjenkins]

@GTench Yes I am finding this out with another plugin as well.

Not sure if this happens with every name change or something special here.

Bit of a PITA for the users.  Thanks for the feedback, I will bring it up on the developers forum.

Glad all is working well.  You must not have any multi-room scenes, as one of my G3 users found where the discovery went into exception (not a crash but effectively tanked updates of scenes) when it tried to discover one.

Maybe if you have a min you could make one and fire-test it for me on G2 as the discovery functions are completely separate.  No rush, but I'd be interested that it works.

 

[GTench]

@sjenkins I don't have any scenes at all for the shades. I just address them individually with programs.

I created a test scene with 1 shade from each of 2 different rooms and set shade position to 30% then clicked "On" but shades did not move. They stayed at there original 10% position

 

 

HunterDouglas_4-25-2024_100131_AM.zip

[sjenkins]

Hi @GTench,

this is the first try at a multi room scene for G2. 
As is usual, I seem to remember the command to activate may be different. 
 

can you activate the scene from the PowerView app?

Edited April 25 by sjenkins

[GTench]

@sjenkins I did not set up this scene in the powerview app only in the AC. I had previously tested single room scenes that I set up in powerview and they worked fine by pressing the activate button in the AC.

Would you like me to set up a multi room scene in powerview and test that in the AC?

[sjenkins]

I am sorry @GTench, I didn't understand what you meant by scene.

No don't bother with the PowerView.  Whole basket of worms with multi-room scenes on G2.  Basically a new category of device.

I have never tried what you are doing with an ISY scene, have only tried programs.  Does not mean is can't be done though.

Can you change from default to command(I think) in the pull-down in your scene, you have the picture above?

Then you tell it activate or on after that.

Usually I have found that works better with z-wave devices.

Let me know if that works (should be the same for G2/3) ; I am not at home to try it here.

 

[GTench]

@sjenkins Yes that works (see below) Clicking the scene "On" button moves each shade to its 15% position. Thanks

[GTench]

@sjenkins For me personally, I don't see any need for using any type of automations with the powerview app now that your plugin works.

[sjenkins]

@GTench glad that worked & really good to hear the plugin is meeting your needs. I mostly wrote it for me & have had some fun/learning along the way. Feels like it’s getting pretty stable too. Have really appreciated your patience and willingness to do multiple cycles of testing of G2. 

[GTench]

@sjenkinsGlad to be able to help. Really appreciate you adding in the G2 functionality even though you did not need it for yourself

[sjenkins]

Just putting out there a feature which you may not be aware of.  The heartbeat feature is part of the UD Template so I won't take credit for it, but many don't seem to be aware of it.

Below is an example of the program you would want to have to take advantage of it or something similar.

 

Heartbeat MQTT - [ID 00CB][Parent 0028]

If
        'MQTT' is switched On
    And 'MQTT' is not switched Off
 
Then
        Wait  1 hour 
        Repeat Every  24 hours 
           Resource 'Heartbeat MQTT'
 
Else
        Wait  1 hour 
        Repeat Every  24 hours 
           Resource 'Heartbeat MQTT'