sjenkins

@zGuy981 , thanks for finding this & the explanation.  I did find the issue.  Give the Beta a try & let me know, if all is well I will push to production if all is good , when I get back home next week.
 

@zGuy981 Ready for you to give it a try ; its in the beta area same version, just reinstall 1.12.4
 Appreciate your patience.  I missed a second occurrence in the shade update routine.
let me know.....
 

@hart2hart, sorry to say its a 3 month old fat-finger of mine when I first refactored the code.  The profile info was done right but in the switch.py code I made the uom 2 instead of 25.  Means only new nodes are affected.  The old ones are fine.  You win the prize for finding it now.  I checked the other nodes and they are consistent.
It's now been fixed in the production and the beta code.
Unfortunately, it's kind of sticky once you make a node with this mistake.
The node needs to be deleted either individually or the whole plugin.  I suggest the former.
0. close the IoX launcher / Administrative Console
1. goto the store (either production 3.1.6 or beta 3.1.9, depending on your preference) and install the virtual plugin on top of the current one (do NOT delete it first).  I did not do a new version for either, just a hot fix.
2. goto the virtual plugin & configuration & make sure the "Allow ISY access by plugin" is ticked and saved
3. goto the node button & delete ONLY the nodes which are showing True/False  [three in your case @hart2hart].  
**The only issue will be if these nodes are part of scenes, they will have to be reinserted in those scenes at the end.  Programs will be fine when the node is regenerated.
4. restart the plugin, the nodes will be regenerated.  Start the admin console.  Happiness (reinsert in scenes if necessary).
 
Apologise for this one and the steps required.  I know of no other way when the drivers are defined in the code wrong but the profile nodedefs are right.
Let me know how it goes.  I have tested it on both the production and beta versions, locally and installed from the UDI servers.  

Hi Rod,
first, you are doing nothing wrong. 
So as I developed this plugin I started with a scope of just gen3 (what I have), then along came a user who has gen2. So right now it’s written as “either or”. 
So two solutions.  I can do a bit of a rewrite; might take me a bit. The other solution is to install the plugin twice in different slots. Setup one as gen2 & the other as gen3. 
try that first and let me know here if there are any negatives to that. 
we can take it from there. 
 

This is solved as of version 0.40 of the MQTT plugin
 

for those watching here, potential solves for this are in the beta (non-production) store.
mqtt-poly NOT mqtt
If @SamM verifies he is satisfied, we will call this solved, or take another run at it.
 

@GTench I put out a new version to consolidate all our changes plus I think I have cracked a better way to define set shade position.  You can have more than one uom in an editor file so a False means don't bother which a number means you want a change.  Check it out.  Make sure to either hit the update profile button or restart your admin console after the update.
As stated in the notes I think I know how to better refine the shade node based on capabilities without having 20 different node types.  Basic structure programming but I got put off by how the ISY talks to the nodes.  The experts helped me here.
Lets start a new thread if you don't mind -  this one is beyond it usefulness & I don't like the title   
I'm going to close it solved but please start a new one with feedback either in the announcement of 0.1.5 or a new one.
Thanks again!

Hi Josh (and perhaps others
Good news your pic was perfect & will help me with future users.
I had made an assumption that normal set-up was completed in your hunter douglas app.
 
for others, I had Josh goto a browser and enter:   http://ipaddress/home for each gateway
I will likely add this to the instructions as a 'test if you're ready' step

- As shown above, this is truly a V3 gateway hub but it is not your primary.

- this is also a V3 gateway hub, and is very likely your primary
- Ithe HomeDoc is not something that the user needs to 'have' or edit but is on the gateway if it has been connected with a Hunter Douglas account, and a Home created.
... from the HD Docs:
" Note: If the Home does not have a HomeDoc, all /home APIs return statusCode 503/SERVICE_UNAVAILABLE until the Home is correctly configured and a HomeDoc is successfully retrieved from the Cloud"
- HomeDoc is created when you run the PowerView App & create an account and then a "Home", this should have been done for you by your installer.  Mine was not very tech savvy so I did it for him.
- you need to download the HD PowerView app on your phone
- If you have never run the app before there is a Setup Wizard which will run out of the box and allow you to create an account and then a home
- If you have run the app before and do not have a home created you can go into the More area in the bottom right, which will come up with a screen you can pick Set-up Wizard from.
 
- I would do a restart on the plugin after you complete the HD app process
- If you want to check yourself after you complete the app HomeDoc process then enter the
http://{ip of the gateway}/home
again into your browser, you should receive a JSON text with a whole bunch of data
- This is part of the 'normal' set-up when you get the blinds but I can see where some installers didn't complete it.  You can still see the blinds on their app if you don't create this link, you just cannot do much with the api
- Also I am going to add some diagnostics to the plugin and the above help to my documentation
 

@Dave Green this is not an AcuRite issue.  This a udi_interface issue.  you may need to wait until Monday for @bmercier to do an update.  Patience for the moment, here is a link to his message.
 
 

@Javi so I deleted the node server &. installed it in another slot.
All 34 nodes came back.  Solved.
Thanks again!
 

So sorry I didn’t get back to the post. Yes I did put in and get an answer to my ticket. Basically that the occupancy was part of the pg-online and therefore not working. I sort of knew this but was unsure if policy brought it back as it was in the menu system still online.