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
{{ message }}
This repository has been archived by the owner on Mar 6, 2022. It is now read-only.
I have added logging and noticed the pir.watch sometimes sends consecutive false values (sometimes three times) before a new true value. Not sure why this happens, but when it does there will be multiple setTimeout called for deactivateMonitor.
So even if there is movement, the next movement detection will only deactivate the last setTimeout, and the others will still turn off the display at some point.
Before calling self.deactivateMonitorTimeout = setTimeout(function(), there should always be a clearTimeout, even in the (value == valueOff) case (line 177 of node_helper.js )
If you want I can do a pull request with this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have added logging and noticed the pir.watch sometimes sends consecutive false values (sometimes three times) before a new true value. Not sure why this happens, but when it does there will be multiple setTimeout called for deactivateMonitor.
So even if there is movement, the next movement detection will only deactivate the last setTimeout, and the others will still turn off the display at some point.
Before calling self.deactivateMonitorTimeout = setTimeout(function(), there should always be a clearTimeout, even in the (value == valueOff) case (line 177 of node_helper.js )
If you want I can do a pull request with this.
The text was updated successfully, but these errors were encountered: