Please use this thread to ask any questions or comment on my plugin. This is my first plugin, but I think I got it bug free.

The Levolor plugin connects directly the Levolor InMotion Hub. You will need to install the InMotion app on your phone and set up your blinds using that if not already done. From the app, if you tap the "about" page 5 times it will report the api key for your hub. You will need this key, plus the IP address of the hub. You should set your router to reserve that IP so it is always the same.

From there, install the plugin and set the two parameters (ip address and api key). The plugin should immediately connect to the hub and query it for any blinds you have setup in it. This should take just a few seconds. If you still don't see any number next to the "nodes" field on the plugin, refresh the web page. You will get x+1 nodes where x is the number of blinds you have.

Restart your admin console. You should see a new node on your main tree called "Levolor Controller". Sub nodes will exist for each blind you have. Controls include to directly set it to a percent closed (0% is open, 100% is closed) or you can execute an open, close, or stop command. This is the same as the InMotion app.

I only have Levolor blinds and only created the plugin for blinds. Basically, open, close, stop, and percent. Other features like tilt exist that I can't test. Perhaps if someone has those types of blinds and wants to work with me, I can update the plugin.

The plugin is limited by the communication between the hub and the blinds themselves. In my experience, sometimes the hub isn't accurate. Both the InMotion app and ISY will give you information that is not correct at times. In addition, the app and plugin will both be a bit delayed according to polling between the hub and the blinds and between app/plugin polling of the hub. I have found that ISY and the app both update status nearly simultaneous, so mostly it is a blinds/hub delay. This is a property of the InMotion setup and nothing in the plugin can change that. Regardless of the plugin/app status reporting, executing commands has had 100% success in all my testing. I have the response time to be less than a second consistently.

Did some bells and whistles on the plugin. After you initiate a blind position change, the plugin will poll every 10 seconds until the target is met or it times out at 3 minutes. So it won't real time track the status of your moving blind, but you won't have to wait up to a whole minute for the regular polling. Be aware, if you change the blind position using something other than IoX, it will still poll every 60 seconds (like the Levolor phone app or Alexa via the Levolor Alexa skill). Side note re Alexa, you can expose the IoX Levolor node to Alexa and let Alexa control the blinds using IoX as the path or you can use the Levolor skill. Google Home should be the same. If you choose the IoX node, then it will poll every 10 seconds until target met.

I also added different ways to view the blind status. You can set UD mobile to display the one that suits your desire. I find that using the UD mobile slider widget is the most practical control interface, unless you never use a mid position. The com between the blinds and the hub can be flaky. Commands consistently go through, but the blinds don't always manage to update the hub with their current status. Nothing I can do about that. The Levolor phone app will also fail to show the correct position. I have just one hub in my house and positioned it so none of the blinds are more than 40 feet away, yet the ones that are more than 20 tend to have missed info or delayed responses to commands. Currently, if you have two hubs, you would need to install the node server twice (use two slots). I would like to change that, but since I only have one hub I'm not going to try to guess if it works. If you have two or more hubs and would like to work with me, I'd be happy to give it a go.

Field	Meaning	Display
Status (ST)	Binary state,	0–50% = Open, 51–100% = Closed
Position (GV4)	Actual blind position (0 and 100 sub word open/closed)	0–100%, exact reported position
Blind State (GV5)	Human-readable description of position	0% = Open, 1–99% = Partially Open, 100% = Closed