You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When in a room with a motion sensor, this often triggers repeatedly in a short space of time as motions becomes active/inactive every few seconds.
This has knock-on effects on other plugins (eg. homebridge-alexa) which reports many status updates which end up being throttled.
It may be sensible to add a minimumDuration setting (or similar) which could be used to prolong motion events reported to homebrige to say 30 seconds. Only after 30 seconds of inactivity would the motion state be cleared.
This would also facilitate better rules around actions taken upon cessation of motion.
The text was updated successfully, but these errors were encountered:
When in a room with a motion sensor, this often triggers repeatedly in a short space of time as motions becomes active/inactive every few seconds.
This has knock-on effects on other plugins (eg. homebridge-alexa) which reports many status updates which end up being throttled.
It may be sensible to add a minimumDuration setting (or similar) which could be used to prolong motion events reported to homebrige to say 30 seconds. Only after 30 seconds of inactivity would the motion state be cleared.
This would also facilitate better rules around actions taken upon cessation of motion.
The text was updated successfully, but these errors were encountered: