Unacceptable delay from Motion to LED

I recently purchased a Zooz ZSE18 Motion Sensor and a Zooz ZEN31 RGBW DImmer to use in our master bedroom. The intended design is that when getting out of bed at night, LEDS under the bed turn on to a low level to light the way. Everything is working, but the problem is that there is 3-4 second delay from when motion is active and when the dimmer switches on. We are are practically across the room by that point. I have other motion sensors connected to z-wave wall switches throughout the house and those are near instantaneous. Have I done something wrong with the dimmer? Is the dimmer just that slow? Here is the log I see:

Here is the real simple rule:

I feel like I have isolated to the dimmer, because I added another switch to the rule that turns on right away when motion is detected.

Found the issue. The ZooZ dimmer has a ramp rate setting that defaults to 3 seconds, I changed it to instant. Interestingly, if the ramp rate was intended to fade in and out...the fade was only noticeable when turning off. When turning on, it seemed more like it just sat there and then quickly dimmed up.

3 Likes

LED sometimes don't like low power levels. You have to have enough power to make the diodes conduct. These might not have turned on until say 18% so they appear to just sit there until they hit that magic point where they conduct.

Glad you found the issue.

1 Like

have a kitchen light fixture that won't turn on at less than 23%. This is causing me to try to figure out how to exclude it from mode manager as all the rest of my lights are set to 15%mat night.

1 Like

You using scenes, or how are you setting these per mode? Mode Manager itself doesn't control lights.

I was trying out the motion and mode lighting app. First try so most likely I missed something. no big deal just testing.

You should be able to adjust that level without deleting anything.

I think I see what you did. I don't use Mode lighting, so I had to experiment. It only sets one level for all bulbs.

So I think you could either install a different instance of this, or what I would do is make a Scene with these all whatever levels you want. When you create a scene, it automatically creates a virtual switch. I like and use scenes because you can mix dimmers and switches and have various dimming levels.

So back in Mode lighting, turn on that scene instead of each individual light. Or easier yet, you could even use Simple Automations to turn on that scene virtual switch.

Thanks for the idea. Hadn't tried scenes before. I already had a simple lighting app that used the motion sensors to turn on the two lights (hallway and kitchen) was playing with this because sometimes the motion sensors seem slow to react. The motion and mode lighting app also allowed a contact sensor as a trigger. (bedroom door) will try the scenes tonight.

May try different path. My kitchen light is an Inovelli Red dimmer. There is a firmware update that allows setting min-max dimming levels. Probably better so that I won't try again setting levels light fixture won't support.

1 Like

Scenes are a little odd/clumsy to set up, but once you have them they really are useful.

2 Likes

Wanted to provide an update. I was still having issues with a delay from motion to led. I had a samsung smartthings motion sensor in my closet that has worked flawlessly for years. So I swapped that with the new zooz motion sensor that I got for this LED lighting. Using the samsung sensor, the LED lights turn on right away, every time. And now my closet has a maddening 2-3 second delay when I enter it before the lights turn on. So in conclusion, I have found that the zooz motion sensor is garbage. I wish I could get more samsung sensors, but seems like they aren't making them anymore. Anyone have any suggestions for good motion sensors that report immediately? Or could my issue be z-wave related (zooz) since the samsung sensor is zigbee?

I find Zigbee sensors to be far faster than Zwave. But 2-3 seconds isn't just the "normal" Zwave lag.

Some have had issues with Zooz sensors, but this wasn't the model reported to be causing issues. That was the 4-in-1 sensor. But maybe this also does something to the Zwave network like the 4-1 sensor? I have a similar generic model of this sensor that is pretty decent, so not sure why this is that slow?

And it could be your Zwave network, but I would think that you would have issues with other Zwave devices if you have, maybe a weak mesh, or something causing interference with the network. It wouldn't hurt to post a screenshot of your Zwave Details page and maybe someone could spot something wrong with that.