Yeah, this is true. The problem right now is that we use a “shared” firmware listing file. Once I put the firmware in the json file then both zigbee2mqtt and zha have it available.
Edit: I think I will work on having separate files in the future.
There is a way to point z2m at an alternate url to make it possible to update right now. If anyone is interested, you can PM me.
The easiest way to ensure you have the latest driver is to use HPM – you can even have HPM check for for updates daily or whatever.
I believe 2.05 is the latest firmware currently available on Hubitat – that’s what I have on my switches right now – I updated earlier this week, and the 2.05 updates for each switch went fine.
Cool, will give it a spin. Here’s what I did if it helps others:
It’s still on fwVersion: 2.00 and fwDate: 20200805 though …argh. Seems like HPM just manages the Hubitat drivers (or apps…), not firmware?
HPM is just drivers. For firmware, you need to go into the individual switch and do the double click on update firmware button. Have another tab open and watch the logs and you’ll see which firmware update is taking place (this is at least how I do it).
I just went through the update process on Hubitat and despite the process completing successfully (it showed progress in the logs once it started), it looked like nothing happened. Like you describe, once it completed, the device page didn’t reflect the change for me either … ultimately, I just air-gaped the switch and as soon as it restarted, the device page showed the new firmware version.
Sorry, I’m feeling like a total idiot, but what’s the version you’re updating to? I enabled trace logs and when double-clicking the updateFirmware button I get:
dev:332022-11-11 09:55:42.996 PMtraceupdateFirmware [he raw 0x175C 0x01 0x01 0x0019 {09 01 00 03 64 FFFF FFFF FFFF FFFF}]
dev:332022-11-11 09:55:42.984 PMinfoKitchen Cans: updateFirmware(switch's fwDate: 2020805, switch's fwVersion: 2.00)
dev:332022-11-11 09:55:42.245 PMwarnFirmware in this channel may be "beta" quality. Please check https://community.inovelli.com/c/switches/switch-firmware/42 before proceeding. Double-click "Update Firmware" to proceed
dev:332022-11-11 09:55:42.238 PMinfoKitchen Cans: updateFirmware(switch's fwDate: 2020805, switch's fwVersion: 2.00)
And nothing visibly happens in Hubitat after giving it a minute and refreshing. Air-gapping and resetting the switch I’ll get some heartbeat info messages when it comes back online, then still the same FW versions.
I guess I’m confused by all the dates and versions it seems to report:
Comparing to non-updated one, it’s just the Device Details section that’s different with
So look at the last 3-4 digits for the version? …0200 → 2.00, …0205 → 2.05?
Is the fwVersion and fwDate a red herring in Hubitat (is it a driver thing, and “fw” means something else)…argh. Hubitat confusion aside, I’m still getting the blinking in my 4-way switch setup 
Try double clicking again . . . maybe a little slower and watch the logs. It is very apparent when it goes. It will say that it is updating in the logs and the switch will start flashing green. It looks like you are still on 2.00 so it should update to 2.05 now and then 2.08 as soon as Hubitat makes the file available.
Air gap worked for me as well.
I want to point out that while this is an option, this is done at your own risk.
For example someone using ZHA could use the firmware link to download 2.08 today, but if your switch is reset and the cached signature is lost, it will ‘break’ the switch as the quirk won’t match and you’ll lose all the options set up through that and drop back to a minimally supported device effectively. Similarly other releases could break things on other hubs as they’re being tested out before being properly ‘released’.
For those running HA+ZHA who may be interested in getting group bindings going again, I manually updated my firmware to 2.08 and then used Python pip to upgrade my HA instance to use the latest ZHA quirks library (0.0.86). It looks like dimming and on/off functions were intentionally removed from endpoint 1. I gave endpoint 2 a try and that seems to work wonderfully.
A question I have for the ZHA people out there… How do I get HA/ZHA to start using the new InovelliVZM31SNv12 custom device class without removing and re-pairing the switch? Is that possible?
You can try restarting HA but I believe it’s going to keep the cached image until you remove and re-pair the switch. Factory resetting at the switch should also do it (may need to delete it in HA as well first, blanking on that).
looks like the HA pull request was merged, i’m hoping it will be available for auto update today at some point 
Any time you update the firmware or the driver, you should follow that with a click on the Configure button on the Device page. Configure with no options will update the version state variables (and a few other things). I recommend that you use the “All “ option on the Configure button just to make sure all the settings and variables are in sync
2022.11.3 needs to be released unless you’re running dev.
@kitt001 @TRiddle1983 I recommend using this method a few minutes after the firmware update completes. You can also just hit “Refresh” on the device page and it will query the device for the firmware version.
The worry I have about the air gap method is that you might pull it while the firmware is being written to storage and that could break the switch. There is some time after the green LED bar flashes that the switch is doing the update process, so it is probably good to wait a couple minutes and then follow one of the above steps.
that’s unfortunate, any clue when that is supposed to happen?
Whenever the devs decide unfortunately. Could be anyone’s guess. There’s never a set cadence for patch releases.
There are usually 5 or 6 patch releases a month. Usually a little more than one per week. Last one was about 3 days ago.
Sorry. The above is a bit over my head. Are we saying that in order to update the firmware on my blue in Z2M from 2.07 to 2.08, and I don’t want to perform some unique workaround, I need to wait until the next HA core version 2022.11.x, is released? And that to do this in Z2M, I’ll need to install the core update first?
I updated my blues to 2.07 in Z2M (a HA add-on) on HA core 2022.10.5. The above seems really unlikely to be true so I’m sure I’m missing something. Seems like this should be independent of HA core and even possibly Z2M updates all together.
From what I gather, whatever changes the firmware required, depended on a newer version of the “quirks lib” within HA:
Inovelli requested the version ‘bump’ (upgrade), it was approved and will be included in the 2022.11.3 HA release.