Also doubling down on the props to @4n0nD3v3l0p3r for the orig and @mtgeekman for the fork. I was able to work with @mtgeekman to modify his integration to gain scrappy control over the bottom rail for a set of top down bottom up blinds I purchased from BlindsGalore.
Re: @nerdyoda, with my particular blinds, I found that the position would never provide HA with a state -though it functioned correctly, the state was always unknown.
Though quite silly, I ended up adding an additional integration on top of this my modified integration from mtgeekman. I used the fork from Robi on this page: Custom Component: Cover Time Based and used the time to open and close, then integrated service calls into the front end and used Lovelace: Multiple entity row to put it all together again for Lovelace.
After doing all of this, HA now shows open and closed states, as well as pretty accurate position states (solely calculated by time).
This allows me to have a single button to control the top rail, and the bottom rail for the 4 most common positions I use (represented with battery icons): all the way open (both rails up), all the way closed (top rail up, bottom rail down), sitting privacy, and standing privacy (bottom rails down and top rail at 52%, and 30%. Lastly, I used a helper toggle to track if the bottom rail is down all the way or not, which lets me change the delay before moving the other rail before the stop command stops both rails.
All in all a very round about convoluted way to get full functionality. I suspect doing something similar will give HomeKit the extra position info it seems to be asking for in the error -but not positive, since I haven’t done it myself.
