FYI, I've updated the iBlinds FW download link that I had posted above...support provided me w/an updated format (gbl) that is evidently "more compatible" than the hex version I used on to update one of my blinds. Using the GBL file todayI was able to update the first blind that I had received that hadn't been able to take the update previously. I had also reset my UZB stick in the PC Controller app today on a suggestion from iBlinds so that may also have contributed to my newfound success.
Also a note - my apologies, but I didn't know this at the time - the 3.02 release is a beta FW version, so if you install it and your dog starts howling and your chickens won't lay, don't go crying to me or to iBlinds. 3.02 has been running great for me on the blind I updated last week, but as always YMMV, and there are no warranties, implied or expressed.
So I'm having some problems w/my second blind I've set up.
It had a bad pairing the first time I tried to pair it, routing info disappeared from Z-Wave Details, entire Z-Wave mesh went to pieces, got it removed using the Remove button.
Since then I've included and excluded it several times, as each time I included it, it would seem to pair and be OK, but would only respond to one single open or close command, and then become non-responsive and take my mesh down to a crawl.
The interesting part is that even if I get what looks like a good exclude "Kitchen Blinds excluded..." message on the exclusion screen, and exclude it a couple more times "Unknown device excluded," the next time I pair it w/the hub it joins using @bertabcd1234's driver, rather than the built-in Hubitat driver. My other iBlind always joined using the Hubitat driver (HAB Home Intel Blinds V3) and then I would later switch it to Roberts (or the iBlinds 3.1 driver before Robert updated his driver). See below:
It seems like either the Hub can't let go of the info from the previous pairing, or the blinds can't. Since I've done the exclude repeatedly (and also used the command on the blinds motor to set all Z-Wave parameters to default values (7-10s press of CLBR button) I'd think that the blind was properly cleared. I've always ensure the Z-Wave table was clear of any entry for the blind before trying to pair it again, no ghost left-behinds.
Last night I finally got a pairing where things seemed to be OK, the blinds responded to a few open/close commands. But woke up this AM and it's non-responsive/not updating status on any driver. Luckily it's not taking my mesh down again but it's gone to "NOT_RESPONDING" in the Z-Wave table and fails when I try a repair.
Used PC Controller to remove it after it came up failed:
Anyone seen this before, where a device defaults to a community driver when re-joined after exclude, and doesn't pick up the HE built-in driver? I don't remember seeing this type of behavior before, and clearly the blinds aren't joining properly as they keep becoming non-responsive/failed. Also tagging @bcopeland for thoughts on when/how a device would pick up a community driver rather than the built-in driver.
But also, the driver in use won't affect the device's ability to pair, so something else must be going on. I always wonder about mesh issues with these since they're stuck in usually metal headrails. iBlinds does have a trick in their support docs where you can lift thr antenna out of the casing, but making sure you have a repeater (or the hub) nearby might be easier. Just a guess!
Thanks for confirming about the driver fingerprint.
Yeah, I've tried pairing it in the room where it's going to be used (through one wall and across an 18' wide room), and with the blinds a few feet from the hub. With and without security. Regardless, it just will not stay connected/happy. My other blind in the same room and probably 15' farther away from the hub is happy as a clam. Strange...
Found the bit about extending the antenna. May try that...not looking forward to uninstalling and re-installing the motor in the blinds.
What does joining w/out the S2 prompt appearing indicate - poor connectivity on the Z-Wave mesh, or ? And does that necessarily mean that the pairing isn't a good one?
Thanks...thought I finally had a good pairing, initially responded to multiple close/open commands fine. However, went for a walk and when I got back the blinds were non-reponsive, showed Failed in Z-Wave Details, and mesh was super slow/non-responsive. I had to remove the blinds using PC Controller. (Too lazy to pull the blinds off the wall and turn off the battery so that the Remove option in Z-Wave Details would work.)
So frustrating that this blind just can't get a good connection, while the other one has been just fine for days now.
The one that I setup first and have no troubles with is on power full time - I have the cable from USB wall wart plugged into the charger adapter.
The second one (that isn't connecting well) is on battery. However, several of my connection attempts were before I had it installed and it was sitting next to me on the couch. In those instances it was usually plugged into power.
I waited about an hour or so, data wasn't showing up, was thinking that might be a symptom of a bad pairing that was going to go south like the other ones. I then cycled through two other drivers (HE built-in and iBlinds 3.1 from iBlinds) and then back to the iBlinds V3 community driver. Each time after saving the driver I hit "Configure," (except for the iBlinds 3.1 driver from iBlinds which does not have a Configure option for some reason). I set/saved some preferences in the iBlinds 3.1 driver since there was no "configure" option.
After returning to the Robert's iBlinds V3 (Community Driver) I noticed that the missing values had appeared.
Now about 3 hours later the blinds appear to be properly connected and my mesh has not been slagged. The blinds shut as expected (along w/my other set) when an Event Engine automation ran to close them just after sundown.
I am cautiously declaring victory, finally, w/the second set of blinds...(no jinx, no jinx!). I'm relieved, and I'm sure you all are also relieved that you hopefully won't have to see another 18 posts about my connection issues.
Odd that I followed pretty much the exact same process last night and was not successful. The one difference last night was that I didn't cycle through the drivers like I did today. Hard to think that would make a difference in the Z-Wave connection, though. More likely dumb luck...
Most of this is just a matter of what the driver puts here (though some are Hubitat-provided, like "inClusters"--and if you don't see anything for that, it's usually a sign of a bad pairing attempt--and "S2," if present). My driver will populate firmwareVersion,protocolVersion, and hardwareVersionwith information it gets from the device, though in reviewing my code it appears I wasn't very aggressive about sending a "get" (request) for those, so it will now do so shorty after installation. To be consistent with Hubitat's driver, I've also ensured that I both get and parse all of manufacturer-specific (manufacturer and product ID, etc.), device-specific (serial number), and version (firmware, hardware, and protocol version), including a request when the device is installed or configure()d.
Hopefully this helps bring it into parity with expectations. I'll see what the v2 device supports and update that driver if I need to, as well. (But it wouldn't be related to your problems. Hopefully they continue to work well!)
[EDIT: Updated the v2 driver with similar changes, but left out serial number since these don't report that, only a "pseudo random" identifier of whose usefulness I am unsure--all assuming my reading of the Z-Wave specs are correct.]
More likely dumb luck...
, is this hotfix 
