Blue Series 2-1 Firmware Changelog | VZM31-SN

[efaden]

Just installed a bunch of brand new devices with the latest firmware… getting a ton of “UNSUPPORTED_ATTRIBUTE” errors. All of my new ones are giving these errors. Any ideas?

Also note as a result I’m not getting any button actions relayed to mqtt from the VZM31-SN devices… but I am from the VZM30-SN devices.

z2m: Failed to configure 'ZB Master Bath Toilet Light', attempt 1 (Error: ZCL command 0x04e3e5fffeecadfd/1 manuSpecificInovelli.read(["defaultLed6ColorWhenOn","defaultLed6ColorWhenOff","defaultLed6IntensityWhenOn","defaultLed6IntensityWhenOff","defaultLed7ColorWhenOn","defaultLed7ColorWhenOff","defaultLed7IntensityWhenOn","defaultLed7IntensityWhenOff","fanTimerMode","doubleTapClearNotifications"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4655,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:372:28) at Endpoint.zclCommand (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:1005:26) at Endpoint.read (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:481:29) at chunkedRead (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2243:9) at configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2344:13) at Object.configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/index.ts:363:21) at Configure.configure (/app/lib/extension/configure.ts:123:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:252:17))

[rohan]

Ah, the fanTimerMode attribute problem shows up again!

Take a look at this post for more details and a workaround for it:

VZM31-SN reporting 10x actual power

Yep, that’s what I was expecting when I asked you about errors. This is an attribute that we just added to Z2M in the current month’s release since it was missing. It turns out that while the specs say it should be included in the VZM31, it’s currently missing on that device. I have a branch removing it temporarily from the VZM31 that I’ll push up shortly. I’ll link it here when it’s ready. Edit: https://github.com/Koenkk/zigbee-herdsman-converters/pull/9756 is the change. Once that’s merged in…

[efaden]

That seemed to work… but now I’m getting these errors…

z2m: Publish 'set' 'state' to 'ZB - B - Zone 3 (L)' failed: 'RangeError [ERR_OUT_OF_RANGE]: ZCL command 0xb43a31fffe26e207/1 genLevelCtrl.moveToLevelWithOnOff({"level":null,"transtime":655350}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (The value of "value" is out of range. It must be >= 0 and <= 65535. Received 655350)'

[rohan]

Is that happening on its own or in response to something that you’re doing?

[efaden]

Changing the state.

[EricM_Inovelli]

@efaden

z2m: Publish 'set' 'state' to 'ZB - B - Zone 3 (L)' failed: 'RangeError [ERR_OUT_OF_RANGE]: ZCL command 0xb43a31fffe26e207/1 genLevelCtrl.moveToLevelWithOnOff({"level":null,"transtime":655350}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (The value of "value" is out of range. It must be >= 0 and <= 65535. Received 655350)'

I’ve opened a PR to workaround this issue. Hopefully it will get approved in the next day or two while we try to figure out the root cause. If you are familiar with the internals of z2m you need to change the line in the converter:

transition: !transition.specified ? 0xffff : transition. Time

To:

transition: !transition.specified ? 6553.5 : Math.round(transition. Time / 10),

Edit: PR URL:

Inovelli: Fix broken on/off command with recent code cleanup by InovelliUSA · Pull Request #9821 · Koenkk/zigbee-herdsman-converters

[EricM_Inovelli]

@efaden, the PR has been merged. If you update your dev version it should apply the fix.

[efaden]

Thanks!

[adman234]

How can I update to the 3.03 beta firmware using zigbee2mqtt? I cannot find any guides for this. Thanks

[nathanphillips001]

Where is the 3.03 firmware supposed to be? I do not see it here: https://github.com/InovelliUSA/Firmware/tree/main/Blue-Series/Zigbee/VZM31-SN-2-1-Switch/Beta/3.03. And my zigbee2mqtt does not find the update either

[EricM_Inovelli]

@adman234 @nathanphillips001 I will PM you with instructions. There is a bug in 3.03 that prevents the internal temperature from being read correctly so I would recommend to wait for 3.04, but I will PM you with instructions if you would like.

[Snapcase]

@EricM_Inovelli Where can we download 3.04? I can’t find it on the github repo

[adam.h.herbert]

I’d like to know this too. @Eric_Inovelli, can someone please post this firmware somewhere?

[Eric_Inovelli]

Let me talk to @EricM_Inovelli today to see how he wants to handle it. I think we’re still testing it, so we didn’t want to release it publicly yet, but if you PM him, I think he can get it to you.

But, I’ll see where we’re at on posting it publicly.

[adam.h.herbert]

That’s fair, but maybe for the people that are asking PM them the way to get it. I’m about ready to rip out all my Inovelli switches. I can’t imagine that the issues left in the beta are worse than the flickering that’s happening in the production release. If there is a safety issue, then I understand. I would much rather have erroneous power usage or temperature readings than the random pulsing flicker that could cause someone into an epileptic episode.

@Eric_Inovelli, I DM’d @EricM_Inovelli as well. Hopefully we can get a Christmas miracle!

[Lance_Inovelli]

@Eric_Inovelli yes, we are still testing it.

[adam.h.herbert]

I’m going to give an update to those still struggling with the flickering problem. I DM’d @EricM_Inovelli and he was kind enough to share the firmware update instructions with me. I was able to get it installed to a couple of the switches and the problem seems to be fixed.

For anyone else still needing help with this, Eric M said to DM him and ask for the instructions. I know I’m a complainer, but I do appreciate the fact they have a fix for this.

It will me a much more of Merry Christmas in my house this year!

[sgarland]

I received my second batch of Blue 2-1s today, and found that they’re on FW 3.03. My other ones from before the backorder period are on 2.18.

Was it intended for beta firmware to be shipped? Can I downgrade them to 2.18, or at least upgrade to 3.04 since that apparently fixes the temperature sensing bug?

[EricM_Inovelli]

@sgarland we did discover the temperature sensor reporting incorrectly after starting production on that batch. I will PM you with fw 3.04.

[bleblu]

Hey Folks, what is the latest production ready firmware? Based on this Blue Series Dimmer Switch • Firmware Changelog | Inovelli Help Center it looks like 2.18 should be considered the current production version, but I wanted to confirm since all of the versions linked in the first post link to a beta branch. Would it be possible to update the first post when a version is promoted to production, and/or make it consistent with the information in the help article?

My switches are stuck on 2.12 (Firmware: 0x01020212) while using home assistant and I haven’t been able to figure out why. I have Inovelli configured as a provider in ZHA and one of the on/off switches did receive an update recently, but none of the dimmers have. Thanks.

My ZHA config:

zha:
  zigpy_config:
    ota:
      otau_directory: /config/zigpy_ota
      extra_providers:
        - type: inovelli