I will have to take pics later just to confirm. I've had it plugged overnight but led is still red but there's another small green led next to it.
Yeah, that's normal. Green is for the battery, red right next to it is just the "I'm alive" color for the motor. 
You're good.
1 Like
All three motors installed.
Response is very intermittent and iffy. 
Which icon are you using in Hubitat and SharpTools?
I actually haven't set it up on a dashboard yet, too busy w/other stuff and spent too much time on it at first when the bad FW file they had sent me wasn't working.
I do have it setup on Google Home, and a Pico my wife uses, and she loves being able to tell GH to open or close the blinds or tap the button on the Pico. I use the Community Google Home integration.
I'll try to set up on a dashboard later today. My control has been perfect, no lag, and reliable/consistent so far.
Which iBlinds driver are you using again?
What iBlinds driver are you using that saying open the blinds works? I'm also using the community integration, and saying open the blinds goes from 0 > 100 (so closed down to closed up).
Edit: I clearly missed 2.2.4 was released with a native driver. Switching to that and updating the GH Community addon resolved the problem.
I'd recommend any of them.
A built-in iBlinds driver is included in today's 2.2.4 Hubitat FW release. It's callled "HAB Home Intel iBlinds V3." Try that one first.
There's also one on the iBlinds site, that requires manual install on Hubitat, as does the community driver.
iBlinds GitHub:
Community Driver thread w/Github link below. I don't know if @bertabcd1234 is going to, or even needs to, update his driver.
Still not working.
1 Like
You mean blinds aren't opening/closing at all, or not reliably?
They opened automatically at 7:00 a.m. as I set up in the rule machine. Then, they didn't work at all. I think that it is a Z-Wave network issue. I'm going to work on that for a while.
I've woken up to a massively slow Z-Wave mesh. No idea where it came from, nothing has changed on my mesh, no added devices since the blinds and they have been on the mesh (on and off and on again, actually ) for days now. I ran 2.2.4 since the start of the beta w/out any significant issues, so this is surprising.
I had best luck pairing the blinds closer to the hub to get a good join, and then moving to their actual location. I did have inconsistent results...in some cases pairing from their installed location was difficult, the next day it was easier. Vagaries of the world of meshes. 
I was not in the 2.2.4 beta so I just upgraded yesterday. It seems that the included v3 iBlind driver is better. I checked the join Hub mesh box. I'm not sure why my Z-Wave mesh is wonky. I moved a Samsung Z-Wave outlet dimmer-repeater close to the blinds but now the repeater is in a Z-Wave fringe.
I'm going to install some Zooz ZEN22 Ver 4.0 Z-Wave dimmers between the blinds and the Hub today so I'm hoping that extends the mesh more robustly and fixes the problem.
The Hubitat Mesh option is only for when you have two or more Hubitat Hubs and want to share devices between hubs. If that's not your situation, then you should turn that setting off.
Sounds like a good plan. You'll want to give your mesh some time to settle down after you add the new devices. Assuming they are all Z-Wave plus they will find their own best routes. You could do Z-wave repairs on them if they look like they join w/slow connections, but in general w/Z-Wave plus the devices work out their routing on their own. Also, you may find that even w/one of the new Zooz devices nearby, the blinds (and other devices) may choose routing that seems odd to you. Happens to all of us. In the future Hubitat wants to provide more control over routing, but we're not there yet...
1 Like
Kind of a splurge purchase but it seemed timely and on sale for $100 off. I expect that it will save hours of time and frustration as I set up the new house.
1 Like
That looks like fun! This home automation stuff is an endless time-eating wormhole.
1 Like
iBlinds support has updated their links on their driver support page to the iBlinds 3.1 driver. That is the driver they are recommending we use w/their blinds. I've been using it for a few days and haven't had any issues w/responsiveness of the blinds. It has some useful settings, including how tightly the blinds close (Close Interval), which is nice.
iBlinds driver support page:
Github - iBlinds 3.1 driver
- Choose the 3.1 driver on the github
Looks like below:
Aside: The iBlinds support folks are really nice, very helpful. I've been impressed w/their responsiveness and desire to help.
3 Likes
On that page, they say 2.2.4 will have a built in driver and seem to suggest not using theirs:
Note: As of this writing (October 2020) the iblinds v3 device driver should be in the next Hubitat update release and should not require manual installation.
Their v3 driver looks to have the same behavior as the v2/v1(?) driver, where events are optimistically generated regardless of whether the device actually responds. I haven't used the v3 driver from Hubitat yet--or installed my unit at all--but I'm hoping the device sends reports on it own after changes (v2 doesn't, so I don't blame them for taking this approach, though it's not the only way) and that Hubitat's driver follows suit, as this is one of my least favorite aspects of their drivers it makes device monitoring/"watchdog"-type apps not really work with them. But some of the options look nice. 
Hope to get mine installed soon to play around with it!
That content is old and incorrect... When I spoke with their support team, they were quite confused that their driver was not in Hubitat.
I just assumed they wrote it in the possibly-not-distant past since 2.2.4 was just released, but beyond that, I'm not sure what they were expecting. As far as I know, all of Hubitat's drivers were written by staff from the ground up, this being no exception (one of Bryan's creations), so iBlinds shoddy port of SmartThings DTH is not what was included--but a(nother) driver certainly is. 
Looking forward to your comments after you set up your v3, and how the new hardware\FW plays differently (or not) with drivers, reports status or not, etc. Especially wondered if you'd find anything that would lead you to update your iBlinds driver.
Whether it's a coincidence or not is impossible to be sure, but my blinds seem like they have behaved best since I started using the 3.1 driver a couple days ago. That could also be subjective bias of course as well. 
At least they have good support - they are shipping my replacement blind tomorrow, so I'll soon have two installed in the kitchen\family room to amaze my family with. 
I just installed the 3.1 driver from the link above. It is different from the driver included in yesterdays Hubitat 2.2.4 system download. I can't play with it just now but I am optimistic. I just need to get my Z-Wave network to settle down.
