117 room size param does adjust ranges
params 101-106 seem to do nothing. I’ve tried setting extremes in all directions and behavior isn’t changing
in my example use case, if I set room size X-small for my hallway it’s mostly correct
but then I can’t tune my left side, so I have to stand within ~3 ft for it to trigger
adjusting 101-106 is not changing behavior
if I set room size XL, it can see the entire hallway - so it’s not a visibility problem
but then it starts triggering in the bedroom
Also experiencing the same. Setting room size does take, however, even though I set the room size and it saves in ZWAVE-JS, it does not update. It uses the old “room” size I previously set. Also tried updating backwards, 106-101, and sensitivity, 10 seconds apart. They all save in the UI, and refresh to make sure the parameters take, but, it does not update the room size from the previously set (with manual room size instead of custom).
Hi Eric, is there any indication from your investigation so far that this is an issue that can be mitigated somehow? I am waiting to configure my switches now, and I am wondering if I should spend time tweaking these settings or wait until there is more information.
I am glad i am not the only one with this issue. It’s really easy to test if you change the mmWave Detection Timeout (114) and mmWave Stay Life (108) to really low. Excited to hear any updates on this
Is there a way we can have the switch return the raw settings from the mmw module? That way we could tell if the settings are being applied and it is a mmw module issue, or not being applied and firmware needs updating.
It looks like the zigbee version you can send commands direct to the mmw module and get output from it, but I do not see that for the z-wave version.
Thanks for sharing this! Are you aware of any place that these types of changes are shared or is it always as comments on the community site? I was looking everywhere for something more dynamic, for example in inovelliusa github repos. Even just issues that are being investigated would be very useful/hopeful. I don’t want to setup automations or install my other switches if they arnt going to be working (or will change in a major way) until there is a firmware update.
I have a dumb question about settings P103 and P104. When you say P103 LEFT, is that left from the switches point of view out or when I’m standing in front of the switch looking at the switch.
like if i am looking at the switch the directions are reversed? Maybe you guys can just add a note to the configuration something like “Left, the side of the lightbar” that makes it very clear.
Thank you! I have been playing around with this update on a couple Red mmWave switches off-and-on today and custom room sizing has drastically reduced “phantom” motion detection coming from sources beyond my own walls (one switch was being activated by neighbors on the other side of a shared wall, another by people walking down the common hallway), and they’re effectively handling motion detection now as I’d hoped.
edit - I had previously mentioned an example of detection at 45/135 degrees being significantly worse than expected after setting custom room sizing and it requiring you to set extended room boundaries (which caused detection issues through walls) in-order for those angles to be successful at being detected. But it all seems to be the result of mmWave emitting a cone-shaped pattern, so I went ahead and deleted it. This will just be something that needs to be accounted for when planning out your switch placement.