Just wondering what the experience is for people using a combo of Zwave and Caseta.
I'm seeing times of 2 seconds to activate scenes. You'll notice int he screenshot, Ensuite Door Closed, which activates Ensuite lights can take up to 2 seconds, and rarely is it faster.
Maybe. In my experience, most Zwave sensors are pretty slow relative to most Zigbee sensors. There are exceptions of course.
I have never timed it, but with Zigbee, my lights are almost instant upon motion or contact. I would say sub one second if I were to guess. With a similar Zwave sensor it was much laggier, maybe approaching 2 seconds.
No. I will completely agree that most z-wave "motion sensors" are slower than most Zigbee motion sensors. This is accurate. There are a handful of z-wave motion sensors that are just as fast as zigbee.
This is about a door sensor / contact sensor. I've noticed little to no speed difference with these compared to zigbee.
I run z-wave door sensors and a RR2 setup and my lights coming on or going off based on the door sensor is instant. Literally door is closed switch is on there is ZERO delay.
If you are seeing the event in the log and the next event two seconds later it isn’t about sensor lag. We are past that at the point it is getting logged.
Here's the logs for my Kitchen Tube (Caseta switch) being turned on when the Kitchen motion sensor detects motion. This motion sensor is a z-wave+ sensor. The time from motion being detected to the light being turned on is ~125 ms.
I'm don't have debug logging turned on - so you don't see the caseta debug output ...
@lairdknox is correct. Something else is awry. Could you post the rule you use for contact sensor triggered lighting?
A few, security focused, extreme battery life, sensors have given people the impression that z-wave sensors are slow.. This is not the tech.. It is a manufacturer design choice
Seems fine to me. There is an extra action which should be able to be removed at the end of the rule. Since issuing the "Dim: Ensuite Pot Lights: 1" action will turn on the light if it is off, you should be able to remove the "On: Ensuite Pot Lights" action.
You should contact support@hubitat.com - this is an unusually slow response time. While I don't think there's anything inherently wrong with your rule, it suggests that there are other things slowing down your hubitat.
You should be able to turn on debug logging for the Rule. That might help diagnose where the time is being spent. The logs you posted are only showing the 'descriptiveTex' logging from the two devices. Having the app log its actions would be helpful.
You are right of course so apologies to everyone especially @philippompili.. did not want to create a whole new thread for a quick question that may or may not be useful to some - just lazy I guess. Will PM instead...
His logs suggest the command is slow to execute in the hub, not the actual time for the light to turn on/off. Depending on the bulb, some lights can only dim to 40%, so while ramping up from 0 will cause an additional delay to the eyes since the light only turns on at 40%. This may be part of the perception of slowness, but the fact is the hub is still taking 2s before it even starts the dim process.
I'll echo the above. Reach out to support. I had a recent slowdown, even worse since I'd have some commands taking almost a minute to fire, and Bobby was great at helping me get it straightened out.
A few, security focused, extreme battery life, sensors have given people the impression that z-wave sensors are slow.. This is not the tech.. It is a manufacturer design choice
