Heard back from iBlinds support...FW versions are as follows:
3.01 and 3.1 are the same firmware. iBlinds decided they wanted to change their FW versioning after they released had released some v3 blinds. So FW 3.1 can be updated to FW 3.02. So @Hal3 - you can (if you want to) update your blinds from 3.1 to 3.02. It'll look weird, but 3.02 is the newest release.
Email from iBlinds support: "The newest firmware we have is 3.0.2, The other firmware (3.1) is the exact same as 3.0.1 and we have opted to go with a different naming convention"
FW 14.x are internal/beta/engineering FW versions, not for normal release. Nothing to see here, keep on moving.
An update on drivers...there are currently three available, and one that may have been used in the beta conducted by iBlinds that is not currently available.
HE built-in driver: "HAB Home Intel iBlinds V3" in the driver list. Written by bcopeland (Bryan) and included in 2.2.4.
@bertabcd1234's community driver Developed for v2 blinds, he just installed his v3 today so the driver is not adjusted, if that's required, for v3 yet: "iBlinds (Community Driver)" in the driver list after installed from his GitHub. Probably the most full-featured driver overall.
Release thread: [RELEASE] Unofficial iBlinds driver
There is evidently a fourth version of an iBlinds driver, you can see pics of its Preferences settings on the iBlinds driver support page - it looks different from the iBlinds driver that is available on the iBlinds GitHub above. Pic of this fourth "mystery driver."
Heard from iBlinds support today - they had accidentally sent me a bad version of the FW update file.
They sent me an updated FW file to try and it updated my second blind fine via PC Controller/UZB stick. I'll try my first blind (the more problemmatic one) maybe later today, hopefully it will now update as well.
They aslo confirmed they've had another report of the single-press on the manual control button not working consistently in addition to my report. The unit from the other customer is on its way to iBlinds from the customer who reported it, and they think it could just be aminor FW tweak to adjust how the button responds.
I’ve been following the community for a little while, but this is my first post. I recently received the V3 iBlinds, and my battery has consistently been reporting as 1 despite being fully charged. I am using the driver from iBlinds and am on firmware 3.1. Has anyone else had an difficulty with the battery reporting correctly?
I just received a response from iBlinds about my battery issue they hadn’t heard of others having this issue, but they sent me the file for their V3.1 driver. This is the 4th driver shown in your post. I let them know that it wasn’t available on GitHub or their website.
Thanks for letting them know that, I also mentioned it to them, hopefully they'll rectify that.
I see your battery is also reporting "1" like @Hal3's. I was able to fix that by setting the battery update time to just one minute past current time, and when the clocked ticked over my battery updated to the correct charge level.
Mine took several hours, but I charged it the first time before I did the install, so I have no idea how full it was when it started charging. They claim ~5-6 months between charges, obviously dependent upon usage. As usualy ambient temps affect battery life, but since this is indoors that should not have a huge effect.
Usually you'd run the blinds twice a day - open in the morning and close in the evening, maybe some adjustments during the day if you want to change the open % due to the angle of the sun.
The motor is surprisingly quiet, and the amount it has to run is very small to open and close the blinds.
I'm starting to really like this...came out into the family room this AM and the automation I had set to open the blinds 30 minutes after sunrise had run, and the blinds were open, room was bright and inviting. Nice!
Green is supposed to confirm that the battery is fully charged, yellow when it's charging. One of my units arrived w/the battery fully charged, IRRC it was green when I connected it.
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.
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.
