Thanks for sharing this. I also updated my switches to 2.18 via HA/ZHA and had the same issue but only for the Off command. Adding the ‘OnOff’ binding resolved it immediately.
Served as a great reminder to always thoroughly review the release notes and comments prior to upgrading - I did glance but that wasn’t enough.
In reviewing the release notes for 2.18 and 2.17 I can’t spot any specific mention of this. Maybe I missed it, but it would be helpful to add a specific notice about this to the notes for 2.18 and update the documentation for ZHA group bindings to reflect this change.
The reconfigure option is supposed to do this, but is not grabbing the new endpoint. I am working with one of the core developers on this and hope to have it narrowed down over the weekend for a fix.
For what it’s worth, my pull-request to add the ability to “interview” has been accepted, and it’ll be in a future release of zigbee2mqtt. It should be appearing with an “interview” button, next to the re-configure button.
To be honest, it is a little unclear what “re-configure” does. According to the source, it “calls the zigbee-herdsman-converters definition configure() method”, but I don’t really know what that means.
zigbee2mqtt 1.38.0 includes the changes that allow for re-interviewing devices.
There’s a new “i” button between the re-configure and delete buttons. Clicking that will cause an interview of the device. Unfortunately, there really isn’t any UI feedback to tell you that the interview has completed (it’s usually very fast). The device information should get refreshed, without requiring a restart of z2m.
My recommendation would be to always perform an interview after upgrading the firmware for a device. This will resolve issues like endpoint 3 not showing up, as well as device information appearing to be outdated (ex: upgrade from 2.15 to 2.18, but device page still says 2.15).
There should no longer be a need to delete and rejoin a device after upgrade of its firmware.
Nice! Hopefully 1.38 is also more stable than 1.37 was. I ended up having to roll back to 1.36.1 and a bunch of other people on reddit were having the same issues (devices randomly going offline).
The firmware update process, in Z2M, waits about 2 minutes at the end waiting for the device to respond back. If no response, it reads the version information and updates the device entities. It appears that 2.18 installation process takes a bit of time before reboot happens and so the device is still running a previous version when it is checked by Z2M. You can fix this by reading the data using the Dev Console and pulling genBasic.dateCode and genBasic.swBuildId. This will update the entries in the UI after a few minutes. I can also confirm that the new “I” option will reinterview and give you Endpoint 3 options with the 2.18 firmware.
Darn, I was hoping this trick of interviewing and using then dev console would fix my problem of my switch refusing to update to 2.18. Looks like I need to try and reach out to customer service again for details on obtaining a wire harness…
If you get a harness, I’ll be curious to follow how it works for you… I too am unable to update any of my Blues to 2.18 (from 2.17), and Eric M sent me a harness, but that’s not currently working for me either – it’s just not sending anything thru to the Blue.
I’m on Hubitat, and I’ve easily been able to do every other update since the Blue’s initial release, so this 2.18 thing is a head-scratcher – something in 2.17 or the current driver is killing the update attempt.
I’m doing the harness via Mac (which may be a first), so perhaps its connection issues are somehow related to that – Eric M and I are currently working through the support ticket via chat.
Out of curiosity, are your Blues on a non-neutral setup? Cause I have maybe 7 Blues and the only one causing problems for me is on a single-pole non-neutral LED light above my kitchen sink. The light even has a bypass. Because of this issue and the constant flickering, I’ve decided to factory reset the switch and plan to move it to another location with a neutral and see if I can update it there.
Mine are all on neutrals… To be fair, I haven’t attempted to update all 9 of my Blues, just 3 so far – all have failed the exact same way.
In the device’s Data section, Hubitat has an entry for both “softwareBuild” and “firmwareMT” (build) – after attempting the update, the firmwareMT value stays at 2.17, but the “softwareBuild” value does change from 01020211 to 01020212 (2.17 to 2.18).
While I haven’t noticed any adverse effects from that with the 3 Blues I’ve attempted so far, it does makes me skittish to have those 2 entries not matching, so I’m holding off on further attempts until something changes (new firmware, driver, etc).
I have two zigbee adapters in my setup. My main stick (I can’t remember what it is and I’m not at home) has had no issues updating everything. My other stick, a Tubes EFR32 can’t update more than one device at a time and fails 1/4 of the time to even start an update.
You seem on top of it, but have you tried updating your routers firmware? If you are running an EFR32, have you tried the new EMBY driver within Z2M?
I’m on Hubitat, so not much control over the router unfortunately! But I doubt the issue is on that side of things – I’ve had no problems adding or updating other zigbee devices.
While it seems unlikely, if you do suspect the driver, one thing you can do is temporarily switch to the “Device” driver and run the “Update Zigbee Firmware” command there.
That’s a good call, Robert – I didn’t think to try that! I too doubt it’s the driver, but that (helpfully!) would rule it out for certain.
I have a new Blue arriving this week - I’ll swap it in for one of my current ones so that I can keep it on the bench for further troubleshooting… I’ve documented a lot of my harness-attempt adventures with Eric M, but having one on the bench would really help make add’l troubleshooting & experimentation easier.
In the meantime, I’m grateful that there are no performance impacts, so all is well in that regard – I’m glad not to be pinched by that while trying to sort thru this.
In case it can be useful to anyone, I took my switch that’s stuck on 2.15 and did a factory reset. Then I moved it from a switch that didn’t have a neutral to a switch that had one. I went back through all the setup and it still won’t update. Currently working with CS to troubleshoot but wanted to just share here as an FYI.
Mad props to @EricM_Inovelli for his help getting my Blues updated to 2.18… My Blues were all early-production ones (no bad-batch ones, but all from that same era), and we suspect that somehow had something to do with my inability to go from 2.17 to 2.18…
We ended up going through two different harnesses and some harness-pin placement switcharoos, but we finally got there – all 9 of my Blues are now hummin’ along on 2.18.
Eric – thank you again for your help and patience getting this resolved!
I just wanted to share my feedback that VZM31-SN on 2.18 and VZM36 on 1.01 seems to be working great together. As was mentioned elsewhere, I did need to unpair and re-pair the VZM31 with ZHA (HomeAssistant 2024.6.3 with SkyConnect 1.0) for endpoint 3 to show up for binding (I did use zha_toolkit to scan it and tried ZHA reconfigure but it just wouldn’t show up), but once I re-paired the binding process was easy. Thanks!
