Alert length vs Cool down about homebridge-nest-cam HOT 5 CLOSED

This is expected behavior. When motion is detected, motion is set to true and a notification is sent to homekit. 5 seconds later, motion is set to false and the cooldown begins, not allowing another notification to be sent for alertCooldownRate seconds. Motion must be set to false 5 seconds later or users will begin to receive multiple notifications for the same alert.

from homebridge-nest-cam.

The automation is 2 part, I am using is one where motion is detected and I turn a light on, the second is motion is no longer detected and the light is turn off. it seem like the false is sent so close in time to the true that homekit never turns the light on. If I disable either one of those steps, the step works. But with both on nothing runs. If it did work I am thinking I would see the light on for 5 second every 3 minutes. I am trying to follow what the camera is actually seeing, i am not sure how to do that if it is being set to false prior to the next poll or next update. Any suggestions?

from homebridge-nest-cam.

I see what mean. I've created a new test version of the plugin that now leaves the motion state on until it doesn't see motion anymore. If you can, try it out and let me know if that works better for you. You can install the test via npm -g i homebridge-nest-cam@test.

from homebridge-nest-cam.

Yes, the behavior is as I expected, the logic looks better. I also have 2 structures and was able to test that. I'll comment in that thread. Thanks for such a quick turn around.

from homebridge-nest-cam.

This is now included in v2.5.0. Thanks for the bug report!

from homebridge-nest-cam.