Great, I ordered some. FYI, I gave up on this PR since it was no longer getting any attention:
I created a new one that will hopefully be addressed much quicker.
I am also going to make a kb article about getting rid of duplicate entities. The easiest way (after this PR gets worked through the system) will be to delete and re-add the device. Alternatively, you should be able to search for them and bulk disable them. It will show how in the article.
Bit late here, but FYI “stay life” controls how long you can stay in a “stay zone” without being seen. If you don’t have any of those defined it won’t do anything. In your case, I’d add one around your couch. I have stay zones programmed for beds, toilets, and showers, which have eliminated most of my issues.
- Fixed an issue where the switch would stop functioning when P17 (Load Level Indicator) was not set to 11
FYI, I spend an hour or so today beating my head on this P17 issue. (It’s just so non-intuitive that out of all the settings I was applying that one would break things!) Happy to test if you need more testers, and have to say I’m looking forward to the bouncier debounce logic as well.
Sounds good, I am going to be releasing firmware 1.02 to the Z2M and ZHA firmware channels today or tomorrow so it might be worth a wait instead of installing it manually.
Are the changelogs posted somewhere?I just got them today!
I had the updates popup in HA, but my switches (both on v1.00) would start the update got to 2-4% and the return back to Update. Did an air gap reboot and am trying the switches one at a time. Going into the Z2MQTT UI and trying to use OTA shows no update available. Any tips for a newbie? Is the OTA on github the current (vzm32-sn_mmWave_OTA_V102_20260330.ota) even though it is in the Beta folder?
Yeah, that should be the same as what is being sent out through Z2M. If the update didn’t succeed then it should appear at a later time for you to attempt again. It may have also completed though and you can check with the method at the bottom of this article:
Blue Series • How to Update Firmware With Home Assistant (Zigbee2MQTT) | Inovelli Help Center
Doesn’t that mean you have to reconfigure any SmartThings automations that rely on or control that device?
Sorry, but I’m not understanding your question. You responded to my post about how to tell the firmware version in SmartThings. Is your question is do you have to recode an automation after a firmware upgrade/removed device? Usually, the automation will remain after a device removal with a placeholder for the device you removed to upgrade the firmware on another hub. You just have to edit the automation to replace that device.
I was replying to the last line in that message: “I temporarily move devices into Hubitat to upgrade them. Quick and painless.”
If you have dozens of devices and hundreds of automations referencing those devices, moving the devices back and forth from Hubitat to SmartThings is an absolute PITA, full stop
Agreed. But there are not a lot of choices. I try not to do updates unless I really need the change. More often then not, I’ll just stick with a certain release unless I need the newly implemented whatever.
I wind up doing more firmware updates to to beta testing rather than production.
Did something change in regard to the led_effect handling? I’m not sure where the breakage is exactly, but in Home Assistant (using Zigbee2MQTT) a call like the following fails:
action: mqtt.publish
data:
topic: zigbee2mqtt/0x0000000000000000/set
payload: |
{
"led_effect": {
"color": 1,
"duration": 2,
"effect": "solid",
"level": 100
}
}
However, when I switch to targeting individual LEDs (via the individual_led_effect payload instead), it works fine.
action: mqtt.publish
data:
topic: zigbee2mqtt/0x0000000000000000/set
payload: |
{
"individual_led_effect": {
"color": 1,
"duration": 2,
"effect": "solid",
"led": 0,
"level": 100
}
}
Additionally, it seems that group led_effect call works if I bump the duration to 3 (which I’m doing in the interim).
Perhaps it’s coincidence, but I noticed this after switching to the v1.02 about a week or so ago.
Just for my clarification, for the Inovelli VZM32-SN, is version v1.02 officially released as standard production? And is it avaliable on the ZHA channels (As of 2026-07-08)?
I’m not seeing it show up as an OTA update in ZHA for my device. The “Firmware” entity shows “Update-to-date” and shows:
Installed version: 0x01030100
Latest version: 0x0103000a
Not sure if i’m doing something wrong on my end? I do have custom zha quirks setup for this device (for accessing the presence entities). Not sure if that gets in the way of the update checking mechanism?
I’m particularly interested in applying the fix for the "led bar notifications not clearing) issue.
Is it recommended to try to manually download the binary and apply it via the zigpy_ota directory? Or should ZHA pick it up eventually if i give it a few more days?
Thank you.
Do you happen to have a custom ota url setup?
Something like this:
zigpy_config:
ota:
extra_providers:
- type: inovelli
url: https://inov.li/IRbxhx1646F/firmware-beta.json
or this:
zigpy_config:
ota:
z2m_remote_index: https://inov.li/IRbxhx1646F/firmware-beta.json
If you do, try to delete the config and restart HA.
Thank you for the quick reply. Much appreciated.
Unfortunately, I don’t see any custom ota setup. I assume this would be in my configuration.yaml, or a file included therein? If so, I’m not seeing it. I also checked the zhacustomquirks/inovelli directory (both the init.py file, and the VZM32SN.py file). Nothing in there seems to specify any OTA configuration.
I’m running Home Assistant OS (Core = 2026.1.3; Supervisor = 2026.06.2; OS = 17.0). Any chance there was a recent change in ZHA within HA, and I need to update to a newer version of HA to properly retrieve the latest firmware update? (My understanding is that as of 2026.1.0 I should not need the custom ota setting, correct?)
Not sure if this helps, but I also have a recently installed VZM31-SN. I’ve not been notified of a firmware update for it, but its firmware page shows 0x01020304 both for Installed and for Latest. Does the fact that this version is showing for “latest” tell us anything? (e.g., does that tell us that my system is looking at a beta channel for all Inovelli devices, or conversely does it confirm that we are looking at the proper channel?)
Any help would be appreciated. As would any comments from others that are running ZHA that have been able to get the latest version for the VZM32-SN.
Soo… has 1.02 actually fixed clear_effect for anyone? I still have the same problem that if I send individual led effect with effect solid (led 1, color 30, level 100, duration 255) it lights up correctly, but then I send effect clear_effect (all other params the same; they should be ignored, right?), the led stays lit. This works just fine on both VZM31-SN and VZM30-SN. Even if I do solid with a duration of 2 seconds, it doesn’t clear it automatically.
I’m eagerly awaiting that fix as well. It didn’t make it into 1.02, but I’m hoping for it in the next release.
Ok, I think I know what is happening. ZHA changed how updates work a couple of months ago:
Remove the Inovelli OTA provider by puddly · Pull Request #1820 · zigpy/zigpy
I went ahead and updated the old json feed with the firmware update, so you should see it eventually on your older install. Updating your HA core will also enable the update (through the new method).
Thanks for the update. I am, however, still unable to update from the HAOS Setting-> Updates (Installed version 16974080 Latest version 16974082) or via the OTA in the Z2MQTT dash. Both places look like they are going to update, then bail out, go unavailable, and then show the update again. Everything up to date on a Promox HAOS miniPC setup.