I’m still getting “The firmware target is invalid”. I’ve rebooted my machine, do you think I have to repair them?
FYI, the link itself is still pointing to 3.15.
Sorta guessing the correct link is:
https://support.myiblinds.com/wp-content/uploads/2025/11/iBlinds_v3.09_US_11.gbl
@FutureGUIs Sorry for the confusion. Thanks again Tommy - https://support.myiblinds.com/wp-content/uploads/2025/11/iBlinds_v3.09_US_11.gbl
Thanks @habhomegit for working on this. I hadn’t heard anything from iBlinds for a couple years and worried it might go out of business. I’m glad to see that isn’t true and has renewed support. Is there hope for updated or new iBlinds products in the future?
Thanks and yep, we’re still here! iBlinds isn’t going anywhere, and we’ll continue to support our current products.
We’re also looking into a more universal version that could work with cordless-lift blinds. That’s something a lot of people have asked for, but it’s challenging because all the new cordless systems moved away from the standards used in corded blinds.
We’re exploring options though, and once we have something solid, I’ll definitely share an update.
Thanks again for checking in!
I’ve got my 7 older blinds updated, but a few are left in a state where it shows null for the battery. Also, I’ve had them not report the proper percent position of the tilt, it always shows 100/closed. And further I don’t know how this firmware could have caused it, but something severely messed up my nabu casa zwa2 host and I lost half my devices, and I’ve had to restore a backup…
Last thing, I still can’t get the v3.15 firmware to update, it either times out or gives an invalid target error…
I’m certainly not an HA expert so others please feel free to chime in.
For the units that refuse to load 3.15, can you please download diagnostics for the node and check what is listed for Product ID? (there may be an easier way to see this)
- 113 = iBlinds v3.0
- 114 = iBlinds v3.1
This will confirm that the correct iblinds version. If you can post (or DM) the Product ID and firmware target shown in diagnostics, I can tell you exactly which GBL file is required.
Running a Re-Interview on the device will trigger a Battery Get request, and the motor will respond with a Battery Report. That should fix the null state.
Note: iBlinds does not send unsolicited battery reports. We leave that to the Z-Wave controller to request on whatever schedule it prefers. On SmartThings and Hubitat, the device handlers poll the iblinds motor once per day. I’m not sure if HA automatically request battery reports on a schedule, or does the user needs an automation for that?
A firmware update on a Z-Wave device will not affect the rest of your Z-Wave network. I’m glad you had a backup to restore from.
Here is a link to another Community Forum user on this subject:
my zwave network must be having problems. I was finally able to get the 3.15 firmware installed on my last blinds. I am still having the problem of it updating the reported value of the blind position. I can tell it to change, and the blinds do adjust properly, it just doesn’t report back the new position… I tried changing the "report’ to disabled or enabled and neither way worked.
This maybe due to some bugs in ZWavejs. The latest ZWavejs release has some fixes related to Window Covering, particularly this one.
Good news everything is working with the latest zwavejs update. the position reports are working, even with send reports set to enabled. Thank you @habhomegit ! I’ve been waiting so long for this.
This has been awesome to watch. I will be interested once 3.15 comes out of beta. I was reading on how to upgrade firmware in anticipation, what method have people been using?
Another big thanks for doing this! Just finishing updating all my blinds now and things are working great!!
I’ve just been using the firmware upgrade feature un zwavejs. Nothing even remotely complicated about it and things are finally working properly again!!
I randomly found this firmware update last night. I updated my 10 iblinds v3.1 to this beta firmware and they work great. Also seems to work well in groups as well with no issues. They update extremely fast after you open/close. I set the devices as a Blind to display and it ends up displaying both styles right next to each other, but also allowed me to continue using the cover change tilt functionality in my automations. Thanks for the update.
This happened to me as well with the new control entity (old cover entity no longer provided by zwave js). So far on 2 blinds it is working well. I’ve been focused on UI and dashboards recently so having the percentage is huge. I’d say having both bars isn’t ideal, but overall not a big deal.
This URL to the beta 3.15 is returning a 404.
Try a HA core restart. HA doesn’t always pick up the changes in-flight.