Hi group,
Dumb question. Is 2.18 a production release, or still a beta? It’s living in the beta folder, but many here are jumping and running with it like it’s production.
Thanks,
Jonathan
Seems like a reasonable question with not such a clear answer.
Should we upgrade to 2.18?
Beta has been through manufacturer and Inovelli testing but has not been certified with 3rd party entity ($$$$$). It is safe for installation at this time.
1 Like
I still have 30+ switches on 2.14 and it’s working OK. Were there any performance or multicast improvements post 2.14? I only want to update if multicast and other zigbee repeater functionality got better. Pre 2.14 the switches caused my network to barely work. Any insight before I take the plunge?
I am running 2.15 on my Blue 2-1s…over 100 switches that are part of a 324 device single Zigbee2MQTT network. Currently slowing rolling out 2.18 to support some of my fan switches with the 2-1. My network is very stable and super fast.
Changes detailed here:
I saw this but it doesn’t get into the real level of detail. It’s always more about features. I’m hoping core zigbee protocol updates are happening because these are essentially my only repeaters and pre-2.14 it was unusable.
Yep . . posted that in case you weren’t aware. EricM will have to comment with the in-depth info.
Hey, just wanted to ask about an error I’m seeing. The error below populates pretty regularly in my HA logs and happens for any VZM31-SN I attempt to get/set the switch’s fanTimerMode attribute. It may be more often than that, but that’s how I’ve been manually triggering it. In Zigbee2MQTT, there’s a related error (also below). Version info is below as well. Curious if anyone else has seen similar, if this is a known issue, or if I’m lucky enough to be unique 
Home Assistant logs:
Invalid option for select.primary_bedroom_switch_lights_fantimermode: '' (valid options: ['Disabled', 'Enabled'])
Zigbee2MQTT (v1.37.1 commit: unknown):
2024-05-23 15:53:22Publish 'get' 'fanTimerMode' to 'Primary Bedroom switch- lights' failed: 'Error: ZCL command 0x040d84fffe02baea/1 manuSpecificInovelli.read(["fanTimerMode"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4655,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')'
Home Assistant core: 2024.5.4
Zigbee2MQTT: 1.37.1 commit: unknown
VZM31-SN FW: 2.18
For what it’s work, I’ve had no issues getting/setting this attribute value from my handful of VZM35-SNs.
1 Like
I would imagine that you have to set SingleTapBehavior (P120) to the New Mode to enable that feature to work. But that means you are binding this to a fan switch and not sure you get all the light control you want.
How did you get 2.18 onto your switches via HA? I thought I have it configured properly, was able to get 2.17, but it won’t recognize 2.18 as an available update.
You have to be on the current/latest version of HomeAssistant and it should detect the upgrade for them after a little while.
2 Likes
Can anyone point me in the right direction here? Never got a response to my message above. Am I supposed to contact Customer Service and request a wire harness?
1 Like
I would contact support if you haven’t already. I know both Erics try to be active here, but they’re also handling the support queue, working on the current and upcoming products, etc and can’t always respond.
Hey all, I’m trying to bind a VZM31-SN to a fan canopy module via: Setting Up Your Blue Series Fan/Light Canopy Module With an Inovelli Blue Series Switch • Home Assistant (ZHA) | Inovelli Help Center
I’ve updated the switch to the latest 2.18 firmware (0x01020212), but I don’t have an Endpoint 3 (config button) available in the Binding settings in Home Assistant (2024.5.4), any thoughts?
You need to unpair and repair it after the upgrade for endpoint 3 to be visible.
2 Likes
That did it! Thanks so much!
1 Like
Edit: my extension is no longer needed. Upgrade to zigbee2mqtt 1.38.0, and you’ll have the ability to interview devices via a button or API. https://github.com/Koenkk/zigbee2mqtt/releases/tag/a1.38.0
Hi all, first time post, here. I didn’t like the idea of having to remove and re-add the switches in zigbee2mqtt in order for endpoint 3 to show up and be usable. Deleting/re-adding devices makes for a lot of work downstream in HA, and I wanted to avoid that. As far as I can tell, the devices simply need to be re-interviewed, but that’s not something that zigbee2mqtt 1.37.1 does out of the box.
So, I created a user extension I call “ReinterviewExtension”, which allows for kicking off a re-interview of a device via the MQTT API: Extension for zigbee2mqtt that allows for reinterviewing of existing devices. · GitHub
The above gist provides all the instructions on how to install and use this extension. I should note that, after the re-interview, you may have to restart zigbee2mqtt in order to pick up the new endpoints. I did this on the 17 or 18 VZM31-SN switches in my home, and everything seems to be working fine. The devices are showing endpoint 3, and I was able to set up new bindings.
I’ve also submitted a pull-request to zigbee2mqtt, adding the ability to re-interview devices. If this gets merged in, it would eliminate the need for my extension.
5 Likes
Upgraded to 2.18 through the ZHA update from Home assistant
For 2.18, you must now bind both On/Off and Level Control to get the switch to work correctly with a Zigbee group binding. This is actually more technically correct, but you need to know to adjust the bindings to get what you are expecting.
This is what worked for me to fix the issue of the lights not turning off and on through the switch
Just tried your extension. Works great! I hope the PR gets merged 
edit: nice, i’m post 1000 in this thread 