Just noticed in another thread that there was native iBlinds support. Didin't see it as it's labelled HAB Home Intel iBlinds not hust iBlinds 
I am using a community V2 driver as that's the hardware version I have.
Should I switch to the supported one even though it's labelled V3? Can one assume backward compatibility?
Cheers.
No, the v3 and v2 units work a bit differently. Mostly notably, v3 has configuration parameters that v2 does not (probably harmless if you ignore them), and v2 cannot be configured to self-report status back to the hub like v3 can (it must be fetched, which I'm assuming Hubitat's v3 driver does not do given that this is unusual...or you could take the even more awkward approach iBlinds took in the drivers they've published on their site, where the state gets updated on the hub regardless of what actually happens in the device--even if they don't respond).
Ugh - how horrible.
1 Like
Ok, I'll stick with the community V2 driver for now. I actually have more options with that one, V3 only gives me Open, Close and Set Position.
V2 has Refresh so if I have to poll for some reason at least that is there for my piston.
If you're using my v2 driver, what it does is poll (so basically refresh(), except it only asks for the new level/position) a set amount of time after an on(), off(), open(), close(), setPosition(), or setLevel() command is called. This is determined by the "Allowance for travel time" preference in the driver and, again, is necessary since the v2 units don't send anything back without being asked. This is further complicated by the fact that if you do try to fetch a level while they're still traveling, they will instead open or close all the way instead of going to your desired level, so longer here is really better--and especially important to consider if/when you calibrate, since it appears to apply then, too (recall that calibration is, confusingly, not kicked off by hitting the "CALIB" button but by hitting it and then sending a Z-Wave command to open/close or adjust position).
The v3 units take care of most of these oddities, though they still don't report back unless configured to do so (my driver does this automatically, and I'm not sure why anyone wouldn't want this, but they seem extra scared about implementing this, possibly due to the problems they created with how v2 units worked). In either the v2 or v3 driver, however, you can do a refresh() to get both the current position and battery level if something goes wrong (or you choose to disable automatic reporting in v3 or fetching in v2). Oh, and did I mention that v2 also doesn't send battery reports on demand? 
(So there's a scheduled job to do that daily there, too.)
Other than that: for v3, the only big differences between Hubitat's driver and mine that I can see is that they did theirs as a "pure" WindowShade device, so you only have those commands available: open(), close(), and setPosition(). Mine also implements the "Siwtch Level" capability, typical of dimmers, which allows you to use commands like setLevel() and opens up compatibility with a wider variety of apps. What you can do should be about equal with either driver, though more apps are likely to work better with the latter due to the additional commands (but if it confuses voice assistants or whatnot, that capability can be commented out).
2 Likes
Well crap, didn't realize I was getting an answer from the proverbial horses mouth! 
Didn't look at the code header, shame on me.
Thanks so much for the detail on the driver. I did buy 2 * v2 as a test because they were on sale last year not knowing that v3 was on the horizon. I had a friend in LA send them on as they don't ship to third world countries like Canada.
Hope to use them soon. My blind order go stalled when Covid hit. It's the finishing touch to the rec room but since no one can come and play I have just let all this sit. 
Weel I finally got the blinds installed and running; Covid argggg.
Having a B'atch of a time getting the calibrate on one but the other went fine.
Getting this while messing around with the Calib.
I'll see if it continues during daily use.
dev:5072022-09-15 16:21:20.521errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_RMoRobert_iBlinds_v2__Community_Driver__559.startPositionChange() is applicable for argument types: (java.lang.String) values: [open] (method startPositionChange)
As far as I know, the v2 units do not support this feature. The v3 units do, and that driver has been updated. I suppose I could "stub it" in this one to stop the error, at least...but the command still won't work. 
Calibration should not cause this command to run on its own--nothing should. It must have been run manually (or via an app?).
Could be manually triggered from the device page. I was pressing many buttons to try and get the calibration to trigger. iBlinds and your notes were fine for guidance but still very finicky. One took to the calibration right away, the other is still too hard off and on.
