This will be a thread for listing out any bugs you may find and/or any enhancements you’d like to see for the Blue Series mmWave Switch (VZM32-SN).
This is not a thread for troubleshooting personal problems – please create a new thread so we can properly help.
Question / Enhancement Thought
Will there be, or is there already, an HA add-on we can use to configure zone settings or create rooms and zones via a GUI? And in the same vein, is there a way to configure multiple detection zones and bind actions to detection in those individual zones?
I read through the setup documents in the help section, but didn’t see an obvious answer to this. The attached image is a sketch of an area I have, with a hallway/stairway (yellow and green areas) and two bedrooms (blue and purple). The numbered red blocks and arrows indicate the locations and directions of the MMWave switches. What I’m trying to figure out, configuration- and usage-wise, is how I would set up switch 1 with two zones, each paired to different lights/automations. Zone 1 would be the yellow zone, configured to turn on the hallway lights, and zone 2 would be the green zone, which would turn on the laundry room lights as you approach.
I’ve been using the Everything Presence Lite sensors and their GUI / designer addon for configuring zones for a similar purpose, so it’d be awesome if the inovelli’s could be linked to a similar GUI for building rooms/zones and placing the sensor within it, then having the addon calculate the zone geometry and save it to the switches.
Heads up regarding ZHA & Inovelli device handlers
After we verified that everything in the ZHA configuration was functioning properly, a GitHub push switched our device “handlers” over to the Quirk v2 framework. Unfortunately, the v2 quirks weren’t fully up-to-date compared to the existing v1 versions, which caused some loss of functionality.
Good news: there’s already a PR open to bring the v2 quirks up to parity:
In the meantime, you can install a custom quirk to restore full functionality until the PR is merged. The instructions are available here:
The ZHA team has labeled the PR as medium-priority, so hopefully it will move through review more quickly.
We’ll keep everyone posted when the fix is merged — but for now, using the custom quirk should keep things working as expected. If you run into any issues, feel free to reach out!
This is a great idea. I’m happy to take a look at what’s out there already and try my best to come up with something and/or work with you all to bring it to life.
When I’m on my computer, I may split this idea into its own thread so we can discuss it in more detail and try to nail something down.
I was working on something similar a couple months ago and maybe there’s some overlap. I just frankly didn’t have the time to finish it.
The concept was that you could use your phone’s built in augmentation mapping to map out the room and then tie that back to the initial setup of the switches parameters to easily set the zones.
Maybe this could also work in conjunction with what you’re proposing in that there would be a 2D/3D map and you could get a better idea of coverage.
Can you point me to the plug in you mentioned?
I’d be happy to open source this as well.
Here’s a link to the GitHub repo for the EverythingPresence configurator.
It’s a Docker container that is designed as a Home Assistant add-on. I can’t find a license type in the GitHub repo, so it isn’t clear to be if this is open or closed source (or if the Docker container contains anything that is raw code). But that’s the thing we’re all looking at (I have a couple of the devices for places the Inovelli switches don’t make sense).
The link from @pkscout is the one I’ve also been using with the Everything Presence One and Lite sensors I have. I also know that the Sensly-One mmWave sensors have a similar addon for their configuration. Sensy-Once Configurator Addon
If the plan would be to open-source it, is there a way to work with the existing configurator instead of making a new one? Then everyone benefits from the design enhancements.
My bet is that these GUI configuration options need to be tied to the hardware, especially given that the Everything Presence stuff is ESPHOME and the Inovelli switches are Zigbee/Z-wave. There’s a ton of work to get that graphical interface to turn into something that can tell the device what settings to change. It would be nice to have one tool to which you could plugin hardware description add-ons, but I think the two that have been linked are trying to build differentiators into their products, so a shared platform might be tough.
After installing a VZM32-SN, I noticed that the brightness (lux) level is being reported to the controller every 15–30 seconds. I tried adjusting the parameters — Lux minimum reporting interval, Lux maximum reporting interval, and Lux minimum change — but these changes don’t seem to have any effect on the reporting behavior.
This isn’t a major issue on its own, but I’m wondering if having multiple switches configured this way could potentially saturate the Zigbee network with too many reports.
What hub / driver are you using? I think that’s going to be a driver issue. Mine are installed in ST with an Edge driver and I have reporting accurately working every 30 minutes at a minimum.
I’m using 900 Min, 1800 max and 100 min change, and it’s working properly for me. I get a report every half hour at the most. Maybe try settings that are not right at the max.
Are you on the 7-19-25 driver?
Yes i think you can see the version in the screenshot “PILOTE”. I will try with you settings and see.
Yes, I see it in the screenshot now.
We’re both on a driver of the same date but they are slightly different. Also, you are in the regular Inovelli channel and I am in the beta channel.
@EricM_Inovelli will have to take a look
Thank you for the feedback. I’ll wait a little, or if it’s allowed, could you send me the beta channel so I can run a test? It might be related to the firmware, which would be surprising given the product’s recent release. Unfortunately, the version isn’t indicated in the ST configuration, and the key combination of holding the down button followed by pressing the config button nine times doesn’t seem to work on this model.
Can you test a couple things?
Lux Min Change > 1000
Wait 5 seconds
Lux Min Change > 1001
Thank you again for your help. I tried your approach with a 5–10 second delay between each modification. I also repeated the process with a delay between each change while applying the suggested parameters (900 Min, 1800 Max, and 100 Min). However, the lux value is still being recorded in the history 3 to 4 times per minute.
I got 2 switches and they aren’t consistently detecting presence. here are the home assistant histories of the presence sensors while my 2 kids were sleeping in their beds from ~8pm to 7am. The beds are about 10-15 feet directly in front of the switches. Do I need to tune the sensor somehow?
@grady on the pref tab you may want to try adjusting the target speed and on the commands tab reset the detection area and clear the interference area
