Blue Series 2-1 Firmware Changelog | VZM31-SN

[harjms]

After completing the update, go to Configure->All and then Refresh->All. Then refresh your browser page.

[jjr]

Updated one of my switches using z2m – took around 30 minutes; is this typical, or do I have a crappy controller [husbzb-1], or is there a turbo button somewhere I can press to make the next ones go faster?

Also – Thank you Inovelli for the new features! The Aux Scene one is very interesting – I was wanting something like that… Now to find a need for the want I have!

[mbrink]

30 minutes is typical. You can run more than one at a time.

[PreZ]

I thought we were not supposed to due to bandwidth concerns, etc. on Zigbee.

I have 60 switches to update … ugh.

[Eric_Inovelli]

@terrence.bentley

I’m simply not happy at all with this update. It has made all of my other, non-Inovelli smart switches obsolete and that’s gonna cost me some dollars to replace with more Blues.

Lol you had me there with that first sentence! Glad you like it

@SViel

Love 2.14 firmware! I had an Ikea 5-led light that buzzes and flickers with other dimmers and previous firmware. With the 2.14, it works perfectly when I set it up this way:

That’s awesome to hear! Glad we got rid of that buzz!

@epow

Thank you SO MUCH for pushing this through, even though your original conversations with the manufacturer were less than promising. My Blues are far more useful now than they were a few hours ago, and it’s fantastic to see (or in my case, hear) how much better the dimming function has become. No more buzzing light fixtures!

Yeah glad to push that one through. I’m really happy with how the switch performs with LED’s now. I didn’t have much of an issue with Leading Edge on my bulbs, but it was probably one of our biggest knocks against us, so I’m glad they figured it out!

Amazing what you can accomplish with code!

@mtnbiker717

On the final batch of switches, the install time has gone from 45-60 minutes a switch to 30ish minutes. I’m wondering if the improvements to the switches are allowing faster communication including downloading the firmware to the switches…

Hmmm yeah that’s a great theory and makes sense to me!

@jjr

Updated one of my switches using z2m – took around 30 minutes; is this typical, or do I have a crappy controller [husbzb-1], or is there a turbo button somewhere I can press to make the next ones go faster?

I’ve seen it vary. I think I was averaging 20 min or so for each switch. Sometimes longer depending on how far away it was from the hub.

[Skooj]

Still waiting on zha to get the update. I see that the json file was to be updated, but it looks like it wasn’t yet. Are we waiting to push it there or was it missed?

Edit: follow up question. In another thread, someone mentioned that a fix for some sengled bulbs dropping off the network will be fixed with this firmware, but I am not seeing specific mention of that issue here. Is this issue fixed here?

[dahanc]

@mtnbiker717

I’ve updated 6-7 at a time.

How do you control which ones get updated?

I’m using HA with ZHA, and it seems to be trying to update all of my switches at once, which isn’t working. Back when I only had about 6 or so switches installed, they updated to 2.08 fine. Now I have 16 switches, and the switches flash their green progress bar for a long time without making much progress (haven’t actually timed how long), then the lights controlled by the switch flicker. I think the LED flashes red a few times, but I’ve only caught one doing that.

And in the HA log file, I see:

2023-04-11 22:58:01.188 ERROR (MainThread) [homeassistant] Error doing job: Task
 exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 1039, in
 request_callback_rsp
    return await callback_rsp
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 1036, in
 request_callback_rsp
    async with async_timeout.timeout(timeout):
  File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line
 129, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line
 212, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

I don’t actually know anything about how OTA updates work, but my guess is that trying to update all the switches at once is bogging down the network and ZHA is giving up before it can finish sending the firmware. So it might help if there’s a way for me to update a few at a time.

[Skooj]

With zha, you can use zha toolkit GitHub - mdeweerd/zha-toolkit: 🧰 Zigbee Home Assistant Toolkit - service for "rare" Zigbee operations using ZHA on Home Assistant to call a service to make it happen.

It’s interesting you are getting updates though, I’m still waiting and have no sign any of them have tried…

[uLLfAEVeKVgMvpiA]

I just opened Updates to match 2.14 firmware (previous 2.08) by michaelkkehoe · Pull Request #5654 · Koenkk/zigbee-herdsman-converters · GitHub to get Z2M up to date.

Please let me know if I missed anything.

[Byarnell05]

Kinda surprised at these update times that people are posting. I updated 4 switches using a hubitat C-8 and it took ~8 minutes per switch.

[tube]

@Skooj

It’s interesting you are getting updates though, I’m still waiting and have no sign any of them have tried…

You can download the OTA to the OTA folder you have configured under zha in configuration.yaml. See the zha docs for the OTA folder option

[Skooj]

Interestingly, I tried that earlier and got nowhere with it. I’ll give it another shot and let it sit overnight.

edit: I was able to get it to go. No idea what I did wrong 4 hours ago, possibly file permissions from the wget. Thanks!

[TheTisor]

Now that these switches have trailing edge dimming capability, I think it’s safe to say that these are easily the best smart switches on the market and it isn’t even a close contest anymore.

Thank you for trailing edge! My lights thank you too!

[jamieb122]

Any pointers on where to grab the OTA? I can’t seem to find it in the repos I’ve seen floating around this discussion

[ThatTallGuy]

I’m having the same issue…

Did you or anyone else figure out how to fix this? I believe all 4 of my switches are on 2.14 now but the UI in Z2M says they’re still on 2.07 or 2.08…

[chack]

Inovelli posts all of their firmware publicly, just have to go to the right switch > folder and end up here for the Blue 2-1’s.

[mamber]

@Byarnell05

Kinda surprised at these update times that people are posting. I updated 4 switches using a hubitat C-8 and it took ~8 minutes per switch

Same here. ~8 minutes using Hubitat C8

[sdbigio]

@Skooj

I was able to get it to go. No idea what I did wrong 4 hours ago, possibly file permissions from the wget. Thanks!

I think I’m having the same issue. I added one switch to HA. Inserted code to configuration.yaml, and downloaded the 2.14.ota file to the update folder. That was 12 hours ago and no sign it has tried to update firmware. Any ideas? Ty

This is on ZHA HA btw

[mtnbiker717]

@dahanc

How do you control which ones get updated?

I’m using z2m, so I’m not sure… Sorry!

[epow]

@mamber

@Byarnell05

Kinda surprised at these update times that people are posting. I updated 4 switches using a hubitat C-8 and it took ~8 minutes per switch

Same here. ~8 minutes using Hubitat C8

My z2m OTA update times are always in the 30-40 min range - doesn’t matter what vendor/model we’re talking about. I’m wildly guessing that z2m may be implementing a poor-man’s QoS throttle to prevent the update from causing congestion on the network. Is there anyone involved with zigbee-herdsman development lurking on this forum that can explain the slow OTA times using z2m?