So I was trying to get the system to not turn on the lights when not needed by changing from using the built in occupancy to using home assistant to control the light based on occupancy and light level.
While the light I found to now be .5-1 second slower (not unexpected) the issue I now was getting is that if I were to walk into the room immediately after the light turned off, the light sensor will still be reporting the illuminance from when the light was on, resulting in home assistant not turning the light on. A possibility I could do is have illuminance changes be monitored as well in node-red and if it goes to dark while occupancy is detected to turn it back on (though I do have a worry that if i manually toggle the light then it’ll just turn back on). would it be possible to code in the firmware to push an illumance sensor update immediately after a light level change?
I’ve been seeing weird behavior with the mmWave params. It seems that only the pre-defined room sizes work properly, and was also seeing unexpected behavior for StayLife as well (setting a very high value with low sensitivity still turns off occupancy after a short while when motion stops but has not left the room). I see that there’s a beta firmware for the Red Series regarding the mmWave params - Red Series mmWave Firmware Changelog | VZW32-SN.
@EricM_Inovelli, is this something that could also be impacting the Blue series?
Exciting update which adds Z2M configuration of mmWave Stay Areas. Thanks @EricM_Inovelli and team!
I think I found a bug: I noticed that when I would try to adjust “Stay Area 1” WIDTH parameters, they would not apply as expected. It seems like it would swap min/max and also +/-
Bug on hubitat. pressing the favorites button doesn’t register an event of any kind. Rules using button 8/13 aren’t triggering either. Also, when the mmsensor is decoupled from the load, the motion sensor capability is not changing state. In fact, no “motion” state for it even exists. Also not seeing any mmSensor events on the switch itself. Is there a different method to detect mmwave state changes for rule triggering? Switch is working normally to control the load when param 110 is set to 1.
edit: “Configure all” on the switch corrected the button 8/13 issue and button 8 state is now showing. Still looking at the motion sensor problem..
Edit2: appears to be sorted. Once parameter 110 is changed to zero, another “configure all” has to be done before the motion state appears. Its all good, tracking active and inactive motion events and I’m standing down from defcon 1 lol…
It’d be nice be able to set the automatic on/off to a particular zone(s). Could be in that setting’s drop down or as binary switch per zone.
Use case is I have 2 switches in my kitchen and due to the layout and sight lines I need two switches. One is playing double duty with some accent lights. Would be nice if I could have the accent lights turn on/off automatically without an automation when I’m very close but still have a separate zone for whether the whole kitchen is occupied. Not the hardest to just make an automation to handle it but pure zigbee would be cool.
Might also be able to be used to have enter and exit zones?
Here’s another good one for you. Setting parameters 95 and 96 results in the LED 1 being different from the others. Testing on VZM31 works fine. Examples setting all color to yellow. Here’s the hubitat RM rule:
