The new log features are cool...but does this look right?
Is this measurement supposed to be latency? That's um...bad if so, but could explain why my Zooz siren takes way too long to make a door open chime.
Your siren is responding in 70 milliseconds on average, has done so 290 times, making a total of 20.165 seconds. So this suggest it's fine.
These numbers really just represent how long the driver code (or app code for apps) takes to run. In many cases, that's likely you initiating a command from Hubitat (manually or via an app/driver), then the driver formatting a Z-Wave command to actually send to the device before exiting. I'd say 70 ms looks pretty good for that. What the device actually does after that is another story. 
Ideally, this would be a beaming device and wake up at most 1 second later and execute the command (it's supposed to be), but you're not alone in reporting that these devices--both this one and others that appear to be the same OEM--are a bit laggy sometimes. But you're unlikely to see that reflected with these metrics on Hubitat. (The other thing this runtime would count is any time the driver code runs to parse a report from the device, like a battery level.)
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
