Hunter Douglas shade plugin BETA version 1.13.0

[sjenkins]

Basically rewrote the whole thing as the Python was pretty ugly & while I'm no expert I have come a ways in my journey.

Also, stole shamelessly off a few other more gifted plugin makers.  Thanks to all who make their work public.  @Jimbo.Automates I'm looking at you.

The end result is much more pythonic and readable ; hopefully easier to maintain.  It is MUCH more responsive and less likely to crash ; with the old version did on a regular basis for me.

Saying all that the feature list is very short & really only for the G3 folks.  

1. Small thing, added a node count to the controller node, does not include the controller.  Saw others with it and can be useful as a sanity check.
2. Motion for shades & Active for scenes should be good for use in scenes as controllers and in programs.  In addition the shade actions should work in programs for control in addition to status.
3. The event engine works much more quickly and reliably now, to the point I now pre-populate POLLING with 60s short and 600s long cycle.  The 60s is for G2 updates and does nothing for G3 except restart the event engine if it ever crashes (doesn't seem to anymore).  While the 600s is only for G3 polling and does nothing for G2.  G3 almost doesn't need the polling anymore.  YMMV.
4. G3 scene activation I found was not always being updated by the PowerView gateway.  The app would read correctly but when you went for the active list, it was out of date.  Now I use the active scene event, but I set the active scene by calculating where the shades are.  I also trigger calculations when the shades start or stop movement.  Seems to work MUCH better.  Sorry G2, there is no way to get the underlying shade data for a scene.  I tried.
5. Cleaned up the logs ALOT.  INFO level is more sane now.  Please send me DEBUG level if you have issues.

I have tested a fair bit but I have 15 shades and about the same number of scenes, ONLY G3.  I am most fearful that I broke something for G2.  So I am really really sorry G2 but I gave you little and may have broke something.  I will leave it in BETA as long as it takes, but I will need some of you to test it.

One last note.  With the move to EISY-UI, there is some behaviour that I am seeing across plugins.  Once you update this plugin, you may need to run an ISY update / reboot.  You should NOT need to delete and re-install (that will cause you to have to resave all your programs, yuck!!).  If you don't update/reboot and you log-in locally, all is well.  But the portal login may give you a lot of blank bits.  They will update as scenes are activated or shades change but a update / reboot makes everything better.  Or at least that is what I found.

You can load the beta in a slot you have production, and move back to production.  Most likely (!!) without breaking anything.  I have done this a few times.  I actually have my programs which schedules triggering of scenes to three different plugin slots (where I keep my production, beta, and local versions).  I only run one at a time but it allows me to test back and forth quickly.

Please give feedback!!