I've been Using HE for a couple years. Several Zigbee and Zwave devices well spread out through the house creating a pretty strong mesh for both. I recently installed all new blinds throughout the house, with Zwave iBlinds firmware v 3.13. I have an HE C8 v 2.4.1.163. I had some issues early on, but switching from the base driver to the community driver has ironed out all issues except for one window. One window consistently will not respond to a close command. A work around I have implemented was to issue a close, an open and an additional close for every rule and button control closing that blind. Interestingly enough, it just reliably closes once every time that sequence is run. Anyone had this kind of experience?
I have had 5 of these for many years, 2 V1, good riddance, and 5 current V3.1.
These was a lot of craziness testing the beta on the HE and User driver; very long thread.
Everything seems to be well sorted now that the beta is in production, no complaints so far.
The only suggetion I have is to repower the offending blind.
I found that the v3 blinds will function well for about a year and then things like Close won't work but Open will or the commands get executed 10 or 20 minutes later all in succession. I think the onboard system has a memory leak.
Are you on the ZW ZIP Gateway still or JS?
Applied the new ZW firmware on the Stttings page?
I think @bertabcd1234 is the iBlind Yoda
Since you're on a C-8, I'm assuming you are still on "legacy" Z-Wave (you are unless you happened to be in on the beta where the upgrade was once allowed or have some other unusual circumstance).
I haven't seen anything like this, but I see odd things with these devices all the time. In your case, maybe see if a calibration helps? Check the manual for sure since it varies based on hardware and firmware, but for yours, it sounds like either the hardware button sequence of the custom command in my driver to start calibration will work, either followed by a "Set Position" to 50%: https://support.myiblinds.com/knowledge-base/calibration-v3/
The other tips on that page might help, too, like changing the close interval. I've never tried this on any of mine. Things normally sort themselves out before I get around to anything...
In some cases, I've seen something that I can only assume is some sort of Z-Wave freeze on the device, where the solution is either waiting a few minutes, power cycling, or probably doing the Z-Wave reboot they added to newer hardware (the fact that this exists at all makes me suspect this as a culprit...maybe more on the V2 units?). But since yours only seem to have problems with one particular direction, that seems unlikely to me.
I should also note that I am not an iBlinds wizard; I just have a lot of these devices and wrote a couple custom drivers before there was a built-in option. 
Thanks for the input. I'm on the iBlinds V3 (Community Driver). The only attribution name I see is Robert Morris. I believe I pulled it from HPM. This driver has several additional commands compared to the core installed one, including calibration. I was soooooo glad to see that after I switched. I'll probably try the hard power cycle. I was just baffled by the consistency of the behavior. Definitely doesn't seem like a connectivity or mesh issue, based on the consistency of the single command issue..... I definitely appreciate the effort and dedication it takes to help support communities like this. Thank you!
Sorry, missed dnickel's question on Zwave config. Not sure what a Zip gateway or JS is. berta is right on track with his assumption that my C8 is pretty much as delivered, except for conscientious updates. As a long time IT pro, take the regression tested updates religiously. Take Beta only if the project depends on it.......
I have seen similar issue with two of my v3 blinds. The same two year after year. They seem to have the issue about a week apart. A forced calibration seems to get them back on track. Maybe I need to write a rule to force that every 6 months to see if keeps the problem at bay.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
