Red mmWave dimmers (VZW32-SN) running 2.2.0, hub is Home
Assistant with Z-Wave JS. Air gapped them after the 2.02 update like Eric
said to.
The one in our hallway keeps reporting motion in the middle of the night
when nobody’s up. Only noticed because the hall light kept blipping on
around 2-3am. Went back through the history and the motion sensor on the
dimmer goes active for a second or two then clears, no one near it. Handful
of times just this week, all between midnight and 4am (6/7 at 12:23 and
12:28am, 6/8 at 2:35 and 2:44am).
Reason I’m sure nobody’s there, my wife and I both have bed sensors (Sleep
Number) and they show both of us in bed the whole time, and the bathroom
light is on a motion switch and it never tripped. So the hallway is seeing
motion with two people asleep and nobody in the hall. When one of us
actually does get up for the bathroom it looks totally different, motion
fires, bathroom light comes on a few seconds later, bed shows someone got
out, and the light stays on ~30 sec. The phantom ones have none of that and
only last a few seconds.
Not a huge deal since I’ve got an automation that flips the light back off,
but it’s clearly the sensor firing on its own.
Other thing that might be related, that same hallway unit is getting noisy
on the zwave side. Over about 4 days the supervision reports off it went
from ~18/day up to 170+, and by 6/7 I’m getting S2 nonce errors and a couple
SPAN decode failures in the zwave js log. The other two dimmers are quiet.
Saw momo’s thread on phantom motion so figured I’m not the only one. Same
issue, and is there anything in a newer beta for it? Or a sensitivity/
blocking param worth tweaking to cut the false detections down in the
meantime? Can pull whatever logs help.