ZHA Firmware Update Guide

Switches General Discussion
,
#21

I’m having exactly the same problem. I’ve tried every firmware update guide out there, and none will work through ZHA for me. I’ve got one switch on 2.15 (and five more of those to install), 22 on 2.14, and 3 on 2.08. Every one of them indicates that they’re up to date.

I’ve tried adding the firmware to the zigpy_ota directory as per the guide and got nothing. Tried renaming the firmware to VZM31-SN_2.15.ota to make sure the syntax matched exactly and got nothing. Made sure the file was the right size. Changed the true/false flag for inovelli_provider. Rebooted after every step–no luck. Tried forcing the update with ZHA Toolkit, tried forcing through the Manage Zigbee Device dialog…no luck.

At this point, I’m either really doing something wrong, or I’m running into a software configuration problem that I’m just not seeing. Just checked my HA version, and I’m current at 2024.2.2.

…so I’m definitely watching to see what others are doing, because I seem to be striking out.

#22

I saw this earlier today and I feel that maybe it’s a bug. This is what I see when I click on the Firmware Update for a switch:

image
image864×426 28.1 KB

But when I look at this in the Manage Zigbee Device page, it shows we are still out of date.

image
image746×288 17.1 KB

image
image778×634 31.5 KB

#23

The firmware image available for ZHA is still set to 2.08, anything at or past that will appear as up-to-date until it’s updated.

1 Like
#24

Do you know where that check lives, offhand? I was thinking about trying to just bypass this for now. I assume there’s some kind of a “registry” somewhere that defines latest versions that I could hack around.

#25

It’s within the zigpy config and points to the json published by Inovelli. I’ll note though, it looks like they’re redoing the way zigpy handles OTA updates and may be worth just waiting for that to get merged in and you’ll be set.

#26

What I’d really like from ZHA is an actual GUI that shows available versions for any particular device, including custom uploaded binaries (still requiring signatures, of course), and for them to provide a “force” option so we could ignore the version checks and perform downgrades. Maybe some day!

Thanks for pointing me in that direction… waiting for updated merge in core is probably the best bet, but I might get a little squirrelly and play with some simple regex on the JSON that it’s using for the registry to bump from v1.08 → v1.15 meanwhile.

Edit: Yeah, looks like this is where it’s pulling the registry from: https://files.inovelli.com/firmware/firmware-zha.json - here https://github.com/zigpy/zigpy/blob/4b77fc267d3c3edffae2e42cc9c17f0f85afc76e/zigpy/ota/provider.py#L692

#27

OK, so I was able to get this to work.

!!! THIS IS ADVANCED, AND YOU CAN BREAK YOUR ZHA FUNCTIONALITY IF YOU DON’T KNOW WHAT YOU’RE DOING; ONLY ATTEMPT THE FOLLOWING IF YOU UNDERSTAND WHAT THIS IS DOING, HOW TO UNDO IT, AND THAT LATER HA INSTALLS WILL OVERWRITE THIS ON ITS OWN - WAITING FOR OFFICIAL ZHA UPDATE IS PREFERRED !!!

OK, disclaimer out of the way… if you add the following patch to zigpy (/usr/local/lib/python3.12/site-packages/zigpy/ota/provider.py), it’ll find the latest firmware (only the line starting with fw_lst, this is in the Inovelli::refresh_firmware_list(...) func):

        self._cache.clear()
                                   
        fw_lst['VZM31-SN'].append({"version": "16908815","channel": "beta","firmware": "https://github.com/InovelliUSA/Firmware/raw/main/Blue-Series/Zigbee/VZM31-SN-2-1-Switch/Production/2.15/VZM31-SN_2.15-Production.ota","manufacturer_id": 4655,"image_type": 257}) 
                                                                                                                                                                                                                                
        for _model, firmwares in fw_lst.items():

This injects the 2.15 firmware JSON into the ZHA upgrade checker, so it’ll find it once you trigger the upgrade. I then restarted HA and manually triggered the firmware upgrade on the device (I used ZHA Toolkit). The switch found the firmware and flashed successfully (the ZHA updater UI actually worked fine at this point).

The better short-term fix would be for Inovelli to update the JSON at https://files.inovelli.com/firmware/firmware-zha.json to just include the 2.15 firmware (all this patch does is add that into the payload from that URL). Medium/longer term fix will be for ZHA to update (like chack mentioned) to hopefully fix manual_ota updates via the zigpy_ota directory again.

Anyway, if someone NEEDS to upgrade their switches meanwhile, you should be able to do the above… but avoid unless you know what you’re doing.

1 Like
Blue Series Fan Switch Firmware Changelog | VZM35-SN
#28

This worked for me. I had to reset my inovelli_provider to true then it finally worked. ZHA_Toolkit did nothing for me without that and didn’t seem to do much for me anyways. Just wanted to add my two cents.

#29

I think I’m in a similar situation. I tried using VS Code to open provider.py, but I don’t see a /usr/local/lib/python3.12/site-packages directory. The closest I see is /usr/local/lib/python3.11/dist-packages. Any idea where I’m going wrong?

#30

This may be the explanation of why the custom OTA file update doesn’t work any more, and a workaround:

#31

@EricM_Inovelli do you guys plan to update the ZHA json file at some point? This is resulting in a lot of folks having to do some circus to get firmware updates on their switches. Just curious if it’s intentional or not. :slight_smile:

#32

Good news is that ZHA has changed the way they handle OTAs so we will be implementing the new method soon (probably in the next HA release). Also good news, the changes made to how ZHA handles updates has also made manual updates much easier. You can just add this to your configuration if you have a recent release of HA:

zha:
  zigpy_config:
    ota:
      z2m_remote_index: https://inov.li/omega/firmware-zha.json

I don’t recommend doing this yet though because there is a fingerprint change in the latest firmware that requires a change that will probably be in the May release of HA:

Add Inovelli VZM31-SN firmware 2.17 support by InovelliUSA · Pull Request #3076 · zigpy/zha-device-handlers (github.com)

5 Likes
#33

Thanks for the update Eric :slight_smile:

I have been anxiously waiting for a while to try out the version with trailing edge control. I did the manual update by editing the zigpy ota and adding the 2.15 info.

Once I rebooted HA I saw the prompt and could update my switches. But I am happy to hear that it’s going to be available for the masses via one click in ZHA :slight_smile:

#34

Instructions unclear. Updated 31 switches to 2.17.

(I kid; that was probably not smart and people should probably wait, but for what it’s worth, there doesn’t seem to be any problems running it prior to that PR being included in the next release. Now to dig through the Zigbee params and experiment, and see whether it fixes the flickering I had on 2 lights…)

#35

@EricM_Inovelli Is this still the recommended URL? Reason I’m asking is that it doesn’t have version 2.18.

I’m on HA 2024.5.1 and I have tried every other suggestion I found around the community and nothing but this will works for me, the only down side is that if offers me to upgrade to 2.17.

#36

I’m out of town, but will add 2.18 to the main manifest when I am back on Monday. In the meantime I believe you can use this manifest file (same url except for the end): firmware-218.json

2 Likes
#37

(post deleted by author)