Wow - color me impressed, I could only get my wife to allow me to automate blinds on five windows. Can I visit?!
With S2 is the recommended approach these days, should provide better communication/reliability on commands and not adversely affect the mesh.
For the closing part, you could compare the "beat them until they are all dead" app (my name) aka the All Off app that Bravenel created to your own close/check/try again process. HIs app sends "Off" commands (which the blinds support) to the selected devices and follows up automatically politely but firmly bludgeoning them until they all report off.
My iBlinds are inside pretty thick older metal blinds housings and it seems to take a very strong signal to reliably control them. Even w/just five blinds I did not achieve iBlinds perfection until I upgraded to the C8 (and then C8-Pro) and (def a YMMV option) changed my C8 Z-Wave antenna to this super ugly antenna.
The blinds still only connect at 40, but they always work, no drop-outs/missed actions. One of our more respected members likes this antenna which is not nearly as ugly.
I also have one blind motor (the older 3.0 HW) that has started to drag when opening/closing, so wondering if it is on the way out...it responds to commands reliably, but is noticeably slower than the others, even w/the same settings in the driver.
Mine started to work perfectly once I created separate rules for downstairs vs upstairs.
I opted to use the “repeat while” condition which checks if any blind is open or closed and continues the action until they all comply. Within the loop it refreshes status and commands it to open or close.
The interesting part is that one blind, and always the same one, initiates the action first and then the rest follow shortly after.
So regardless of all my attempts to create a synchronized event they will open and close independently at different times. Some days with a bit less lag than the next.
I am using the c7, so it may not be an issue if I decide to update to the c8.
My only real complaint other than the latency is the fact that the button doesn’t initiate a tilt motion (i.e. tilt while pressed until you let go) so it kind or sucks that for manual control you can either close them completely or open them at their last tilt setting.
It feels like a programming miss if you ask me.
Anyways, I have 10 blinds total with an 11th one which I am trying to fit into a tiny window.
I don’t regret them at all since they were still a fraction of the cost than what I was quoted for other options.
I only get 40 even with good antennae.
I have messed with them for years and one thing they don't like is a group command.
I have always had to loop with a delay to each device. I find 5 secs works without issue.
So after a few weeks/months of good operation, these past few days the blinds in my master bedroom have started to fail during the opening call. Mainly one is failing and I am not sure if it is due to a battery gone bad.
When I look at the logs, this is what I find:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: iBlindsV3.getBattery() is applicable for argument types: () values: (method getBattery)
Does anyone know what this means? I am using the built in driver for all blinds.
Sounds like you were using my driver at some point (or some other that may have happened to use this exact name by some coincidence). You can remove the scheduled job in Logs -> Scheduled Jobs, though it's technically harmless.
If you're having problems with the device itself, changing between these two drivers is also unlikely to help or change anything, by the way.
Yeap I had originally set all the blinds with your driver and then reverted back to the built in.
In this case switching between drivers actually DID help because I was able to send a recalibration command which woke up the device.
I had only encountered that same issue one other time at the moment that I installed the last motor I needed where it didn’t move more than a few positions until I used your driver to recalibrate.
I’m not sure why it happened this time around though but it looks like problem solved.
Not that I'm having issues with the community driver but what is the built-in driver called?
I see no specific iBlinds just Generic Z-Wave Shade - is that it?
Never mind.
It's under HAB Home Intel iBlinds
Love that you can filter the drivers with search text.
Yeah, that's what I use and it's great.
I do like to migrate to a supported device after they come online though.
Members who create drivers/apps are the backbone this thriving platform.
When HE catches up then I reason that the built-in is now supported so I can create a proper support ticket/thread rather than bothering a member who is doing this with his free time.
Can I visit?! 
