Is 3.04 not supposed to be released? I hit the buttom to update in Hubitat and it updated the switch to 3.04.
3.04 is solid, and I expect it’ll eventually be blessed as Prod.
There was a couple of us helping test 3.04 on Hubitat, so Eric M (and presumably Mike Maxwell) made it available for us to grab.
That was originally done on the down-low so as not to attract a ton of attention (particularly when 3.04 was brand new), but the cat’s obviously getting out of the bag now… And 3.04 seems to be a very solid release (I’ve been on it for over a month with 9 Blues), so I wouldn’t hesitate to update.
2 Likes
It’s a little counter-intuitive, but 0x01020212 is v2.18. You’re on the latest production firmware release.
1 Like
Oh! Thanks for pointing it out! I completely missed the discrepancy there!
Out of curiousity, when do you plan on releasing a production rev? It looks like 3.x firmware has been in beta for close to a year and a half.
Just trying to decide if trying the beta is worth it?
3.x started in July 2025. So not quite that long yet! Personally, I’d try the beta if you’re having flickering issues. There’s a couple of separate issues that Eric and team are working on fixing before 3.x goes to production. I have no guess as to timeline for that though.
I will say I’m running nearly 25 VZM31s on 3.04 and it’s been solid.
1 Like
Ha! My bad - I read the year wrong (or my math clearly wasn’t mathing)! Thanks for clarifying - 6 months is way different for development betas than a year and six months!
I’m having issues getting most of my switches to update.
This post in the non-neutral installation thread points to possibly needing the harness to update the bootloaders on older switches to get it to take the update to work, which is rough…
I had issues getting one of my switches to 2.15 (I think) and had to borrow the harness. That one took 3.04 fine. All 5 of my other switches had no issue taking the updates up to 2.18, but are refusing to update to 3.04 now. I still have one in the box from the original release as a backup that I have not tried updating yet.
Yeah that behavior sounds exactly like you need the harness. I had about 10 switches in the same boat. It’s not fun, but it’s fairly easily doable.
Bummer.
I guess it’s time to bite the bullet and order a debugger for myself. I’ve had a couple of things I’ve wanted one for but never really needed it. It will be nice to have one on-hand.
Thanks for the confirmation!
The changelog help article doesn’t appear to have any information past 2.18. Are there plans to have this updated?
Shoot, yeah, we forgot about that one. @Lance_Inovelli can you update the help document with the info here?
Done.
2 Likes
Will this new version be uploaded for upgrade through Zigbee2MQTT soon?
@tigermike83 I just put it in the z2m json file today so I believe it will start showing for users tomorrow.
If anyone has troubles updating please refer to our help article: Blue Series Switch - Troubleshooting OTA (Over-the-Air) Updates | Inovelli Help Center
1 Like
z2m has updated, Updates are available in my HA instance (2/12/2026)
Seems to only be a cosmetic issue, but wanted to raise it. The version tag in Z2M says Unknown:
Or is this something I need to correct? - I tried restarting.
Thanks, z2m might just need some time to update that field. It is filled in for mine.
1 Like
@EricM_Inovelli Can I make a suggestion for the Zigbee2MQTT firmware upgrade guide? The post-upgrade firmware version discrepancies can be resolved by re-interviewing the device, which can be done by clicking the “i” icon on the device’s page or device listing. This will query the device’s firmware version, among other things.
Its still not fully automatic, but at least you don’t need to navigate to the dev console and manually query each device, anymore.
1 Like